-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Update usage of EnumerableOwnProperty(Names) in the structured cloning algorithm #5374
Labels
good first issue
Ideal for someone new to a WHATWG standard or software project
topic: serialize and transfer
Comments
domenic
added
good first issue
Ideal for someone new to a WHATWG standard or software project
topic: serialize and transfer
labels
Mar 19, 2020
I would like to take it up. |
@AjayPoshak go for it! (Edit: note you need to be able to sign https://participate.whatwg.org/agreement.) |
I have one concern with agreement on this line
Does this mean that web developers can't contribute to WHATWG? |
It does not, but unfortunately getting it clarified is taking its time: whatwg/sg#67. I think given your employer (per your personal site) you can sign as individual. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Ideal for someone new to a WHATWG standard or software project
topic: serialize and transfer
https://html.spec.whatwg.org/#structuredserializeinternal step 26.4:
EnumerableOwnProperties got renamed to EnumerableOwnPropertyNames in Editorial: rename EnumerableOwnProperties to EnumerableOwnPropertyNames tc39/ecma262#1113, so the note referencing it is currently not right.
But, EnumerableOwnPropertyNames no longer reorders keys arbitrarily, as of Normative: make EnumerableOwnPropertyNames ordered tc39/ecma262#1793! So, I think we can use it directly, replacing step 26.4.1-2 with
The text was updated successfully, but these errors were encountered: