Labels |
Added:
?
|
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-05-07 19:14:02 |
Closed_By | ⇒ | HLeithner |
That doesn't mean we don't accept IE fixes but I would prefer not to keep the issue open.
So you're saying that we no longer need to ship ES5 files?
As already mentioned in the other issue that's a decision of george.
If you're unsure about that or cannot make the decision, please leave the issue open. Shipping ES5 means you support IE11
Status | Closed | ⇒ | New |
Closed_Date | 2020-05-07 19:14:02 | ⇒ | |
Closed_By | HLeithner | ⇒ |
reopened
waiting for a final response
There are differences between shipping es5 files and supporting. As in the motion we don't support IE11, that doesn't mean we have to make it harder for 3rd party developers. So it's a won't fix but can be fixed.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-05-08 10:35:34 |
Closed_By | ⇒ | HLeithner |
Why ship broken ES5 code then? I really don't get it
Status | Closed | ⇒ | New |
Closed_Date | 2020-05-08 10:35:34 | ⇒ | |
Closed_By | HLeithner | ⇒ |
We should try and fix this but it's definitely a lower priority issue. We should allow people to build frontend templates that work on IE11 even if we won't support IE11 in core anymore
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-04-09 04:42:32 |
Closed_By | ⇒ | C-Lodder |
Internet Explorer is not longer support in J4 by Production Department Motion PROD2019/005