-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: revert "prevent prematurely cloning light dom slot vnodes" #4454
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with this approach, the number of impacted customers was very low prior to this fix too.
❌ One or More Pre-release Checks Failed
|
❌ One or More Pre-release Checks Failed
|
❌ One or More Pre-release Checks Failed
|
Details
This reverts commit 1105823 (#4258).
The fix for #4446 is ready to go (#4452), but for 252 (Winter '25) I think it would be pragmatic to just revert #4258 entirely.
This will make the 252 behavior the same as 250. I think this is the right choice, because:
main
disconnectedCallback
– synthetic lifecycle already has plenty of bugs where it doesn't calldisconnectedCallback
, which mostly manifests as memory leaks rather than DOM nodes failing to render).Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
Yes, 252 behavior will go back to 250 behavior (
disconnectedCallback
not firing correctly in certain tricky cases with light DOM slot forwarding).