-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Intl.NumberFormat V3 proposal? #488
Comments
tidoust
added a commit
that referenced
this issue
Feb 2, 2022
Requested in #488. Four entries as this proposal is divided into four individual specs (all at stage 3).
tidoust
added a commit
that referenced
this issue
Feb 2, 2022
Requested in #488. Four entries as this proposal is divided into four individual specs (all at stage 3).
No problem except we'll need to add one entry per spec. That was done in #489 but the problem is these individual entries are not full specs, and don't strictly follow the exact same format as full proposals, meaning that the extracted title is wrong for the time being, e.g.: Lines 1786 to 1813 in 68019a6
I'll fix that before releasing a new version of browser-specs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like
tc39.es/proposal-intl-numberformat-v3/out/numberformat/proposed.html
isn't a browser-spec right now, seebrowser-specs/src/data/monitor.json
Line 285 in a2b1f28
We have a BCD PR which proposes to add these spec_urls for new NumberFormat features which ship in Safari 15.4, see mdn/browser-compat-data#14786
The spec_urls are
Do you want to revisit adding this spec? If not, BCD will probably add this to our allowlist.
The text was updated successfully, but these errors were encountered: