Skip to content
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

Step 13.3-4 in element definition should clarify the ordering #542

Closed
rniwa opened this issue Aug 11, 2016 · 3 comments
Closed

Step 13.3-4 in element definition should clarify the ordering #542

rniwa opened this issue Aug 11, 2016 · 3 comments
Assignees

Comments

@rniwa
Copy link
Collaborator

rniwa commented Aug 11, 2016

Steps 13.3 and 13.4 of the element definition algorithm doesn't explicitly state the ordering of Get other than implicitly defining it via a map.

We should either call it an ordered map, or explicitly state the order by which these properties are obtained as they're observable via Proxy objects or getter.

@rniwa
Copy link
Collaborator Author

rniwa commented Aug 11, 2016

@domenic @annevk

@domenic domenic self-assigned this Aug 11, 2016
@domenic
Copy link
Collaborator

domenic commented Aug 11, 2016

Makes sense, I was assuming with my JavaScript background that it was an ordered map, but I should definitely should clarify.

@rniwa
Copy link
Collaborator Author

rniwa commented Aug 11, 2016

Yeah, it was pretty obvious that's what you meant from JS semantics but I think it's good to be explicit in specifications :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants