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

> It would be unfortunate if we can't agree on a deterministic ordering since that seems like an interoperability nightmare.

Wow, you guessed it. Edge is suffering that interoperability issue today, as we don't even try to preserve source order at all (we order based on a generated mapping table that changes whenever we add newly supported attributes :). We **do** have plans to fix this by switching our attribute storage system over to source-order--but it's been on our backlog for at least 5 years now. Unfortunately, it's a big change for us which is why we haven't fixed it yet.

I'd be very supportive of having attributeChangedCallback order use something natural like source order--and we'd work on getting our implementation in line with that.

---
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-205529119