Internet Explorer 10 triggers warnings from Google, WordPress

I just visited using Internet Explorer 10 in Windows 8.

Because I was signed into my Google account, my Google profile appeared in the upper right corner, along with a notification that there was something new for me to look at. Here’s what I saw when I clicked that notification:


Update to a modern browser… Hmmm, what could they possibly mean?

By the way, if you use the F12 Developer Tools to change the user-agent string to Google Chrome, the page displays just fine. Cheap shot, Google.

In a related development, WordPress is also getting confused by Internet Explorer 10. I have an up-to-date, self-hosted installation of WordPress. When I visit the Dashboard, here’s what I see:


Thankfully, the Browse Happy website isn’t shilling for any browser maker. It’s just designed to educate people who might be a revision or three behind.

Still, WordPress, you might want to fix that.

5 thoughts on “Internet Explorer 10 triggers warnings from Google, WordPress

  1. A more probable explanation is that the Google+ engineers were just lazy with their browser detection code and thought ‘IE10’ was ‘IE1’ or something. Nevertheless, they should update their browser detection code. Or better yet, use feature detection instead.

  2. It was even more funny when the marketing department at Microsoft in Denmark decided to launch a campaign to promote IE9. First of all they warned users with the latest Chrome or Firefox that their browsers were outdated, but if you visited the website with IE10, it also recommended that you updated to IE9. That’s what you get when you let the marketing department write the code for your website. 🙂

  3. It appears that WordPress will properly identify IE10 in my tests, but I’d be happy to fix whatever is causing this false positive. Could you go to and reply (or send to my email address included with this comment) what it returns? Thanks!

    If I had to guess, it’s possible that IE10 is operating in IE7 compatibility mode at the time that WordPress makes the check. We should also be able to account for that, but I’d like to know for sure that’s what is happening.

    Also, Browse Happy is WordPress, too. So we’re 1 for 2. 🙂

  4. This type of thing happens a lot, and it’s almost always just due to either a bug in the detection logic, or something being out of date in the logic.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s