- From: Hayato Ito <notifications@github.com>
- Date: Tue, 23 May 2017 20:22:25 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 24 May 2017 03:23:00 UTC
> I guess another option is to get rid of the suppression but fire slotchange event only when the slot is inside a shadow tree. Then we wouldn't fire a slotchange on a removed slot element since that's not in a shadow tree. That might make this event a lot easier to understand & reason. That sounds reasonable option to me. +1 for that. I would like to mention that there is a minor backward incompatibility: - A slot which is not in a shadow tree no longer receive a slotchange even if we append a child to the slot. (it is known as *fallback content*) However, I think we can ignore this case in practical. No one is interested in this case, I guess. If someone is worrying about this backward incompatibility, please let us know that. -- 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-303607146
Received on Wednesday, 24 May 2017 03:23:00 UTC