- From: Hayato Ito <notifications@github.com>
- Date: Tue, 23 May 2017 22:38:42 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 24 May 2017 05:39:19 UTC
I see. I am okay to disable `<slot>`'s functional APIs completely if it is not in a shadow tree. The sounds more consistent. As of now, the functional APIs which are visible to outside are: 1. `<slot>` can fire a slotchange even if it is not in a shadow tree, as I explained 2. slot.getAssignedNodes({flatten: true}): This might return non-empty if the slot has a child even if the slot is not in a shadow tree. I think that is all. We should update DOM Standard to disable 1 and 2. I am happy to update PR to DOM Standard if this is okay. I think this change doesn't have any practical impact on web developers. -- 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-303622768
Received on Wednesday, 24 May 2017 05:39:19 UTC