[w3c/webcomponents] Are document fragments "intert"? (#532)

Seems like document fragments are intended to hold inert node trees, that will become active when the fragment tree is inserted into live DOM. This would make it good for temporary structuring until finally ready to be inserted into DOM.

A couple questions:

1. Is are disconnected and connected callbacks called when custom elements are appended into a document fragment?
1. Can custom elements know when they are in a fragment in order to (or not to) do certain things?

Just wondering, because it seems like we want to prevent connected and disconnected callbacks from firing until the fragment content is inserted into actual DOM, as those callbacks are currently *the only* callbacks for initializing and de-initializing things when a custom element enters and leaves the DOM. We might not want to enact certain behaviors when the element is in a document fragment.


---
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/532