Re: [w3c/webcomponents] Define order for attributeChangedCallback invocation? (#474)

> It's not just the parser. In Gecko, some attributes are shared across multiple elements, and those are stored in a separate list from the non-shared attributes; order is preserved for the non-shared attributes only. The sharing is a huge memory and performance win, unfortunately....

So you're saying if I do `el.setAttribute("x", "x"); el.setAttribute("y", "y")` for some values of `x` and `y` Gecko will have `el.attributes[0].name === "y"`?

Does the spec currently reflect this? I can't find it. The spec appends attributes to the list, as far as I can tell, and doesn't let you insert them at arbitrary positions.

Or is there another situation, besides `setAttribute` and besides the parser, which I am not thinking of?

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/474#issuecomment-205521078