Please forgive me if I placed this in the wrong section of Stack Exchange, I will be happy to repost elsewhere, Im just not sure which section to go to.
Why does IE8 display differently in Browser Mode (which is accessible through the IE10 F12 Developer Tools) than in XP Mode?
It seems that the CSS is rendered differently. Does anyone know the details as to why this occurs?
IE8 Browser Mode vs IE8 in XP Mode CSS renders differenty?
Yep, that's a pretty well-documented problem. It may be called compatibility mode, but the fact is, it isn't really all that compatible.
This is why it's generally considered a bad idea to use compatibility mode to do your testing.
Ultimately the only reliable way to test that a site works in IE8 is to actually load it in a real copy of IE8. XP Mode is a good way to do that.
I agree it's more of a hassle than switching the mode in IE10, but unfortunately, that's the way it is.
Related
Generally speaking my font works fine but I'm seeing on odd occasions such as switching back to the browser from another application and sometimes when switching back from another tabs that my font seems to have unloaded and is using the fallback font.
I'm struggling to consistently replicate this and when I have seen it there are no errors.
I have also seen this happen in Chrome and Firefox on windows and osx and at a bit of a loss as to how this can be happening.
I haven't seen this issue in Firefox personally, but it is a known bug in Chrome.
https://code.google.com/p/chromium/issues/detail?id=336170
does anyone know how can i force IE 10 to open in IE8 browser mode. Is it possible, Change something in IE settings? Does IE have some kind of a config file what can define it? Or can i make some changes in REGEDIT to force it to open in IE8 mode?
If you want cross-browser testing, take a look here. This offers multiple browser testing without the need to have virtual machines etc.
If your specifically looking for IE, then take a look here.
EDIT: You can look at IE10 on Windows 7 Side-by-Side IE8 for the issue you have.
If I use the F12 Developer Tools to debug for IE, can I depend on the "Browser Mode" and "Doctype" to debug issues for IE8 and below?
By debugging I mostly mean for overall page behavior... HTML/CSS, A client says "The dropdown doesn't work in IE8", I have IE9... Instinct is to hit F12 and change the doctype or browser mode and test.
Short answer, no.
I would not recommend using compatibility mode. I have never quite understood why MS doesn't seem to do what Mozilla and Google do which is, disallow the use of deprecated tags. As an example, at my work, we have two tiers of browser usage, tier 1 and tier 2. Tier one consists of: Safari (oddly enough, we get quite a few customers buying via their iPads), Chrome, Firefox and IE9. Tier two is: IE8 and the rest of the pile. Recently, we had a bug where some checkboxes where not rendering correctly in **only IE8**; but worked fine in IE7 and IE9. The moral here is that using compatibility mode is testing under an assumption, and if you want thorough and correct testing, you cannot assume anything.
You can try to use the Quirks mode, but that's not 100% the same. If you are lucky, you will hit the same bug also in quirks mode.
The only sure way is to use a IE8. There are cross-browser testing tools that enable you to do so without any installs.
Just for bug reporduction purposes http://www.modern.ie/virtualization-tools offers some VM-s you can use.
I'm working on a corporate intranet and we have recently redesigned it using all sorts of CSS3 goodness as specified by a design agency. Our corporate standard browser is (still) IE8 so in order to make the CSS3 work I employed CSS3 PIE (http://css3pie.com/) which recreates the CSS functionality using VML via a .htc file - and it works great. However I've noticed that the http_referer value for pages viewed in IE8 is being returned as the location for pie.htc instead of the actual referring page and it was working just fine before the redesign. Firefox is tolerated as an alternative browser and for pages viewed in that browser all the http_referer values are as they should be. This is causing quite a headache for forms which redirect using this variable, as well as the logs which dump various environment variables to database for easy querying - and the guys who analyse the stats aren't remotely happy!
I have flagged this with the developer of CSS3 PIE and it's a mystery to him, but before I register a bug I wanted to see if it might be some failing of IIS or some setting I've missed in it (I'm using version 6 on Windows 2003). We have an Linux server with Apache as well for different purposes which I redesigned using the same technique and that doesn't seem to be displaying the same behaviour.
Does anyone have any related experience with PIE or any other .htc files on IIS which they were able to solve? Or is it some kind of IE8 bug that will never be fixed?
we experience the same issue. We removed it from the html. It could be an IE bug, I don't see any reason why the referer of the .htc should be the same as the page.
Is there anyway to target chrome on windows? I'm looking to do this because of the difference in border-radius rendering. Chrome on osx seems to work fine, only problematic in Chrome on Windows. Thanks.
If you really, really have to do this, I recommend this CSS Browser Selector script:
http://rafael.adm.br/css_browser_selector/
Of course, you'll have to update your site when the browser issue gets fixed. :p