[wayland] Tooltips not constrained to screen if another popup is open
Categories
(Core :: Widget: Gtk, defect, P2)
Tracking
()
People
(Reporter: emilio, Assigned: emilio)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression, regressionwindow-wanted)
Attachments
(5 files, 1 external file)
STR:
- Hover over the hamburger menu on a maximized window. Verify the tooltip is moved inside the screen.
- Open the hamburger menu and repeat, see the tooltip outside the bounds of the screen.
Multiple people could reproduce this on #nightly
Comment 1•1 year ago
|
||
If tooltip and opened popups are not adjacent (tooltip is opened for different window that hamburger one), we can't use move-to-rect as Wayland protocol requires xdg-popup chain needs to be adjacent. I was told it might be possible to create tooltip as different temporary window type and still use move-to-rect (make parent the toplevel window and configure the popup differently) but I haven't explored the solution yet.
Comment 2•1 year ago
|
||
A workaround may be to always place tooltip inside Firefox toplevel window but we'd need to use popup X11 placement code and use toplevel window coordinates instead of screen coords.
Comment 3•1 year ago
|
||
Comment 4•1 year ago
|
||
Just a quick note to say that the issue is not limited to the hamburger menu and affects the first 3 icons from the right (hamburger menu, extension drop-down down, and the first extension icon).
Comment 5•1 year ago
|
||
Can you take a screenshot of the issue?
Thanks.
Comment 6•1 year ago
|
||
Comment 7•1 year ago
|
||
Comment 8•1 year ago
|
||
Comment 9•1 year ago
|
||
I also tested it on release Firefox 134.0 and it is the same. Therefore, the issue is not limited to Nightly.
Another consideration is that it doesn’t have to be the tool tip from the same popup.
STR
- Open hamburger menu
- Move mouse over icons
Comment 10•1 year ago
|
||
Even when they are not overlapping
Comment 11•1 year ago
|
||
Yes, it's because the tooltip belongs to toplevel window.
| Assignee | ||
Comment 12•1 year ago
|
||
From the regression range 1777269 looks like the main candidate.
FWIW a potential workaround might be to constrain them manually to the window, rather than the screen.
Comment 13•1 year ago
|
||
Set release status flags based on info from the regressing bug 1777269
Updated•1 year ago
|
Updated•1 year ago
|
Comment 14•1 year ago
|
||
Jonas, is it possible to create a xdg_popup for tooltip outside of the recently opened popup chain hierarchy?
Right now we don't use move-to-rect if tooltip doesn't belong to latest opened popup.
Thanks.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 15•1 year ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:stransky, since the bug doesn't have a severity set, could you please set the severity or close the bug?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 16•1 year ago
|
||
Emilio,
do you think it may be possible to place the tooltip (or any other popup) in bounds of Firefox toplevel window? It may need some plumbing in xul popup code where we may exchange screen size with Firefox main window code but it may be doable. It may also help us with the Wayland move-resize-hide-show stuff.
Actually I think we may even try to use that if Firefox toplevel window is maximized or the toplevel window is large enough. It will save us all the complications related to Wayland move-to-rect.
What do you think?
Thanks.
| Assignee | ||
Comment 18•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 19•1 year ago
|
||
Updated•1 year ago
|
Comment 21•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
Comment 22•1 year ago
|
||
The patch landed in nightly and beta is affected.
:emilio, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox141towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Issue is reproducible on a 2025-07-07 Firefox Nightly build on Ubuntu 22.
Verified as fixed on Firefox Nightly 143.0a1 and Firefox 142.0b5 on Ubuntu 22.
| Assignee | ||
Comment 25•1 year ago
|
||
I'd say probably not, it's somewhat edge casey / cosmetic.
Updated•1 year ago
|
Description
•