Re: [w3c/webcomponents] Need "slotchange" event (#288)

If you do your own bookkeeping, you can replay. This is similar to attribute records without old values. But instead here we don't even provide a way to get to the old value (you have to store it yourself) and new value you have to get yourself too through a method.

Something akin to rAF could work, but e.g., @smaug and @dbaron have raised concerns in https://www.w3.org/Bugs/Public/show_bug.cgi?id=28876 that we already have too much activity unwinding at that point. We'd have to clearly define when it happens relative to the other activity that happens there, which is doable within the framework HTML provides, but per feedback it's unclear whether that framework will stand the test of time.

Furthermore, if you only do this for rAF you lose the generality of Shadow DOM working in any node tree. Suddenly some small part of it will only work correctly when chained up to a document that is the active document of a browsing context. That seems rather sad.

---
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/288#issuecomment-202823955