[theme-reviewers] Ang.: Current Theme Unit Test Data
myazalea@hotmail.com
myazalea at hotmail.com
Wed Jul 18 23:51:01 UTC 2012
With the amount of users, who better to set the standard than WordPress, if we can only come up with and agree on some minimums.
Maybe decide on some standard breakpoints and have the theme check plugin to check if they exist in the css.
Skickat från min HTC
----- Reply message -----
Från: "Emil Uzelac" <emil at themeid.com>
Till: <theme-reviewers at lists.wordpress.org>
Rubrik: [theme-reviewers] Current Theme Unit Test Data
Datum: tors, jul 19, 2012 02:21
And again this is a never-ending conversation, since there's not really any standards as far as the Responsive Web Design :)
Emil
On Wed, Jul 18, 2012 at 6:09 PM, Daniel Tara <contact at onedesigns.com> wrote:
What I mean to say is that the main layout adaptations should not rely entirely on JavaScript. Using it as fallback, to prettify traditions or where there's no other alternative should be fine.
Daniel
On Jul 19, 2012, at 2:05 AM, Emil Uzelac wrote:
"Design responsiveness should not be JavaScript dependent"
IE8 and bellow do not support CSS3 media queries, so JS is very much needed :) please see: https://github.com/scottjehl/Respond/ I'm using that in my Theme and many others out there.
Thanks,Emil
On Wed, Jul 18, 2012 at 5:43 PM, Daniel Tara <contact at onedesigns.com> wrote:
The only guidelines I would recommend regarding responsive design are:
No content should be hidden, ever, that's (very) bad practice.Images should constrain proportions.
Design responsiveness should not be JavaScript dependent
Everything else would mean restraining the developer. IMHO.
Daniel
On Jul 19, 2012, at 1:10 AM, Emil Uzelac wrote:
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)
Thanks,
Emil
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
_______________________________________________
theme-reviewers mailing list
theme-reviewers at lists.wordpress.org
http://lists.wordpress.org/mailman/listinfo/theme-reviewers
_______________________________________________
theme-reviewers mailing list
theme-reviewers at lists.wordpress.org
http://lists.wordpress.org/mailman/listinfo/theme-reviewers
_______________________________________________
theme-reviewers mailing list
theme-reviewers at lists.wordpress.org
http://lists.wordpress.org/mailman/listinfo/theme-reviewers
_______________________________________________
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/20120719/56fe006a/attachment.htm>
More information about the theme-reviewers
mailing list