3 ms·

Why? Their plan for bootstrap v5 at the moment is just some cleanup to fix mistakes they made and remove the jquery dependency. I dont see the reason for these

by tpetry 7y ago

Why? Their plan for bootstrap v5 at the moment is just some cleanup to fix mistakes they made and remove the jquery dependency. I dont see the reason for these goals to not support ie11. As much as i hate ie11 we have to still support it as its used in many businesses using our softwares

thawaway1837 7y ago
I think it makes sense to formally drop the IE dependency in versions sooner than when you’re making changes that actually break IE. Besides, replacing jquery May indeed be why they chose to drop IE right now. One of the biggest selling points of jquery, and one of the biggest contributors to its heaviness, is cross browser support including IE. As one of the comments in the linked issue points out, dropping IE11 means they can also start using basic JS constructs, like Array.prototype.forEach.
- uk_programmer 7y ago
  > As one of the comments in the linked issue points out, dropping IE11 means they can also start using basic JS constructs, like Array.prototype.forEach. Array.prototype.forEach is supported from IE9. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach#Browser_compatibility https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... EDIT: It is the nodelist api that isn't supported in IE. Not Array.prototype.forEach. Quite a lot of these basic JS constructs even if they are missing (most aren't in IE11) are very easily polyfilled. Personally I think it is fine that they drop support if they don't feel the need to support it. Bootstrap 4 isn't going to vanish.
  - marcthe12 7y ago
    And if you can polyfill, that is good way to drop support for ie11. Personally instead of support ie11 out of the box, have have create custom build or expect them to do polyfilling themselves. This way they can optimize for the remaining browsers.

3 ms·

Why? Their plan for bootstrap v5 at the moment is just some cleanup to fix mistakes they made and remove the jquery dependency. I dont see the reason for these

by tpetry 7y ago

thawaway1837 7y ago
I think it makes sense to formally drop the IE dependency in versions sooner than when you’re making changes that actually break IE. Besides, replacing jquery May indeed be why they chose to drop IE right now. One of the biggest selling points of jquery, and one of the biggest contributors to its heaviness, is cross browser support including IE. As one of the comments in the linked issue points out, dropping IE11 means they can also start using basic JS constructs, like Array.prototype.forEach.
- uk_programmer 7y ago
  > As one of the comments in the linked issue points out, dropping IE11 means they can also start using basic JS constructs, like Array.prototype.forEach. Array.prototype.forEach is supported from IE9. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach#Browser_compatibility https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... EDIT: It is the nodelist api that isn't supported in IE. Not Array.prototype.forEach. Quite a lot of these basic JS constructs even if they are missing (most aren't in IE11) are very easily polyfilled. Personally I think it is fine that they drop support if they don't feel the need to support it. Bootstrap 4 isn't going to vanish.
  - marcthe12 7y ago
    And if you can polyfill, that is good way to drop support for ie11. Personally instead of support ie11 out of the box, have have create custom build or expect them to do polyfilling themselves. This way they can optimize for the remaining browsers.