You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem with the current docs sample is that the MenuBar is the direct child of a SplitLayout which directly adjusts its width. This hides the fact that in most cases, you need to give the MenuBar a width relative to its container (e.g. 100%), and also make sure the min-width is set to something that allows it to shrink (e.g. var(--lumo-size-m)).
We need to keep the SplitLayout in the sample to showcase the feature properly, but we should wrap the MenuBar in some other component – e.g. a HorizontalLayout – and provide the width and min-width appropriately. This will help developers figure out how to use the overflow feature.
If you think this issue is important, add a 👍 reaction to help the community and maintainers prioritize this issue.
The text was updated successfully, but these errors were encountered:
The problem with the current docs sample is that the MenuBar is the direct child of a SplitLayout which directly adjusts its width. This hides the fact that in most cases, you need to give the MenuBar a width relative to its container (e.g. 100%), and also make sure the min-width is set to something that allows it to shrink (e.g.
var(--lumo-size-m)
).We need to keep the SplitLayout in the sample to showcase the feature properly, but we should wrap the MenuBar in some other component – e.g. a HorizontalLayout – and provide the width and min-width appropriately. This will help developers figure out how to use the overflow feature.
If you think this issue is important, add a 👍 reaction to help the community and maintainers prioritize this issue.
The text was updated successfully, but these errors were encountered: