Hey Marc,
in the past few days I have stumbled across a problem in determining the
> Internet Explorer version from the user agent string
> when Internet Explorer decides to use compatibility mode. In this case
> IE11 is considered to be IE7 for example, which is a
> big problem in my case.
>
My understanding has always been that if IE decides to use compatibility
mode for IE7, it really uses a IE7 engine and thus the browsers should
really be treated as IE7. After all, I think at least that is the whole
point of the compatibility mode?
But then this should work as expected (i.e. Wt renders IE7 to a IE11
browser that pretends to be IE7) ?
> The browser is defined as IE7 then, although IE11 would be suitable. This
> can cause many different problems, as it does
> in my case (for example, IE uses compatibility mode for intranet addresses
> as a standard).
>
Does it? That's ASFAIK not the behaviour we see (that IE11 switches to
compatibility mode) for intranet addresses. But even if it does, it would
be bad idea to treat it as IE11 if it intends to render as IE7 ?
2. Setting the UA Compatibility meta tag for IE8 as well
> ========================================================
>
> When using IE9, the following tag is set by the Wt application:
>
> <meta http-equiv=\"X-UA-Compatible\" content=\"IE=9\" />
>
>
> Appropriate tags are also set for IE10 and IE11, but unfortunately it is
> not done for IE8. In that case, it appears to me the
> browser also falls back to compatibility mode, and thus to IE7 behaviour.
> I could not figure out a way to make that IE8 tag appear
> as by modifying two other blocks of code. Concerning some testing I have
> done today, this works perfect for my needs:
>
The actual purpose of setting these X-UA-Compatible headers is to select a
particular (older) rendering engine in a modern browser: for example we
will treat IE12 as IE11 since we do not know yet how IE12 might break
things.
In your mind, it seems that you want to force a browser that is through its
settings configured to assume a legacy engine, to use a more modern engine.
This is the opposite indeed of what the code tries to do.
>From all this, I can only infer that your browser behaves differently than
ours; are you aware of special configuration settings?
Regards,
koen
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
