# Internet Explorer Published articles for Internet Explorer. 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! ## The Firebase JS SDK Is Dropping Support For Internet Explorer DevFeed: [The Firebase JS SDK Is Dropping Support For Internet Explorer]() Original publisher: [Read original article]() Author: Christina Holland Published: 2022-05-26T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [SDKs](), [browsers]() Tags: [browsers](), [firebase](), [internet-explorer](), [js-sdk](), [sdk](), [update]() ### AI overview Starting with version 9.8.0, the Firebase JS SDK no longer supports Internet Explorer. The change enables newer library features such as ESM exports and may reduce bundle sizes. Users who need IE support can continue using versions earlier than 9.8.0, but those versions will not receive bug fixes. ### Source excerpt Starting with version 9.8.0, the Firebase JS SDK will no longer support Internet Explorer. ## A Brief History of TLS Certificates at Shopify DevFeed: [A Brief History of TLS Certificates at Shopify]() Original publisher: [Read original article]() Author: Charles Ng Published: 2020-05-14T15:46:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [TLS (Transport Layer Security)](), [certificates](), [Provisioning](), [Internet Explorer]() Tags: [certificates](), [internet-explorer](), [provisioning](), [shopify](), [tls]() ### AI overview Shopify describes its progression from manually provisioning a small number of TLS certificates to developing a fully automated system for encrypting storefront traffic at scale. The article covers early certificate management, Shopify Plus, operational drawbacks, and the automation project that began in 2015. ### Source excerpt In this post, we'll cover Shopify's journey from manually provisioning TLS certificates to the fully automated system that supports over 1M businesses. ## Calculating Color: Dynamic Color Theming with Pure CSS DevFeed: [Calculating Color: Dynamic Color Theming with Pure CSS]() Original publisher: [Read original article]() Published: 2019-12-05T00:00:00Z Content type: tutorial Language: en Sources: [Una Kravets]() Topics: [CSS](), [color](), [modern web development](), [Vanilla JavaScript]() Tags: [color](), [css](), [internet-explorer](), [javascript](), [properties](), [property](), [themes](), [variable]() ### AI overview This tutorial explains how to build dynamic color themes using pure CSS, custom properties, HSL values, and calc(). It demonstrates recreating common color transformations, including lightening, darkening, analogous, complementary, and triadic colors, without JavaScript or a CSS preprocessor for modern browsers. ### Source excerpt Did you know that you can build custom dynamic color themes without the use of JavaScript or a CSS preprocessor!? Read on! ## 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. ## What is HTTP/2? DevFeed: [What is HTTP/2?]() Original publisher: [Read original article]() Author: umer Published: 2016-04-23T00:00:00Z Content type: article Language: en Sources: [Code Ahoy - Articles]() Topics: [HTTP](), [servers](), [Web](), [Firefox]() Tags: [browsers](), [efficiency](), [firefox](), [hacks](), [http](), [internet-explorer](), [make](), [performance](), [protocol](), [security](), [servers](), [standards]() ### AI overview This article explains HTTP/2 as a major update intended to make the web faster and more efficient while addressing shortcomings of HTTP/1.1. It describes how HTTP/1.1 workarounds increased complexity and introduces Google's SPDY as a stepping stone toward HTTP/2. ### Source excerpt There are many reasons to feel excited about HTTP/2. It is the first major update of the HTTP protocol in 16 years! It was long overdue as the web dramatically evolved over the years. HTTP/2 is aimed at making the web faster and overcome many shortcomings of HTTP/1.1. HTTP/2 brings advancements to speed, efficiency, standardization and security. HTTP/1.1: Simple Protocol, Complex Workarounds HTTP was envisioned as a simple, application level, request-response protocol. Clients connect to servers and make HTTP requests asking for resource. Servers send response back and terminate the connection. HTTP/1.1 was released in 1999 to keep up with the performance demands of 90's brochure-esque websites. Its major improvement over its predecessor, the HTTP/1.0, was that it allowed a connection to be reused to send multiple requests and responses. This improves performance by eliminating connection setup overhead for each request. In 2004, Web 2.0 ushered in the new era of rich user experience and collaboration. It allowed users to interact with websites, leave comments, indulge in social sharing and enjoy many new features. New technologies emerged and many Web 2.0 websites like Wikipedia, Flickr and YouTube went on to become huge successes. While all this was going on, the protocol that ran it all, HTTP/1.1, was having trouble keeping up. The websites were growing significantly in size and complexity and it wasn't designed to handle that. So smart people did what they do best: they invented workarounds, so-called best practices, to overcome HTTP/1.1 limitations. Hacks like request pipelining, domain sharding, sprite sheets and data inlining were used to optimize performance. This added complexity on top of HTTP/1.1 and introduced regressions like unnecessary downloads, poor caching etc. Lack of standards meant that web developers had to deal with different browsers and versions. Ugh! I remember countless hours I sunk into tweaking websites to look great on both Firefox and ## 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. ## Adding Support for Search Engines to your Javascript Applications DevFeed: [Adding Support for Search Engines to your Javascript Applications]() Original publisher: [Read original article]() Published: 2013-06-19T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [JavaScript](), [mvc](), [Web Development](), [HTML5](), [Internet Explorer]() Tags: [html5](), [internet-explorer](), [javascript](), [mvc]() ### AI overview This article explains how to improve search-engine visibility for JavaScript applications, especially those using client-side MVC frameworks. It discusses pretty URLs, the HTML5 History API, server routing, and serving content for search engines, while noting that Google's JavaScript indexing changed the relevance of the earlier noscript-based approach. ### Source excerpt Important Update (May 25, 2014): Google has started parsing and indexing Javascript. The approach of this article is to use