11–20 of 67 posts
Probably because of the new release of their layout engine. IE11 comes with trident 7 while all the previous versions use 6 or below. It might be causing the trouble with google. Probably that's why Google works well in compatibility view.
But the bug is that Google is broken in compatibility view and works properly when in standards view.
I'll tell you more guys. I've updated to windows 8.1 on my tablet a month ago through MSND subscription and Google search worked just fine. Looks like this problem appeared after public availability of Windows 8.1. So I believe it's something that Google or Microsoft should figure out.
Not saying this is malicious. Maybe just Google is doing something silly. Maybe Microsoft have slipped up on their compatibility-list-thingie (which is a horrible invention IMO).
Sometimes adding too many special cases in your code instead of having one "good enough" version for everyone will cause you a million problems you never saw coming. I've had more bugs come from special casing than any general, "run everywhere" code I've written.
I can easily see how both ends could be responsible for this problem, even at the same time.
"Hey, if we make Google uglier, maybe people will use Bing!" "Probably not, but let's mess with 'em anyway."
"Hey, if we make Google uglier, maybe people will use Chrome!"
"Probably, they are used to IE not working"
Not sure who had the slip-up, but evil works both ways :P
"Hey, if we make Google uglier, maybe people will use Bing!" "Probably not, but let's mess with 'em anyway."
Earlier quoted context omitted.
but what is this setting ? it doesn't look like an UA switcher.
For a site like Google, I see no reason why Microsoft should have put it into compatibility mode- I have to assume that Google does testing on IE and any bugs should have been addressed quickly by Google. Furthermore, by using compat mode, the only way for google.com to use newer features in IE is to ask Microsoft to take it off the compat list then push an update to all IE browsers. In general, this compat list shou…
Unfortunately, we see otherwise during our compat testing here at Microsoft on many occasions.
So nobody @ MSFT has access to Google.com before shipping off the product. Given that a typical engineer is so addicted to 'googling' all through the day, this would've been noticed.
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 something MSFT pushed out as a compatibility list update around the general availability of 8.1 is causing this.
Earlier quoted context omitted.
For a site like Google, I see no reason why Microsoft should have put it into compatibility mode- I have to assume that Google does testing on IE and any bugs should have been addressed quickly by Google. Furthermore, by using compat mode, the only way for google.com to use newer features in IE is to ask Microsoft to take it off the compat list then push an update to all IE browsers. In general, this compat list shou…
"For a site like Google, I see no reason why Microsoft should have put it into compatibility mode- I have to assume that Google does testing on IE and any bugs should have been addressed quickly by Google." Unfortunately, we see otherwise during our compat testing here at Microsoft on many occasions.
"Hey, if we make Google uglier, maybe people will use Bing!" "Probably not, but let's mess with 'em anyway."
Unless it was google.. "Hey, if we make Google uglier, maybe people will use Chrome!" "Probably, they are used to IE not working" Not sure who had the slip-up, but evil works both ways :P
That's the solution posted in that thread. It's an IE problem.