Forum:Broken in IE8

WowWiki (and other brands) are completely broken under IE8.

Please see:

http://blogs.msdn.com/mikeormond/archive/2008/09/25/ie-8-compatibility-meta-tags-http-headers-user-agent-strings-etc-etc.aspx


 *  (that's not a wikia's response)  What is broken, WoWWiki or IE8? I hate having to code hacks for specific browsers. I see that IE8 needs also hacks to make the web compatible with that browser, which is really stupid. Instead, IE8 should be compatible with the web.
 * If you are still using IE, please, do us (the web developers community) a favor and use an alternate browser that follows the latest standards. --Ciencia Al Poder (talk) -WikiDex 16:44, 17 October 2008 (UTC)


 * Thank you, Ciencia :) If it gets close to IE8's release and there are still problems we will certainly spend time looking into it. We (and especially myself) did check over how the site acted in IE8 Beta 2 a while back, and I know it resulted in blank pages in some circumstances - though that appeared intermittent. There is always the IE7 compatibility mode, a single click away, that should make it work fine for now. 17:44, 17 October 2008 (UTC)

As long as the Doctype is good, iE8 should use the higher standard it has. At least that is what it say in that article. — TulipVorlax 19:19, 17 October 2008 (UTC)


 * Hacks? IE is the most used web browser, and 8 will be the next version. How can you call making it work properly a "hack" ? -- LordTBT Talk! 06:26, 19 October 2008 (UTC)


 * The blog linked avobe says how to change the behavior of rendering pages on IE. It says several ways:
 * Meta tag in header (&lt;meta http-equiv="X-UA-Compatible" content="IE=......."/&gt; ). This is NOT a standard, because is focused on a particular browser. This is what I call a hack.
 * HTTP Header (X-UA-Compatible: IE=........ ). This is NOT a standard, because is focused on a particular browser. This is what I call a hack.
 * Conditional comments (&lt;[If IE 8]&gt; ... &lt;[endif]&gt;). This is NOT a standard, because is focused on a particular browser. This is what I call a hack.
 * A browser that needs such hacks to render properly a web is a crap. People use it because is installed by default on Windows and are lazy to find out better alternatives.
 * But well, not all the guilt is for IE. Once Wikia passes the XHTML validator, then we could see if the problem is solved or not.
 * BTW, the DOCTYPE of the documents generated by MediaWiki is, but documents are served as  . That means that: The document is XHTML 1.0 Transitional, but it should be rendered as HTML (not XHTML) by web browsers (see XHTML Media Types), so all browsers (including IE8) should render them as HTML instead of XHTML, without the need to put a "compatibility mode" hack.
 * On my part i think the lazyness part is on the web designer's side as i'm one od them and when i do web sites i put the conditionnal statement for all version if IE in them so all page have links to CSS files for each version of IE in wich we can alter the CSS rules that need it (and only them), the defaut CSS file been for Firefox and others. But with IE7, most of my sites dont even have anything in the dedicated CSS. When they'll have a french version of IE8, i'll try it. — TulipVorlax 18:40, 19 October 2008 (UTC)
 * IE8 shouldn't require any changes, given the work they put into updating the CSS and HTML rules this time. We already support IE8 in that we don't apply any specific hacks to it - everything like that only applies to IE7 and below. With a proper doctype (which we have), IE8 should use standards mode. With all that being said, we will ensure Wikia works on IE8 - there's really very little reason why it wouldn't. 20:13, 20 October 2008 (UTC)