Home >
I was a bit nervous about telling my coworkers about the fact I'm doing this blog. After all, I'm under NDA and my inspiration for these posts usually comes from things that happen on the job. I try to keep things very general, but I'm very aware that if I stray to the wrong side of that line I might not have a job for very long. However, now people know what I'm doing it's actually a big plus—my coworkers pass along their juiciest tips with the idea that they might end up here.
So here's a shout out to Chris Casey, who made me aware of this not-so-stupid CSS trick for sites/pages that aren't yet ready for IE 8's Standards mode: IE=EmulateIE7 Header. In a nutshell, this tells IE 8 to act like it's IE 7 when displaying your page/site, quirks mode and all.
Tag Cloud
Podcasts & Screencasts
@InsideRIA on Twitter
Follow InsideRIA on Twitter
Facebook Application Development
Interesting. Would you know what the primary display differences between IE7 and IE8. I am heavily involved in design of a free web dating site and have primarily done most of the CSS using IE7 as test client. I will test it in IE8 next week after reading your blog but am wondering what are the primary things to look out for ... like tables, margins, padding.
The consequence of these violations can be quite visible when a filter is syntactically invalid e.g. missing a terminating parenthesis. CSS syntax error recovery rules require parsers to ignore unknown, illegal or malformed declarations by locating the end of such declarations and resuming parsing the rest of the style sheet. An important caveat is that certain character pairs must be matched during the recovery : if one or more ‘(‘ are found, the declaration does not end until the matching set of closing ‘)’ have been parsed.
Sökmotoroptimering