Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520)

MutationObserver was explicitly designed to work that way, but I can't now recall the reasoning.
I think it might have been something along the lines that for consistency every setAttribute call should create a record. Conceptually there is after all a mutation: there is an old value replaced with a new one, and whether or not they are the same doesn't really matter.
And Custom elements should work the same way as MutationObserver.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/520#issuecomment-336574796