Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)

In Gecko one can handle attribute changes before the value has been added/changed/removed or after, depending on the case. And both are useful. The reason is mostly that BeforeSetAttr can still access the old value (which can be used for unregistering element from some data structures or cancelling loads etc.), and AfterSetAttr can then trigger whatever the new value should do. But I'm not sure if this is all just implementation detail. Would need to read through how `attribute change steps ` is used.

And at least the pr would make the spec inconsistent. Why only `change` is modified, why not also `append` and others?


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

Message ID: <whatwg/dom/pull/1176/c1490173078@github.com>