# Internet Explorer Internet Explorer is a Microsoft web browser for accessing the Internet, with versions supporting multiple operating systems and developer-oriented ActiveX technologies. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Microsoft Retires Internet Explorer 11, Ending Support for All Internet Explorer Versions DevFeed: [Microsoft Retires Internet Explorer 11, Ending Support for All Internet Explorer Versions]() Original publisher: [Read original article]() Author: Stanko Published: 2022-06-16T00:00:00Z Content type: opinion Language: en Sources: [Stanko Tadić]() Topics: [Internet Explorer](), [browsers](), [Microsoft]() Tags: [browsers](), [internet-explorer](), [leaving](), [microsoft](), [modern]() ### AI overview An opinion piece reflects on Microsoft retiring Internet Explorer 11, which ends support for all Internet Explorer versions, and notes the shift toward modern browsers. ### Source excerpt End of an era. I started my career when IE6First time I wrote about IE6 was back in 2009. was a thing. And yesterday, Microsoft announced they are retiring IE11. With that, no version of Internet Explorer is longer supported. Over the years it seemed that we are doomed to support IE forever. We even planned celebrating when we finally don't have to. But today, it feels funny, nobody is celebrating. Modern browsers came in, slowly but surely overthrown it, leaving us with a pretty evergreen landscape today. So, IE, you weren't really a good browser, but it has been so long, so I bid you farewell! ## Internet Explorer 6 hacks, ten years after DevFeed: [Internet Explorer 6 hacks, ten years after]() Original publisher: [Read original article]() Author: Stanko Published: 2019-02-25T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [Internet Explorer](), [CSS](), [Web Development](), [browser]() Tags: [blog-post](), [browser](), [css](), [internet-explorer]() ### AI overview A retrospective republishes and contextualizes Internet Explorer 6 CSS hacks from ten years earlier, covering issues including box-model differences, disappearing content, unsupported sizing properties, PNG alpha transparency, and other browser-specific workarounds. ### Source excerpt Exactly ten years ago, on my my friend's blog I published a blog post about Internet Explorer 6 CSS hacks. I remembered it recently, and thought it would be really cool if I republished that same post, on it's 10th anniversary. I added comments about the hacks from today's perspective to give you some context. Cited parts are from the original post. Younger developers may find some things unbelievable, because browsers came a long way in the last ten years :) So here it is. Calculating width and height # All browsers (but IE) are calculating element's width (and height) using the following formula: width + padding + border-width While IE is using width and subtracts border width and padding from it. Which actually makes sense. There are lot of different solutions to normalize this, and this is the one I'm using: .element { border: 2px solid black; padding: 8px; /* this line will be read by all browsers */ width: 400px; /* but this one, due to inline comments will be skipped by IE */ width/**/:/**/380px; } Internet Explorer will skip the last line, and use 400px while everyone else will use 380px. This was before box-sizing was supported, and only browser using border-box was IE while other browsers were using content-box. Today, I think literally everyone are using border-box in their CSS reset. Disappearing text and images # This is one of the weirdest IE bugs. I never found out why it is happening. Randomly content will disappear, poof, and it is gone. Luckily, just add position: relative to the unfortunate element. To this day I don't know why this used to happen, and how position: relative fixes it. min-height and min-width # IE doesn't support these attributes, but you can use this hacky quick fix: .element { min-height: 500px; height: auto !important; height: 500px; } To be honest, I was looking at this one today, and I have no idea why and how this works. PNG Alpha transparency # To understand this hack you'll need to read about .htc scripts. There are a bunc ## Dropping IE8 Support: Consequences for JavaScript DevFeed: [Dropping IE8 Support: Consequences for JavaScript]() Original publisher: [Read original article]() Author: Patrick Gotthardt Follow Published: 2016-06-01T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [JavaScript](), [Internet Explorer](), [Web Development]() Tags: [babel](), [browser](), [debugging](), [frontend](), [internet-explorer](), [javascript](), [libraries](), [performance]() ### AI overview The article describes trivago's experience after dropping Internet Explorer 8 support. It reports that the change allowed developers to update dependencies such as jQuery, core-js, and Babel, adopt newer JavaScript standards, reduce testing and debugging overhead, remove compatibility workarounds, and improve performance in other browsers. ### Source excerpt When people hear about dropping support for a certain Internet Explorer version, they mostly think of all the CSS hacks and workarounds that could be removed as a consequence. However, dropping support for IE8 can have subtle, but profound effects on your JavaScript. ## Browser statistics June 2015 DevFeed: [Browser statistics June 2015]() Original publisher: [Read original article]() Author: Henning Spjelkavik Published: 2015-06-25T23:00:32Z Content type: article Language: en Sources: [Finn.no]() Topics: [browser](), [browsers](), [Mobile](), [Google Search](), [Web](), [Internet Explorer]() Tags: [android](), [apple](), [browser](), [desktop](), [devices](), [google](), [google-search](), [internet-explorer](), [iphone](), [mobile](), [mobile-web](), [statistics](), [web]() ### AI overview FINN.no's June 2015 statistics show that smartphones and tablets accounted for 62% of visits, while desktop and laptop visits accounted for 38%. Responsive mobile web was the largest FINN.no application category, and Apple led the browser-vendor ranking. ### Source excerpt In July 2013 more than 40% of the visits to FINN.no were from a tablet or a phone. Nearly one year later, in April 2014 - the share was 48%. What do you think has happened the last year? In April, Google rolled out their "mobile-friendly update", which boosts the ranking of sites that are mobile friendly in the Google search. We're clearly not the only one seeing the increased market share of mobile devices. How many visitors use a desktop or laptop? Our first graph shows the share of our users using a mobile phone, tablet or a desktop computer to access FINN.no, regardless of whether they use the traditional somewhat-responsive-desktop-web (www.finn.no), our responsive mobile web (m.finn.no) or an Android or iPhone app. 62% of our visits are now from a smartphone or a tablet. The traditional desktop/laptop has a market share of 38%. Which FINN.no application do people use? We have three major versions of FINN.no - the desktop, the responsive m.finn.no, and native apps. Our reponsive site is now the biggest! 14% of our visits are from our native apps, 42% from www.finn.no, and 44% from our responsive m.finn.no. Browsers First of all, let's take a look at the numbers of the browser vendors. The ranking is clear, Apple is the biggest, ahead of Google, Microsoft and Mozilla - and Opera is still in the top 5, representing more than an amazing 0.2% of our visits. Do you remember the "browser wars"? When IE 8.0 ruled the web? In case you wondered which browser is the biggest on the "desktop" here's the trend: The complete browser statistics, across all applications are as follows: It seems like a good idea to make sure your website works well with Safari! In case you still have Internet Explorer 9 as your favourite, it's still making it to the top 15, with a total share of 1.2% of our traffic, marginally behind Internet Explorer 10 with 1.4%. In 2015, poor IE8 is down to 0.3%. Thanks to Tobias Flatin, Chris Searle, Gregers G Rygg, Trond Hjorteland, and others for feedback ## Normalizing Cross-browser Flexbox Bugs DevFeed: [Normalizing Cross-browser Flexbox Bugs]() Original publisher: [Read original article]() Published: 2015-01-05T01:44:38Z Content type: tutorial Language: en Sources: [Philip Walton]() Topics: [bug](), [browser](), [Internet Explorer](), [Front end](), [CSS](), [Testing]() Tags: [also](), [browser](), [bugs](), [css](), [flexbox](), [front-end](), [github](), [internet-explorer](), [testing]() ### AI overview This tutorial examines cross-browser flexbox bugs encountered while building a sticky footer, focusing on Internet Explorer 10 and 11. It explains a browser-independent solution and offers recommendations for writing more compatible flexbox code. ### Source excerpt Way back in September of 2013, while testing my Solved by Flexbox project, I discovered a bug in Internet Explorer 10 and 11 that was preventing my sticky footer from actually sticking to the bottom of the page. I spent some time trying to work around the issue, but all my attempts failed. ## Strange Error When Downloading File in IE8 from SSL Site DevFeed: [Strange Error When Downloading File in IE8 from SSL Site]() Original publisher: [Read original article]() Published: 2012-07-15T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [ASP.NET](), [Caching](), [Internet Explorer](), [SSL](), [mvc](), [browser]() Tags: [article](), [asp-net](), [browser](), [caching](), [firefox](), [internet-explorer](), [mvc](), [ssl]() ### AI overview A troubleshooting article explains that IE8 fails to download files generated by an ASP.NET MVC backend from an SSL-protected site when cache-control headers prevent caching. It proposes overriding the default output-cache behavior for file downloads in IE versions below 9. ### Source excerpt Lorem ipsum dolor sit amet ## Internet Explorer not sending NTLM authentication DevFeed: [Internet Explorer not sending NTLM authentication]() Original publisher: [Read original article]() Author: Graham King Published: 2008-10-29T21:01:12Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Internet Explorer](), [Authentication](), [trust](), [Windows](), [Perl]() Tags: [authentication](), [internet-explorer](), [perl](), [security](), [software](), [trust](), [windows]() ### AI overview This article explains why Internet Explorer may refuse to send NTLM authentication when a Windows domain differs from the domain hosting a Twiki site. It recommends adding the site to Internet Explorer's trusted sites under Local Intranet settings. ### Source excerpt Taming IE's trust issues: A quick fix for cross-domain NTLM authentication. ## Javascript credit card generator fix DevFeed: [Javascript credit card generator fix]() Original publisher: [Read original article]() Author: Graham King Published: 2006-03-08T20:40:30Z Content type: release Language: en Sources: [Graham King]() Topics: [JavaScript](), [Internet Explorer](), [Firefox]() Tags: [credit-card](), [generator](), [javascript]() ### AI overview A mistake in a JavaScript credit card generator that prevented it from working in Internet Explorer and Opera was fixed. The author tested the updated generator successfully in Firefox, Konqueror, Internet Explorer, and Opera, and added a usage example. ### Source excerpt There was a mistake in the Javascript credit card generator, meaning it would not work on MS Internet Explorer or Opera. This has now been fixed, and I have tested it successfully on: - Firefox 1.0.6 - Konqueror 3.4.1 - Internet Explorer 6.0 - Opera 8.5.2 The archive now also includes an example on how to use the Javascript version (which seems the most popular).