|Pathologically Eclectic Rubbish Lister|
Re^2: PM redesign: status update (compare)by kimmel (Beadle)
|on May 24, 2012 at 04:09 UTC||Need Help??|
What issues with IE I can fix with HTML comments, I did. Here is the head element of one of the two design templates I am working on. This head example has all the IE comment support stripped out. As you can see it is very short and to the point. Now lets look at a head with IE support included, it is longer and more complex. Here is just the IE fixing code:
That fixes a whole mess of trouble for us concerning IE. To get HTML5 semantic elements and CSS3 Media queries is more complicated. The Story of the HTML5 Shiv does a great job explaining the development landscape that lead to html5 shiv. Of note is the following:
Fast forward to 2008, HTML5 is gaining momentum. New elements have been specified, however in practice, Internet Explorer 6-8 pose a problem as they do not recognize unknown elements; the new elements cannot hold children and are unaffected by CSS. This sad fact was posing quite a big hinderance to HTML5 adoption.
The linked screen shots show very little to have much opinion on unless you are trying to design a layout for use only on "mobile". They don't even appear to cover what it looks like to read a thread even just on "mobile".
I get what you are saying. I updated my post with more refined questions of what I am asking for.
The "before" screen shots on small devices don't use any of the pre-existing features for supporting small geometries.
Do you mean preexisting features in the PerlMonks design? Those screens are just after the page loaded. Do I need to append data to the url to get a different design or something else?