You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It does expect certain, polyfillable, es5 features to be present for which you can use es5-shim for ie8
disturbs the flow of thoughts, currently:
For example events.on works in all browsers ie8+ but it uses the native event system so actual event oddities will continue to exist. If you need robust cross-browser support, use jQuery. If you are just tired of rewriting:
It does expect certain, polyfillable, es5 features to be present for which you can use es5-shim for ie8
over and over again, or you need a ok getComputedStyle polyfill but don't want to include all of jQuery, use this.
I was going to open a PR but thought to first ask if there is preference on where to move that line? I was thinking of moving the line to after the thought ends, possibly in parentheses:
For example events.on works in all browsers ie8+ but it uses the native event system so actual event oddities will continue to exist. If you need robust cross-browser support, use jQuery. If you are just tired of rewriting:
over and over again, or you need a ok getComputedStyle polyfill but don't want to include all of jQuery, use this.
dom-helpers does expect certain, polyfillable, es5 features to be present for which you can use es5-shim for ie8
or
...
over and over again, or you need a ok getComputedStyle polyfill but don't want to include all of jQuery, use this. (It does expect certain, polyfillable, es5 features to be present for which you can use es5-shim for ie8)
The text was updated successfully, but these errors were encountered:
In the README the insertion of the line
disturbs the flow of thoughts, currently:
I was going to open a PR but thought to first ask if there is preference on where to move that line? I was thinking of moving the line to after the thought ends, possibly in parentheses:
or
The text was updated successfully, but these errors were encountered: