51–60 of 67 posts
Never assume malice when ignorance will do.
Someone broke something, probably not intentionally. Microsoft has a shady history here, Google has a shady history here (esp. with hostile treatment of Microsoft user agents with YouTube and Maps!), so in the absence of further evidence let's not point fingers.
Earlier quoted context omitted.
(Strike this, see note below) This problem just started in the last 24 hours - Google rendered fine and was my default search engine for over a month running the 8.1 RTM, and for a few months before that running the 8.1 Preview. This isn't MSFT's fuck up unless Google is doing feature detection and IE11 is presenting itself as not supporting some trivial HTML5 feature. Edit: I stand corrected - it looks like somethin…
Edit2: I'm not convinced of the above anymore. It doesn't look like the IE compat list is abnormal, but it could be a fluke interaction between Google and IE11. On the other hand, it's very strange that it suddenly occurred in the past day, when I've been running 8.1 release for over a month.
IE11 normally sends "Trident/7.0" and not "MSIE". Apparently Microsoft has added "google.com" to the Compatibility View List [1], which means IE11 now sends Google a User Agent that does include "MSIE". Google is interpreting this to mean it's an old version of IE, and sending the legacy view. You can manually disable the CVL, but then other sites that Microsoft has determined need old versions of IE won't work. I su…
Oversights can happen of course, but trying to blame Microsoft when the real cause was Google's bad browser sniffing is just weak.
IE11 normally sends "Trident/7.0" and not "MSIE". Apparently Microsoft has added "google.com" to the Compatibility View List [1], which means IE11 now sends Google a User Agent that does include "MSIE". Google is interpreting this to mean it's an old version of IE, and sending the legacy view. You can manually disable the CVL, but then other sites that Microsoft has determined need old versions of IE won't work. I su…
Click on "Known compatiblity issues". Notice the "Request tech details on your site" link.
Earlier quoted context omitted.
Does this mean microsoft never contacted anyone about compatibility list? To score some cheap points against a competitor you made your own product inferior. Good Luck with that attitude.
Again you're full of assumptions. We're very proactive in our compat outreach and we've had numerous conversations with sites like Google. Sites like Google are VERY aware of the CV list & the modes they're rendering in; it's not a surprise to them. Don't assume we're doing something nefarious when it's not the case. We have nothing to gain (and a lot to lose) by breaking one of the top web properties, even if they'r…
[1] If it had worked fine, it would never have been added in the first place. [2] Sites like Google are VERY aware of the CV list & the modes they're rendering in; it's not a surprise to them.
Those 2 together are suggesting Google knows problem all along and you have been working with them but they didn't fix the issue.
Earlier quoted context omitted.
Again you're full of assumptions. We're very proactive in our compat outreach and we've had numerous conversations with sites like Google. Sites like Google are VERY aware of the CV list & the modes they're rendering in; it's not a surprise to them. Don't assume we're doing something nefarious when it's not the case. We have nothing to gain (and a lot to lose) by breaking one of the top web properties, even if they'r…
You are not being consistent: [1] If it had worked fine, it would never have been added in the first place. [2] Sites like Google are VERY aware of the CV list & the modes they're rendering in; it's not a surprise to them. Those 2 together are suggesting Google knows problem all along and you have been working with them but they didn't fix the issue.
Earlier quoted context omitted.
You are not being consistent: [1] If it had worked fine, it would never have been added in the first place. [2] Sites like Google are VERY aware of the CV list & the modes they're rendering in; it's not a surprise to them. Those 2 together are suggesting Google knows problem all along and you have been working with them but they didn't fix the issue.
All I'm saying is that we go to great lengths to get companies OFF the CV list. If they're on it, it's for a reason. We can't update their code for them.
Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko
> If you currently use the x-ua-compatible header to target a legacy document mode, it's possible your site won't reflect the best experience available with IE11. For more info, see modern.ie. ?
If a site is on the list and they declare "edge", will they see the real ua string? What can someone on the list do to get the real ua string?
Earlier quoted context omitted.
I've tried switching to Bing (kinda forced on a Lumia) and also sometimes when I can't find what I'm looking for with google. Without fail I've found myself switching back from Bing almost instantly even if I'm stuck with IE.
You probably are in the US. Outside that, bing just cannot find anything. Anyway i also have a lumia but I set google as search engine in ie mobile