The point is to avoid this approach whenever it's possible. First, this backward-compatible mode was originally introduced to allow nonstandard web sites to not break in newer versions of IE. Second, this compatibility mode will be sooner or later abandoned by IE (IE10, for example, dropped its support to conditional comments to basically demonstrate its consistent standard support). In that vein, you should **not** follow this approach. Instead, embrace graceful degradation as a more useful way to develop web sites. This approach is followed by big stars such as Google and Yahoo (Yahoo originally introduced this idea through a detailed browser support chart), so why you insist with sticking to tricks and hacks?
Bye :-) On Fri, Apr 19, 2013 at 6:05 PM, David Hucklesby <huckle...@gmail.com>wrote: > On 4/19/13 1:31 AM, AngelPSan wrote: > >> Hi, anyone knows the definitive solution to make internet explorer web >> pages load in standard mode? >> >> > Boy, have you opened a can of worms! > > Here's what Microsoft[1] has to say (about IE 9) - > > "Important The new standards support in Internet Explorer 9 requires the > browser to be in Internet Explorer 9 Standards mode (“IE9 mode”). The best > way to do this is to use a standards !DOCTYPE directive and no > X-UA-Compatible meta tag or HTTP header. The !DOCTYPE to invoke IE9 mode is > the following: > > <!DOCTYPE html> > > ..." > > > Personally, I use the X-UA-Compatible flag no matter what, as IE 8+ > displays > a "Compatibility mode" button if I don't. This button switches IE to the > anything-but-standards mode that emulates IE 7. As it appears next to the > browser's refresh button, so very easily pressed by mistake. :( > > The X-UA-Compatible META was introduced in IE 8. Earlier versions use a > valid DOCTYPE to force so-called standards mode. But it must come first on > your page. Leading comments or an XML declaration in front will fail to > enforce standards mode. > > There are additional issues if you add lots of class names to the HTML tag, > for example if you use "conditional class names" or Modernizr. You can read > about those issues here: > > <http://nicolasgallagher.com/**better-conditional-classnames-** > for-hack-free-css/<http://nicolasgallagher.com/better-conditional-classnames-for-hack-free-css/> > > > > "Definitive solution?" I don't know. But this is to the best of my current > knowledge. I do hope it helps. > > > > [1] > <http://msdn.microsoft.com/en-**us/ie/ff468705<http://msdn.microsoft.com/en-us/ie/ff468705> > > > -- > Cordially, > David > > ______________________________**______________________________**__________ > css-discuss [css-d@lists.css-discuss.org] > http://www.css-discuss.org/**mailman/listinfo/css-d<http://www.css-discuss.org/mailman/listinfo/css-d> > List wiki/FAQ -- > http://css-discuss.incutio.**com/<http://css-discuss.incutio.com/> > List policies -- > http://css-discuss.org/**policies.html<http://css-discuss.org/policies.html> > Supported by evolt.org -- > http://www.evolt.org/help_**support_evolt/<http://www.evolt.org/help_support_evolt/> -- Gabriele Romanato Referente IWA ITALY - Regione Abruzzo International Webmasters Association Italia http://www.iwa.it | e-mail: abru...@iwa.it Professionista Web - Legge 4/2013 http://gabrieleromanato.com/ http://gabrieleromanato.name/ (English) ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] 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/
