Sub menus touching the bottom of screen do not expand upwards to show contents
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Confirmed
|
Medium
|
Unassigned | ||
unity (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
This is what someone told me.
I know the source of the problem. When an extension creates a Firefox popup menu, it has different position attribute values that determine the sub-menu placement.
https:/
Essentially, the sub-menu is being created underneath the parent menuitem. Since the parent menuitem is at the bottom of the parent menu and next to the bottom of the screen, there is no room for the new sub-menu to expand. It should be creating the menu from bottom to top instead.
You shoud report this issue as a "Global Menu Bar Integration" extension bug. They need to change the extension code, so the sub-menu grows upwards when created next to the bottom.
Meanwhile, scroll the parent menuitem to the middle of the screen, before acessing the sub-menu.
This is my bug I have to take out the Unity appmenn to get my bookmarks folders to expand from the menu bar bookmarks. When I have a folder that is on the bottom of the page it will only show about 6 bookmark without have to use the up and down arrows. Anyone else having to do this?
affects: | ubuntu → unity (Ubuntu) |
Changed in unity: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in unity (Ubuntu): | |
importance: | Undecided → Medium |
summary: |
- "Global Menu Bar Integration" + Sub menus touching the bottom of screen have scroll arrows even if there + is plenty of space on the screen |
summary: |
- Sub menus touching the bottom of screen have scroll arrows even if there - is plenty of space on the screen + Sub menus touching the bottom of screen do not expand upwards to show + contents |
I don't know who told you that, but they're wrong. In Unity, Firefox (and globalmenu- extension) have no control of the positioning or view of the menus. This is entirely controlled by the shell, and this is explained in the bug reporting guidelines (https:/ /wiki.ubuntu. com/MozillaTeam /Bugs) which we ask everyone to read before submitting a Firefox bug.
This needs reassigning to the correct component, but I'm 99.999% certain that this has already been reported anyway