Has the responsive design area for IE8 been considered since 2013?

Question

I still see issues here that relate to creating flexible design work for IE8, or gods banning IE7.

Due to the lack of awareness of Windows-related devices, I immediately thought it would be impractical to implement responsive design for IE8 due to the small number of mobile devices that will still run IE8 today. And just leave the sites as static 1024x768 for this particular browser, as there is no reason for a flexible design, with additional painful efforts that it requires, and a limitation of polysompleniya media requests, if more than 95% of the remaining share of IE8 browser works only on desktop computers with a safe screen width of 1024+.

If volume still matters, which mobile platform still uses IE8 browsers, this will require or justify a flexible design approach for them. Share useful relevant links.

PS: the context uses only standard mode, excluding the use of IE in compatibility mode or quirk mode.

Answer 1

So, after the investigation, I am going to answer my question with a few statistics that I was looking for:

No known active tablets or mobile phones use IE8, as far as I can tell. Event: The earliest Windows phones use the IE9 engine. Thus, laptops are excluded, IE8 is not used by smart mobile devices.

According to w3counter, statcounter, and analytics from 3 client sites, the IE8 browser share in March 2013, based on US sites, ranged from 5% to 11%. The average value is 8%.

The number of IE8 users using screen resolutions of 800x600 pixels or less today, according to three different sites that I studied in the USA, ranges from 0.6% to 1% of the total IE8 user base. Following the trends observed last year by Jacob Nielsen, “small screens for desktops and laptops are becoming rare”, fall to 1%: http://www.nngroup.com/articles/computer-screens-getting-bigger/ p>

Today, this leads to the average expectation that common IE8 users with a screen size of 800x600 or less are approximately 0.05%, a maximum of 0.1% if we enable IE7; lower than US IE6 total usage, accounting for 0.2% according to ie6countdown.com

Thus, the flexible design compatibility requirement below IE9 for IE7 and IE8 users is well worth the effort.

If you enable polyfill media queries or use Bootstrap, it works right away and then fine. But it definitely doesn’t cost more than a few hours to deal with numerous potential errors (a Google search for “bootstrap ie8” says that), since it no longer makes websites completely compatible with IE6.

While the site works in IE8 with a fixed design, which may be easier to implement, rather than trying to painfully make it respond to IE8 / IE7, this is enough for today.

Answer 2

I would agree, but simply. I don’t know what numbers are, but I’m sure there are many more notebooks with small displays in the wild that still run Windows XP and use IE7 / 8. One of the simple solutions to the problem of receiving media queries for working with old IE is css3-mediaqueries.js . This is a polyfill that makes media queries work with all browsers. You can use conditional comments to include them in your site.

Answer 3

Short answer: Depends on your requirements.

Long answer: Because I read a lot about responsive design, as well as the two books mentioned in the comments. I would answer your question as follows. Responsive design (in my opinion) basically has nothing to do with a mobile phone. It is more like what your page is “responding” to what your user / client uses to view your page. I know that some of these aspects have very deep roots in the idea underlying the Internet, as the exchange of information. Blind people also deserve an accessible network, and even if it has nothing to do with CSS, it still has something to do with a sensitive network, in my opinion.

So the question should be more like - how far should we go with adaptation when it comes to sensitive websites, and there is probably no real answer. The best way to get started with a new responsive (mobile first) web page - if I remember it correctly - is to create a page that works with the lowest possible resolution with the worst feature set that you are likely to support. In your case, I would say that IE8 on the screen is 320x240 (whoayy .. another question .. is the amount of responsive design that should be considered for mobile phones with a screen resolution of 320x240 as of 2015, for example). In the case of uber nerd fanblog, the lowest feature set can be a terminal with text-only support (for example, good days); - CSS? what is it? Cross-Shell Scripts ?! Whahoo ..) .. Although the fancy html5 video page may also require you not to use IE at all, because there is no clip, and your design depends entirely on that. There is also an aspect of the compound, for example. offline site / different speeds that can play a role. Such a responsive design is not only the appearance that I would say, but also the backend. For example. uber nerd fanblog http daemon sending plain text without any code / markup when there is no valid HTTP header.

I'm glad that you already answered your question and realized that it all depends on your user base / requirements.

This is not intended as an answer to the ops question, rather a clue for visitors.

@chriz "although responsive design is really designed for mobile devices." - I don’t think so .. A few weeks ago I had to adapt my css only for 4k + smart TVs .. also if you think about the current best practice with a mobile first gradually improving .. most responsive designs work to get more space on the screen and improve your page with things that don’t work on small mobile screens .. Responsive design is the result of the fact that these mobile devices try to use all these crappy desktop pages with zooming in / out ba and all these disappointments are not running things.