We have used SIFR to change the property of H1 tag, this is working fine in IE6,7 and Mozilla 2.0 but in IE 8 its not applying SIFR properties to Ha tag and instead of showing text its showing XXX in the browser. I don’t have any live url for this issue.
I have seen the same issue you have been getting, it is rather curious but it only occurs with IE8 in standards compliancy mode. If you trigger the compatibility button, the issue disappears and the sFiR loads perfectly fine. It seems to be a general compatability issue but the cause is currently unknown.
Hi Guys, I’ve got the same problem with IE8 and sIFR now.
see my website: smart-im.nl for example.
In compatability modus it works fine, in IE8 it shows
What version of sIFR are you guys all using? I haven’t seen any problems with v2.0.7 in IE8, compatibility mode or not.
edit: oh right, I see one person using the beta of v3… might be a problem with v3 then. Take it up on Stack Overflow with Mark Wubben I think his name is.
This is why I still stick with the release version for production websites!
mitchrenton, I would not advise that unless you want Microsoft to potentially add your website to the “broken list” to which it will permanantly render in that method unless you include the META tag to force compliency.
Thats not true, only high traffic/volume sites will actually be put on that list. And second its not permanent once your site works in IE 8’s standard mode it will be taken off the list. Small personal sites are not likely to be put on that list. Also before Microsoft even puts your site on that list, the site owner is contacted.
I forgot to mention…your site will not be put on this list if you use the X-UA-Compatible (for IE7 mode) header. Only those sites that do not use it, that actually require it. (I.e. sites that do not work in standard mode that do not issue the X-UA-Compatible header.)
I have used the
<meta http-equiv=“X-UA-Compatible” content=“IE=EmulateIE7” />
To workaround the problem, but we certainly need a fix. This is not a site specific problem, but appears to be widespread accross many platforms. I am using umbraco CMS (a DotNet CMS running on IIS) version 3 beta 1. I updated from version 2 back in the IE8 BETA days due to the same issue.