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

Specify order of attributes for parser-created elements #1035

Closed
ayg opened this issue Apr 12, 2016 · 2 comments
Closed

Specify order of attributes for parser-created elements #1035

ayg opened this issue Apr 12, 2016 · 2 comments

Comments

@ayg
Copy link
Contributor

ayg commented Apr 12, 2016

I think the desired behavior is that it's unspecified, because in practice implementations do not have a consistent order, and I recall past discussions were that some of them aren't willing to change. This should be specified explicitly, because it could be argued that the order should obviously match the DOM order unless specified otherwise. Alternatively, if implementations are willing to converge, we could specify that they match some specified order (e.g., DOM order).

@domenic
Copy link
Member

domenic commented Apr 12, 2016

This was discussed in WICG/webcomponents#474. #1012 causes the order to become specified, as we concluded there; Gecko will not be able to comply, but they are currently non-compliant in other ways related to attribute order.

@ayg
Copy link
Contributor Author

ayg commented Apr 12, 2016

Thanks! Good to know. If the change to the spec has already been agreed upon and will definitely happen soon, I'll close this now.

@ayg ayg closed this as completed Apr 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants