menu is wrongly placed at bottom
See original GitHub issueAre you reporting a bug or runtime error?
I think it’s a bug. menuPosition is default (auto). When there is no enough space for menu, it still appears in the bottom. The reason is: In Menu.js, this getMenuPlacement
will calculate a wrong menuHeight. In my situation, the menu will load data asynchrously, so it will display ‘Loading’ (loading message) in the menu first, then the data after it’s loaded. But getMenuPlacement
only calculates the height of ‘Loading’ and decides to put the menu at the bottom.
Expected
should calcuate the menuHeight when the data is loaded and decides the placement again.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5
Top Results From Across the Web
start menu in the wrong place - Microsoft Community
right click on taskbar, make sure it unlocked then press and hold left click on taskbar & move to bottom. 1 person found...
Read more >Drop-down menus appearing in the wrong place
I'm having issues with drop-down menus appearing in the wrong place. In particular, when I open up an application, whether it's a Finder ......
Read more >md-menu wrong position #1116 - angular/components - GitHub
when i click the button,the menu appear on bottom... All reactions.
Read more >Stop placing the menu button in the wrong corner
Stop placing the menu button in the wrong corner · It can hold lots of content · It doesn't take up much space...
Read more >Why is the Windows taskbar default at the bottom?
To my knowledge it was not a design issue but a technical one in win 95. The taskbar should be at the top,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@hasakilol got it. We’ll be looking at this in the very near future. We’re updating from Flow to Typescript and this type of behavior will be the next on the list.
In contrast, when using react-select, the placement is wrong and falls into
// 1: the menu will fit, do nothing
My Suggestion is: Maybe react-select should recalculate the placement when options change.