-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Bug] #in-element
cannot directly render in to shadow-dom
#20641
Comments
NullVoxPopuli
added a commit
to NullVoxPopuli/limber
that referenced
this issue
Feb 4, 2024
This was referenced Feb 4, 2024
NullVoxPopuli
added a commit
to NullVoxPopuli/limber
that referenced
this issue
Feb 5, 2024
Repro: https:/NullVoxPopuli/ember-source-5.6-broke-shadow-dom |
I have a hunch this has to do with Glimmer-vm changes 🤔 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐞 Describe the Bug
😕 Actual Behavior
Used in this test:
Causes this error:
and doesn't actually render in to the shadow dom:
🤔 Expected Behavior
A clear and concise description of what you expected to happen.
🌍 Environment
I was able to get desired behavior at the cost of an extra div here:
(this change also makes the test pass, but again, at the cost of an extra div)
The text was updated successfully, but these errors were encountered: