- From: Micah(phones) <notifications@github.com>
- Date: Tue, 25 Oct 2016 11:22:40 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Message-ID: <w3c/webcomponents/issues/592/256122854@github.com>
So to clarify, editing innerHTML should replace the text node, which *should* or *shouldn't* fire a slotchange event? Here's my understanding: MDN says about the `childList` element: >> Set to true if additions and removals of the target node's child elements (including text nodes) are to be observed. My naive understanding is that listening for slotchange is akin to using a MutationOberserver with `{childList: true, subtree: false}`? So, given an element containing a single TextNode: if setting its innerHTML to a single line of text is supposed to remove the old TextNode and add a new one, then it sounds like a MutationObserver with `subtree: false` would notice that, and that a slotchange event `should` fire. Of that's the case, do I need to file a bug report somewhere? Also seems like something that might need to be polyfilled. On Oct 21, 2016 5:14 AM, "Anne van Kesteren" <notifications@github.com> wrote: > If removing and then inserting a text node does trigger the change that > would indeed be a bug. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webcomponents/issues/592#issuecomment-255345461>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAXylhjWYz7FprZIazPRr6acJ29lOhfqks5q2JCRgaJpZM4Kc78C> > . > -- 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/592#issuecomment-256122854
Received on Tuesday, 25 October 2016 18:24:08 UTC