-
Notifications
You must be signed in to change notification settings - Fork 624
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
Conditional element causes runtime panic when used as breakpoint #7126
Comments
The panic is
That means that there's a circular dependency. For example: At least in case of the direct use (without wrapper), |
But shouldn't the wrapper with A workaround is to make the whole layout conditional:
I am not sure if this only works because of #407. Or is there another way to achieve the behaviour I want? In a nested layout tree, I want to use a vertical layout on small screens, and a horizontal on larger ones. |
Another workaround is to wrap the
I am not sure why it works, and also not if this is desired behaviour or if it will change. This does not work with the non-inherited Wrapper. |
I think you're right that your workaround only work because of #407. |
Thx for the insights. I think it is a great idea to keep both systems around. |
Bug Description
I tried to add a 'breakpoint' for a mobile screen inside a layout tree. I slimed down the example, but interstingly the panic only occures when the condition is inside a component.
Try to use the wrappers in the code below. Each wrapper causes a panic.
I also tried plastering
width: 100%
s,VerticalLayout
s andHorizontalLayout
s everywhere. Nothing helped.Reproducible Code (if applicable)
Environment Details
Product Impact
This bug blocks us from building a mobile friendly version (lower prio)
The text was updated successfully, but these errors were encountered: