Document our browser support list

That list looks good to me, but considering the upward trend of mobile, I think that we must consider support for mobile browsers using media queries.

http://gs.statcounter.com/#mobile_browser-ww-monthly-200912-201012

Except IE, different version of browsers have very little difference. Maybe only the browser-specified-css-rules changes.

Chrome - stable version is 14 now.
Safari - smaller than 5 is dropped everywhere, include jQuery http://docs.jquery.com/Browser_compatibility
firefox - 3.6 still not EOF, but 4.x have EOF already. stable version is 7.0

I'd say this conversation is pretty relevant: #1217788: Drop IE7 support in Drupal core

Its worth noting that one of the key points in that discussion is that we need to think about what browser versions people will be using 18 - 36months from now, not what they are using today.

== my 2 cents

We've got a handbook page for this, which needs updating based on whatever is decided in this issue. Linking it here for reference so we don't end up creating another one. :)

http://drupal.org/node/367318

Half year passed.

- Firefox 10 released. It's a ESR version. FF3.6 will be EOF in April (market sharing is less than 5% now).
- Basically, Drupal needs align to jQuery / jQuery UI (http://docs.jquery.com/Browser_compatibility)

(CSS Layout side views)
I think it only worth to test its browsers during development:
- IE8+
- Safari 5.0.x
- Firefox 10+
- Chrome Current - 1 version
- Opera Current - 1 version

A lot of Mobile Framework only supports WebKit Engine. So for mobile side, I'd say same to Safari 5 is okay.

Keeps it in mind: Drop firefox/Chrome 3,4,5,6,7..... 99.9% won't break the layouts.

Basically, Drupal needs align to jQuery

jQuery 2.0 is dropping support for IE8 and earlier. https://twitter.com/paul_irish/status/218395508018921472

This is not really a documentation issue. I think it's really a coding standards issue about deciding which browser versions we are supporting in our JS, CSS, and markup (at which point a documentation page can be updated with that information).

Most of this is about JS but there are a lot of CSS issues, as well as some form bugs (IE8-) and other kind of quirks. Moving to base system.

Related: #1645494: Allow core themes to display single-column on IE8: do not compensate for lack of media query support

Editing wording to be more neutral and current.

.

AFAIK, D8 is currently intended to support IE8+ in the sense of needing to work. However, per #1645494: Allow core themes to display single-column on IE8: do not compensate for lack of media query support, displaying a single-column layout is ok, and per #1649780: Remove first/last/odd/even classes in favor of CSS3 pseudo selectors, lack of zebra striping in admin tables is ok.

#10 is interesting. If someone wants to make a case that jQuery 2.0 is likely to be ready in time for D8 to use it, and offers enough compelling stuff, that we should drop IE8 support entirely, please do so. Same for #12: if there's a case to be made that IE8 support is hindering us, let's make that case by collecting a list of the issues.

Core does not support IE8 anymore: #1993322: [Meta] Drop IE8 support

So, what need we do here?

Looks like this issue started as a docs one, and was changed in #11 pending a final decision. #1787012-139: [policy, no patch] Write D8 JS against ECMAScript 5. Prevent errors with feature detection (drop IE8 support) has the final decision for IE8, so moving this back to docs.

At the end of the issue summary of #1787012: [policy, no patch] Write D8 JS against ECMAScript 5. Prevent errors with feature detection (drop IE8 support), I started a work in progress docs update to http://drupal.org/node/61509. Do we want to move that into this issue summary, and use this issue to refine it?

What documentation are we updating exactly?

I'm guessing at least http://drupal.org/node/61509 and http://drupal.org/node/367318. What else?

Changes in past few months
- Drupal is dropped IE8 now.
- Opera Desktop moving to Chromium Blink engine.
- Opera Mobile (Chromium based) is released and support for 2.3+ ( http://my.opera.com/ODIN/blog/opera-14-for-android-is-out )

Support following browsers are good enough:
- IE9+
- Safari 5.0.x
- Firefox Current - 1 version
- Chrome Current - 1 version
- Opera Current - 1 version (Chromium based only)

.

For information in the issue #1664268: Drop some browser specific prefixes this is the list of browsers we cared for:

Target Browsers:
IE: 11, 10, 9
Firefox: 31, 30
Chrome: 37, 36
Safari: 7, 6.1
Opera: 23, 22
iOS: 7.1, 7.0
Android: 4.4, 4.3, 4.2, 4.1, 4
IE Mobile: 10

** Notes: to maximize the support, I also ran a command includes Safari 5.1 & iOS 6 to compare the differences. Thankful, it has given same results :)

It's a bit crazy that we still haven't documented the browsers we support.

Seems like the list should be:

IE: 11, 10, 9
Firefox: Latest release, Latest Extended Support Release
Chrome: Latest release
Opera: Latest release
Safari OSX: Latest release
Safari iOS: Latest two releases (ios uptake has slowed)
Android: 4.4, 4.3, 4.2, 4.1, 4
IE Mobile: 10

It's going to be annoying to update the numbers every time a release happens but it feels too ambiguous otherwise. If we just say "Latest release" is there any guarantee that we've actually tested it? Maybe this should be versioned in the README, so when a new browser release happens we actually test it up and then update the README.

Can we update this list before D8 RC ?

Where do we document this list? Should it be on drupal.org somewhere or in a textfile in the repo?

We shouldn't have a file in the repo with that kind of informations until we have frontend testing.

There is already a doc page no? See #8

We have manually testing now, but not automated testing now. Should we wait until Drupal 8 is released to change this page? This is why I think it would be better in a repo...

@LewisNyman I agree that it should be in the README.txt (or wherever) in the repo but in order to deal with your question in #21 ("If we just say "Latest release" is there any guarantee that we've actually tested it?") properly we need front end testing first (see #24). The hurdle of manually testing all of D8 will be so large that no one will ever do it just because there is a new version of FF.

Is it well defined what we mean by "browsers we support" anyway? Which themes/features will work? As I'm sure everyone on this issue knows, any site will look different depending on which browser you look at it on...

True, we should define "support" as well. Everything should be functional, even if it doesn't look the same.

We should go about that like the others:

(http://quirksmode.org/presentations/Autumn2015/webplatforms_visma.pdf slide 42).

A-list browsers are the ones you guarantee the application to work in.
B-list browsers (optional) are the ones you consider likely to run the entire application and/or they lack a few non-essential features.
C-list browsers are all other browsers; you don’t make any guarantees, but they’ll at least be able to view the HTML.

I found a doc page and stubbed it with D8 stuff from #21
https://www.drupal.org/node/367318

I split off 8.0.x for actual versions as of release and the general policy. I could be wrong, please feel free to update but at least gets us started and a place to put it in reply to #23

As of #2390621-139: [policy, no patch] Update Drupal's browser support policy, this is documented 🥳