- From: Hayato Ito <notifications@github.com>
- Date: Wed, 17 May 2017 22:34:08 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 18 May 2017 05:34:45 UTC
Okay. Then, let's continue the discussion. Basically, I don't have a strong opinion, however, I should be very careful for any changes which might have a performance impact. I think that we all are aware that getting rid of suppressing completely would simplify the spec and looks more consistent. I am aware of that too. So no need to repeat it, I think. My questions: - 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? - In real worlds, does removing slots (or its one of ancestors) from the tree happen frequently? If that happen 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. -- 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-302305131
Received on Thursday, 18 May 2017 05:34:45 UTC