RE: [WSG] IE8 compatibility mode

[Nick Hodge]

 
 On Mar 25, 2009, at 10:07 AM, Gunlaug Sørtun wrote:
 
  tee wrote:
 
  Sorry for my ignorant, is IE8 out?
 
  Yes, as of March 19th.
 
  Keep an eye on a site like this...
  http://www.upsdell.com/BrowserNews/
  ...and you'll at most only be a few days off regarding new releases.
 
 Georg, thanks.
 
 I have developed a work fatigue symptom that I don't want to deal with
 any beta version of browsers until they finally arrived.
 
 Strange that Microsoft is a bit shy with the new release because  I
 have not been prompted to update the browser each time I turned on the
 PC. None of my clients' sites that I have access to their analytics,
 show IE 8 stats, except mine.

Shy no; more careful. Forcing major version updates on day 1 is generally 
risky. Security updates are treated differently.

More info on Windows Update plans for IE8:

http://blogs.msdn.com/ie/archive/2009/01/06/ie8-blocker-toolkit-available-today.aspx
 

 Good news is, all sites are rendering properly as I expected them be,
 except one that the jQuery slide show is showing the exact problem as
 I saw in IE6 and 7.
 
 A heads up, I was using Classic View for my Vista, in IE8 with
 standard mode the sites all had a few paddings/margins issue in a
 number of pages where absolute position is declared, and on few areas
 where there is darken background color with lighter 1px horizontal
 line, the line turns to solid white. Soon as  I switched to Vista
 View, all these problems disappeared.

Is the URL for this so I can escalate to IE8 team?

Nick Hodge
Professional Geek, Microsoft Australia


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

RE: [WSG] IE8 compatibility mode

[Nick Hodge]

 James Leslie wrote:

  Using meta http-equiv=X-UA-Compatible content=IE=8 / will also
  have the same effect (getting rid of the compatibility view button
  and forcing standards mode), but may be a bit more stable against
  future releases of IE.

 But, may also lock documents to IE8's rendering capabilities even if
 future IE releases can handle more, better - which they should. Not
 very
 wise, IMO. You wouldn't choose/advice such a safeguard strategy for
 any of the other browsers, would you?

 IE8 does have a few dozen irritating bugs and weaknesses, and is
 (pretty
 much) limited to CSS2.1. However, IE8 final is pretty stable and works
 quite well for all properly built sites, so one can say Microsoft has
 done an acceptable job. No signs they'll jump off the standards path
 either now that they've finally got on it, even if they're a little
 behind the others.

 What's holding IE8 back now is all those sites that has been
 safeguarded and tailored to work in earlier IE versions as if there
 was no tomorrow, and it is about time we stop treating IE as a browser
 that will be in need of special solutions forever.

100% agree. Build sites to standards. This will help your design work on 
Firefox, Chrome, Safari and IE8

Nick


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***