22

IE is still widely used, especially in enterprise environments. One might be actually forced to use it. In this case, the banner becomes only a nuisance, because you just can't switch browsers as you'd wish. I don't think anyone needs to be actually reminded everytime that IE is bad and there are better solutions; it's perfectly possible they would really ...


21

I vote to leave Internet Explorer 11 supported in the current form. The first reason is, I occasionally use Windows RT, on which the latest browser is IE11, and there's no other way to install any other browser on that platform. (I still feel that my purchase of a first-generation Surface in 2012 is a great investment, and it's lighter than even my 2016 ...


20

So does microsoft.com:


19

As of early November 2019, support for IE 11 has been dropped from SE's official compatibility matrix. Edge is still supported, though I guess in 6-8 weeks I might ask about Edge (EdgeHTML) support in the era of everything being blink-based... if I'm feeling cheeky.


18

We are trying to block a scraper that is scraping against our terms & conditions. This bug was an unforeseen consequence of trying to ban them client side - not realizing that atob is not supported by IE 7/8/9 (and 10 in 7/8/9 mode). I am reverting the change and deploying as we speak. Meta is back to normal now... as is the rest of the network.


16

Winter Bash is disabled in IE. You'd only see black hats anyway: Hats black in IE 11 I have no idea what changed, but I can no longer reproduce this issue in IE. And this matches reports from other users who say that everything seems fine. So I have re-enabled Winter Bash in IE for the time being; I'm curious if other people are going to see broken hats.


13

First, we cannot support IE 8. If it works, great - if it doesn't, upgrade: at this point, you're three versions behind current, and likely running into problems elsewhere too. Second, make double-certain you're not dropping into "IE7 compatibility mode" when this occurs. I'm not accusing you of turning it on - I'm suggesting IE is turning it on in ...


13

Yes! I share your pain due to work IT policies. A good example of how this can be done is Github, which has a similar message with a helpful "Ignore" button. This is a great compromise:


12

This is fixed in the next build, which should roll out within a few minutes. Sorry 'bout that :-(


12

Stack Exchange supports Internet Explorer 10 and above. Anything below is not supported. No site should be supporting IE6 anymore in my opinion anyway. Change your browser (or if you can't, may God have mercy upon thy soul).


12

I feel your pain; the local devs would allow console in production code from time to time for some reason. As a workaround, just bring up the IE dev tools by pressing F12. This will define console and the button will work.


12

I can repro this at will and it causes all sorts of issues for me. Once I'm in compat mode, my tags look like crap Why do my favourite tags look screwy only on travel.se? and I can't use arrow keys to scroll after clickg a voting button https://meta.stackexchange.com/questions/110452/has-something-changed-recently-that-would-affect-focus-for-keystrokes . As ...


12

More important than what is supported by Microsoft is what is actually used by people browsing the Stack Exchange network. Considering the lag a lot of corporate standard browsers have and the laziness a lot of consumers apply to software updates it will be quite a while until something that's not supported anymore is not used anymore. If it were my ...


11

I wanted to comment on the answer to say "Me, too!" but on IE9, but because I was having the same problem (can't enter comments) I had to do it with an answer. SE then took my short answer and converted it to a comment, so great. But I wanted to say that for some reason I cannot even log in using Stack Exchange on FireFox 26.0. I am entering this answer ...


11

We changed to the UglifyJS2 compiler yesterday to eliminate the dependency on Closure in our environment. Why? Cause Java, that's why. We don't install Java on our build machines, it just happens to be there in a small way because we use TeamCity as our build system, so the agent itself is Java-based and contains a small JRE within. The conflict of required ...


10

HA!!!!!!!!!!! LESSON LEARNED: DONT USE WINDOWS 3.1 FOR USE WITH THE STACK EXCHANGE BUT: Supported Browsers Lemme try Google:


10

I have to agree with @Cyberharbalist. My employer dictates what version of IE I use and I have to have it in compatibility mode due to some internal applications I must use. If this change is not reversed, I will have to consider leaving SO as I cannot upgrade my work system for valid work reasons. This was a shortsighted change that doesn't reflect how non-...


10

To state it: IE 11 is still supported by the Manufacturer until 2025. The EOL is in 2025. The same date that Windows 10 support will be dropped from Microsoft. I don’t contest the support drop from SE, but any argument that it’s because it’s no longer supported by the manufacturer are not the real fact.


9

This ended up being a bug with the MVC Mini Profiler, which is active on Data Explorer. The MVC Mini Profiler tries to inject its stylesheet into the page as part of its initialization routine by creating (via jQuery) a <link> element from a string with rel and type attributes. It then attempts to set the href attribute to point to the stylesheet. IE ...


9

None specifically, yet. It's more a culmination of features that have been added over time that have been building up a lot of IE-specific clutter in our CSS and JavaScript and blocking other specific features that we simply cannot build while still supporting IE. For example, you might have seen this pull request pop up on Stacks recently. We also could not ...


7

You're viewing that particular site with Compatibility Mode enabled, which causes issues by bumping things down to near-IE 7 levels (IE 7 itself is unsupported). Disable it by clicking the broken document icon in the URL bar. For what it's worth though, the problem is caused by the text-indent: -999em on .profile-triangle which causes IE to apply some crazy ...


7

Given the nature of the link text - "free community promotion ads" - and the fact that it selectively applied to that link and not the preceding one, my money is on this being the effect of some ad-blocker or malware blocker, not a bug in IE proper.


7

It's because #question-header is defined to be too wide: .question-page #question-header { width: 980px; padding: 20px; } …where 980 + 20 + 20 equals a width of 1020 pixels inside of #content, which is only 980 pixels wide. This doesn't cause layout problems in the general case because #content has overflow: hidden, but when scrollIntoView ...


6

My problem is the same, but all the following solutions did not work for me. I tried the solutions offered in both of these: External JavaScript code failed to load "Stack Overflow requires external JavaScript from another domain" message Finally, my problem was solved by changing the DNS (google DNS). Just offer my solution for others who meet ...


6

We also offer free community promotion ads for open source projects and non-profit organizations. It is the same on all 3 sites (in Chrome). In IE7: The promo box is mysteriously missing: But when I click on May I promote here? I see:


6

There are many questions that are specific to Internet Explorer in general, or to more than single version. So it's not viable to blacklist internet-explorer tag (although many people would probably dream about it). The best way is to improve the tag wiki and state clear, when to use generic tag, and when to use version-specific tag. Of course it will work ...


6

Internet Explorer 10 support has been officially dropped, per this edit to the list of supported browsers from an SE employee. As such, this discussion is now moot.


5

This is being caused by a "IE8 Specific" page layout error and the effects created can be stopped by doing the following. To Stop compatibility view from recovering from page layout errors the Solution is simple.(although it took me awhile to figure out were the option was) Open "Tools" menu then go to "Internet Options". Under the "Advanced setting" tab ...


5

Fix will be rolling out shortly. There was a problem in the revisions.js script which did not go down the designated path in the reopen and close review queue task views. Update Turns out there were actually issues with the revision switcher in the reopen queue both while reviewing (which was fixed in .1133) and in the review results (fixed in .1134) ...


5

IE 9 is not officlally supported. See Which browsers are officially supported, and what else do I need? for more information.


Only top voted, non community-wiki answers of a minimum length are eligible