Should ally.js support older browsers?

[rodneyrehm]

Browser support as of ally.js 1.0.1:

ally.js has been tested on IE10+, Android 4.4+ and iOS8+ alongside the latest desktop versions of Firefox, Chrome and Safari.

For me and my projects that's good enough. For future jQueryUI that is good enough, but for current jQuery to use ally.js we'd have to support IE8+.

This issue is here to collect your thoughts on the minimum browser version (specifically IE, but also Android WebView and iOS Safari) that ally.js should support. We're trying to assess where we should focus development time…

Simply comment with "IE8", "IE9", "IE10" (which means no change). If you see any other browsers (like UC Browser or Yandex Browser) in need of special attention, call for it.

[ginader]

Did you run your tests against the mentioned Browsers just to see where we're at? Maybe it's not "a whole lot" of extra work? Is it?

[rodneyrehm]

Did you run your tests against the mentioned Browsers just to see where we're at? Maybe it's not "a whole lot" of extra work? Is it?

not yet. not a bad idea, why did I not think of that?

[ginader]

👍

[braders]

"IE8"

To clarify, I don't mind if features don't necessarily work, but the library should degrade gracefully so that I can use ally.js and not worry about it breaking other scripts on older browsers. No fatal errors should be thrown.

I guess it would also be good to highlight in the docs any exceptions to the general browser support for each feature/ component.

[rodneyrehm]

To clarify, I don't mind if features don't necessarily work, but the library should degrade gracefully so that I can use ally.js and not worry about it breaking other scripts on older browsers. No fatal errors should be thrown.

@braders: How would you make an ES5 library not fail in an ES3 browser (without including the ES5shim) though? Simply overwrite all ally.* functions with no-ops?

I guess it would also be good to highlight in the docs any exceptions to the general browser support for each feature/ component.

@braders: Are ally.is.focusRelevant notes and ally.maintain.disabled notes examples of that, or did you have something else in mind?

[braders]

How would you make an ES5 library not fail in an ES3 browser (without including the ES5shim) though? Simply overwrite all ally.* functions with no-ops?

I'm thinking basic feature detection - If functions are used that simply don't exist in IE < 8 then break out of the relevant function. Something like

if( ! 'querySelector' in document) {
     return
}
//run the function in modern browsers

I guess it would also be good to highlight in the docs any exceptions to the general browser support for each feature/ component.

Exactly like that - Didn't notice that earlier. Great job.

[rodneyrehm]

I'm thinking basic feature detection - If functions are used that simply don't exist in IE < 8 then break out of the relevant function […]

I know the concept (and ally.maintain.disabled is doing that in case of MutationObserver on IE10). But since everything requires ES5, I would have to break out of everything, rendering the library completely useless on ES3 (… but not throwing any errors).

[braders]

I've actually just noticed 'ES5-shim' is listed as an implict dependency on the readme. I've not seen it mentioned on the website though (might have missed it). Maybe it should be?

Sounds like it would be a big effort to add ie8 + 9 support without the polyfill though and I can't see people much caring as long as it works if the polyfill in place.

[rodneyrehm]

I've actually just noticed 'ES5-shim' is listed as an implict dependency on the readme. I've not seen it mentioned on the website though (might have missed it). Maybe it should be?

I guess Getting started is a good place to repeat the "system requirements"…

Sounds like it would be a big effort to add ie8 + 9 support without the polyfill though and I can't see people much caring as long as it works if the polyfill in place.

The ES5 shim is only necessary for IE8 (ES5 compat table).

[braders]

👍 Sounds good