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 ...
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.
I think it would be far simpler if there was an auto text identifying the browser in bug reports, something like:
This bug was submitted using: Google Chrome 19.0.1084.56 m / Win7 64.
Or better yet:
User agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0
No need to keep an (internal) list of supported browsers, and we ...
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.
What you have problems with is opening this image. Is a 4908x4408 px plot GIF image with 1,203.9 KB of data. Your browser either, runs out of memory due a memory leak (that we cannot help, report a bug) or your system is quite tight on resources (we cannot help either).
Normally accepted answers are shown on top. If the question asker accepts his own answer, this doesn't apply. Such an answer doesn't get pushed to the top. It is sorted just the same way as if it wouldn't be accepted, which is randomly among those answers with the same score.
This is not a bug but by design. If it really behaves differently in chrome, then ...
If you're looking for an alternative browser, then Software Recommendations is probably what you want, as noted by @Robert Longson. Be aware that SoftwareRecs.SE is pretty strict with questions, so be sure to read its help center and question quality guidelines before you post your question there.
If you want a general way of lowering CPU usage on a browser,...
Rob's comment (above) triggered "more thinking", and I quickly found the culprit: I use an 'add-on' in Firefox called AdBlockPlus. I've used it for years, and never had a problem with Stack Exchange sites. However, when I added stackexchange.com to its whitelist, the 'banner warning' disappeared.
So - question in an answer:
What changed? What switch ...
Honestly the large majority of of bugs on SE occur in all browsers or are obviously unrelated. SE is not a stable product, and bug reports are pretty easily resolved if they really are too localized, I'd rather err of the side of making bug reports easy. Unlike a ticketing system with one admin, we have a large community that's able to judge the value of ...
Are you trying to post a question here, on SO? If so, keep in mind that you should tell us what you're trying to achieve (with possibly some background information), a piece of code (don't paste ALL of your code, just a piece of it) which is relevant to your question. After explaining and showing your code you could add a question if you haven't done so ...
I don't use the tab title, so I'm not bothered by your examples. What does bother me though is that tags often chew up valuable space in Google results instead of showing more of the title:
"proper nouns - Why are the United States often referred to as ..."
"legislative process - How would the United States of America grant ..."
"marvel cinematic universe - ...
Firefox for Mobile is not officially supported and never has been on our network. It has always been in a state of "it works but may break" in our list of supported browsers on Meta (which in fact still mentions version 10.0.3 from back in 2012).
This is probably in the hands of the browser and out of the hands of the SE team.
The browser has not accessed that page before. It is not in the browser's history. Therefore, as far as the browser cares, that link has not been visited by it.
You sure did click on it, but the browser didn't handle it and as far as it's aware you've never been to that page ...
An OpenID identifier is a URL that represents an identity on the Internet. OpenID was invented by LiveJournal as a way for users to prove their control over a particular blog. It has since come to be used by Google, AOL, Yahoo!, Stack Exchange, and other web sites as a decentralized authentication platform to let someone with an account on one site (the "...
Unfortunately, we can't really support this browser.
Actually, navigating to the CSS site directly (https://cdn.sstatic.net/stackoverflow/all.css?v=62fd31659efc), and manually accepting the certificate seemed to fix my problem. Thanks for your help everyone!
While recommendation questions are off-topic in most Stack Exchange sites there is one that might be suitable if you're looking specifically for a browser add-on: Software Recommendations. It has pretty strict requirements for questions to be on topic so be sure to read its help centre and question quality guidelines carefully.
Outside of Stack Exchange ...
While HTTPS works (most of the time) it's not officially supported as yet. There are issues with getting certificates for the child meta sites (the current naming scheme means that SE need a certificate per site, rather than one certificate that covers a range of sites).
Therefore, any problems you get are likely to be transient.
Which browsers are officially supported is in Which browsers are officially supported? And what else do I need?. It shows that all of your browsers should be supported.
CSS files are downloading from https://cdn.sstatic.net. Check that you have marked its SSL certificate as trusted.
as @Popular Demand you are right, this about Font used by WebServices, this feature is possible to disabling in the Mozilla Firefox, notice preview of majorities from web sites is more than terrible ..., I'd have to live with buggy preview :-)
by default is checked option Allow pages to choose their own fonts with output to the screen