On Wed, 25 Apr 2012 15:36:30 +0100, Ellen Herzfeld <[email protected]> wrote:


On 25 Apr 2012, at 11:48, Duncan Hill wrote:

This could potentially drift off-topic for CSS-D as it is more based on JavaScript being used to apply styling, and without specific CSS queries one of the other lists may have more help to offer.

You are right, but in this case, I had no way of knowing if my problem came from the javascript or the CSS, or possibly both.

Seems the JavaScript is failing to provide the correct styling for IE8.

selectivizr requires a JS framework, it would seem prudent to load the framework first (jquery)

I'm using nwmatcher with selectivizr because jquery has incomplete support (and is missing things I need). I know that makes for a lot of js for IE 6/7/8 but it's that or nothing. Anyway, this is just a test run. I'll get into optimization later.

The point was that selectivizr 'requires' jquery, it is loading and probably triggered 'before' the jquery is available.


I still don't understand this part:
<!--[if gte IE 6]><!-->
                <link rel="stylesheet" media="all" href="/2012/reset.css" />
                <link rel="stylesheet" media="all" href="/2012/base.css" />
                <link rel="stylesheet" media="all" 
href="/2012/content_modules.css" />
<!--<![endif]-->
that seems to conditionally serve the stylesheets to IE6+, yet it also serves them to all browsers.


Yes, that is the point. IE less than 6 doesn't see the stylesheets that are served to all other browsers. Actually, this is something that is a holdover from a site that was made a few years ago, when IE 5 and 5.5 were still around and I had decided that enough was enough for those two. So I suppose I could remove it now, since hopefully IE 5 and 5.5 are dead and buried. I'm still trying to cater to IE6, but my latest tests cause it to crash on a regular basis. I haven't decided what I'll do about that yet.

If it is no longer needed or relevant, it should be removed to eliminate it as a cause.

It's a bit difficult trying to do "mobile first" and still serve a desktop site to IE < 9. But it's been difficult with IE for years...

Fully prepare your mobile site for the browsers that can natively handle the styling correctly, then you have a solid base to pick off specifics for the less capable.
Are there really a lot of IE < 9 'mobile' browsers still in the wild ?

I think you are right and I should go elsewhere with my problem.

There have been many discussions on this list about solving problems with @media and mobile styling, I'm sure much better advice will come if you are more focused on the CSS first.

Good luck

Duncan
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to