-
Notifications
You must be signed in to change notification settings - Fork 18
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
resolvedOptions order #163
Comments
|
Does Anba's ordering result in a normative change from the spec pre-#150? |
Normative-wise, yes, because [[NumberingSystem]] is now second instead of last. |
The spec which passed Stage 3 is in the following order
the order got changed accidentially while merging PR 150 then I just merged PR 165 to correct that accidental change. So I reopen this issue if we want to chagne the order. That need to be discuss and reach consensus in TC39 with a Normative PR |
@anba, could you explain why you say
I am not agree (nor disagree) with you. Just want to make sure we all understand the reasoning of that. Is that because that align with the access order of the information from the option bag? |
For example:
Yes, I think so. [1] Intl.Collator is an exception, because its Unicode extension properties [2] Intl.RelativeTimeFormat does not have |
This is a rehash of #30.
The ordering was fixed in 02584a5, but then reordered again in #150.
I wonder if the decision was intentional, since it makes
locale
come out second. This is observable at runtime.JSC currently still puts
numberingSystem
last andlocale
first.The text was updated successfully, but these errors were encountered: