Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #57301, comment 15


Ignore:
Timestamp:
12/15/2022 01:53:52 PM (2 years ago)
Author:
sergiomdgomes
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #57301, comment 15

    initial v1  
    2222
    2323But moving on to hypotheticals, you could make the argument that this will one day help Firefox < 40 users on Windows 11 (once it adds support for the UN flag emoji). But then you also need to consider that:
    24 - The failure mode (once the trailing commas are removed) is to **load an unnecessary polyfill without anything breaking**. That's what's happening on **every browser** right now because of the bug we're trying to solve. It's not ideal from a performance point of view, but it works, and Firefox < 40 / Edge < 12 users have much bigger performance issues elsewhere anyway. I can't overstate how this is not in any way, shape, or form, something we should be caring about.
     24- The failure mode (once the trailing commas are removed) is to **load an unnecessary polyfill without anything breaking**. That's what's happening on **every browser** right now because of the bug we're trying to solve. It's not ideal from a performance point of view, but it works, and Firefox < 40 / Edge < 12 users have much bigger performance issues elsewhere anyway. I can't overstate how this is not in any way, shape, or form, something we should be caring about given the level of usage of these browsers and the expectations of the users who run them.
    2525- **Core does not support those browsers**, and other things **will** fail. `wp-includes` has other scripts that will fail in Firefox < 40, and this will only get worse as time goes by.
    2626- Realistically, how many Firefox < 40 users can there possibly be on Windows 11?! That's a 7 year old browser on a 1 year old OS, which is not exactly a common use-case.