[theme-reviewers] Current Theme Unit Test Data

Emil Uzelac emil at themeid.com
Wed Jul 18 22:10:27 UTC 2012

Hi Bruce,

This is all good and we appreciate the heads-up, however at this moment I
would not require Theme Reviewers to test RWD.

Think of it like this. If developers says that their Theme is HTML5, none
of us will actually go and check just to see if every Theme element is
HTML5 and/or if developers decided to "hack" with non-HTML5 techniques.
As Chip said once this will be under the description and that's all for
right now.

Just for FYI purpose only all this and much more is under my Theme
http://wordpress.org/extend/themes/responsive, feel free to browse around
if you need. Autohide or shrink of sidebars is not the best practices, I
would always prefer to "stack" -vs hide.

Few sites to consider:

   - http://foundation.zurb.com/ (my personal favorite)
   - http://twitter.github.com/bootstrap/ (second favorite)


On Wed, Jul 18, 2012 at 1:30 PM, Bruce Wampler <weavertheme at gmail.com>wrote:

> Sorry a bit slow with this - Chip asked for some ideas about responsive
> theme tests or guidelines. Here are some of the issues I believe to be
> important:
> 1. Sidebars - sidebars should nicely shrink with the rest of the page -
> things should stay proportional. At some point (maybe at about 480, maybe
> even below 600), the sidebar should autohide or everything gets too
> squished. I think this kind of behavior should be at the least RECOMMENDED
> for responsive themes, if not required.
> One of the problems testing this behavior is that not all browsers respond
> to responsive div hiding - they need a manual refresh at each new width.
> The content will shrink fine, but the responsive hides don't always
> auto-show.
> 2. Images - images need to shrink as the screen does. This includes the
> header image.
> 3. Menus - menus need to resize nicely. This isn't always easy to do, and
> it is not uncommon to get a mess of unreadable, unusable stacked menu items.
> 4. Possibly unhide or move special areas as the width shrinks. Sidebars
> might switch from the side to the bottom, for example.
> 5. Video media - Video should either dynamically shrink with the screen
> (not easy), or at worst hide the overflow.
> 6. Same for iFrames.
> 7. Titles - titles should ideally shrink and wrap, not overwrite
> surrounding content. Actually, same for all content. The content should
> shrink or re-wrap, and not overwrite surrounding content or sidebars.
> 8. If themes have special handling for some devices (iOS or Android), it
> should be noted, but it is probably unrealistic to expect testers to have
> those devices to test on. Don't know how such things can be tested. Maybe
> if there are reviewers with access to such devices, they could have
> priority for testing such features. Don't know how many themes include that
> kind of support yet, but I imagine it will become more common. It might be
> interesting to discuss as recommends to use the existing iOS features that
> are available with the WP admin side. (I know they are there, but
> unfortunately don't really know if they can easily be used by themes. Seems
> like a good opportunity.)
> Also, Opera has a mobile device simulator that could be of some use for
> testers of responsive themes.
> Bruce Wampler
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120718/2596d3f3/attachment.htm>

More information about the theme-reviewers mailing list