-
Notifications
You must be signed in to change notification settings - Fork 77
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
"top level" {{#if}} not allowed #161
Comments
My assumption is that Glimmer tries to update / remove parts of the DOM, that already have been destroyed by vertical-collection. |
For the record: seems related to yapplabs/ember-wormhole#66 |
Yeah this is most likely due to the bounds of the component that’s being managed being manipulated in some weird way by Glimmer. However, VC already does dom manipulation at a low level, so if we can figure out what’s going on here I think we can provide a fix 🙂 I’m not going to have time until after the holidays most likely, but if you’d like to give it a shot @buschtoens ping me on slack, can help guide you on it |
I believe the issue relates to us removing our own custom bounds. |
This defuses html-next/vertical-collection#161 for now. More information about this: #514 (comment)
This defuses html-next/vertical-collection#161 for now. More information about this: #514 (comment)
Does anyone have further insight into this issue or should we close as |
I know this is a total edge-case, but I can't really work around it, so here goes: It is not possible to use a "top level"
{{#if}}
helper inside a vertical-collection.Initially, all is well. But if you scroll a bit and then toggle
renderAsParagraph
, you get this error:I stumbled upon this bug (?) while working on this PR: adopted-ember-addons/ember-light-table#514 (comment)
Do you see any chance of "fixing" this?
The text was updated successfully, but these errors were encountered: