-
Notifications
You must be signed in to change notification settings - Fork 9
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 bug where ContextMenu
items were being improperly positioned
#3724
Conversation
Fixes #3723 . Issue appears to be with the following CSS style: hoist-react/kit/blueprint/styles.scss Lines 112 to 117 in c117858
By applying a
This is
An alternative solution would be to remove the
|
+ This seems like a just-gentle-enough change to qualify for a warning note vs. full-on breaking change section. + Tune up a few related doc comments around context menu classes.
Thanks for diving into this, Greg. I'm assuming since you setup the PR like this, you are thinking that the portal is the best overall option. (I am inclined to agree.) The style rules to ensure we don't overflow the viewport height are important for menus in general, as it is not difficult to end up with a big menu that can exceed the height of the viewport on a short screen or compressed window - we have seen this a number of times with the primary app menu, and it's one of those badly broken outcomes we really want to avoid (i.e. it looks really silly). We could consider not applying that rule to context menus in particular - those do seem less likely to overlfow vs. the main app menu - but if the portal approach works OK and we aren't seeing janky scrolling, etc. let's go for this. I'll merge it now and we can keep an eye out. |
Agreed - those were my thoughts as well. It would be nice if BP built overflow handling into |
Thanks for the research and for this fix, looks great! |
Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.
develop
branch as of last change.breaking-change
label + CHANGELOG if so.If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.