| 20:54 | <shu> | @sffc @dminor i think we have a webcompat issue in CLDR 48: https://issues.chromium.org/issues/475851786 |
| 20:55 | <shu> | haven't had a chance to test Firefox yet, do you know what CLDR version Firefox is shipping with @dminor ? |
| 20:58 | <dminor> | We just landed an update to ICU78 in Firefox 147 (https://bugzilla.mozilla.org/show_bug.cgi?id=2000225), that's probably just going to release now. |
| 20:58 | <dminor> | That should be using CLDR 48. |
| 20:59 | <shu> | interesting, would be interested to hear if you run into any compat issues. we found this in pre-release testing |
| 20:59 | <shu> | our preference is for CLDR to roll back this change |
| 21:46 | <dminor> | Looks like Firefox is affected as well, I've raised this with webcompat and I'll file a bug. |
| 22:18 | <dminor> | For reference, here's the Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=2010411 |
| 23:39 | <sffc> | It's too late for CLDR 48 to "roll back" the change; they even already did a patch release 48.1 with minor fixes. It's possible a change could still be considered for 49.0 but the data freeze is in one week. |
| 23:44 | <sffc> | But, what about this change does @shuyuguo:matrix.org feel makes it more likely to break the web than other changes? Is it because we have evidence that it breaks the web, or is it based on a heuristic like being in English? |
| 23:46 | <sffc> | I see, there's a link to https://order.jetspizza.com/tx026 in the chromium issue. |