- From: Surma <notifications@github.com>
- Date: Thu, 18 May 2017 06:40:35 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 18 May 2017 13:41:25 UTC
> When firing such a slotevent at slot's removal, the slot's assigned nodes will be always empty. Is slotchange for that really a useful event for web developers? Does web developers have a clean up task at this timing, although that assigned nodes is always empty? I think those scenarios exist, where cleanup is desirable and/or necessary. (E.g. Setting/Unsetting `aria-activedescandant`.) > In real worlds, does removing slots (or its one of ancestors) from the tree happen frequently? If that happens frequently and there is no use case for a slotchange event at this timing, I object to this change because the performance impact can't be ignored. I have no hard numbers, but from experience I’d say that performance does not need to be a concern here. Removing _slots_ from a Shadow Root is pretty rare – I have never seen or done it. Maybe @sorvell or @kevinpschaaf can provide additional insight. -- 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/447#issuecomment-302406601
Received on Thursday, 18 May 2017 13:41:25 UTC