Re: [w3c/webcomponents] Why does attributeChangedCallback fire when a new attribute value is the same? (#676)

For consistency with mutation observers.

I don't understand why you'd have to add that check though, it's a fault of the caller.

-- 
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/676#issuecomment-336384695