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

I always thought that the MutationObserver was supposed to get called when either setAttribute or removeAttribute was called no matter what values were set. This was to allow the code to act upon the calls and not just on a value change. There are some, rare, occasions when the dev might need to know that the same value was applied. Maybe to refetch data from the server, maybe to redraw with recent values, etc.

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