-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) #191
Comments
Also see the issue #362. |
I specced this per #362:
(and similarly for connectedCallback). Please re-open or open a new issue/pull request if I got that wrong. |
What about newAncestor/oldAncestor? |
What about it? What is it? |
It's the argument passed to "insertion steps" / "removing steps". |
Why is that relevant here? |
Because why should that primitive not be exposed to connected/disconnected? |
Because connected/disconnected are different from inserted/removed, and we never discussed this previously, so you're proposing an entirely new feature? |
The only difference is that connected/disconnected require the element's shadow-host-including root to be a document, right? How does that change what context you might need? I guess I'm fine not exposing this for now, we can add it when there's a need. |
Sounds good. Feel free to open a new issue proposing it for wider discussion. |
Title: [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943)
Migrated from: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26943
comment: 0
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26943#c0
Olli Pettay wrote on 2014-10-01 09:43:50 +0000.
Per the current spec attachedCallback/detachedCallback explicitly aren't
called if the element isn't inserted into / removed from a document.
I think we want the callbacks to be called also in shadow DOM case.
The text was updated successfully, but these errors were encountered: