[Wayland] Bookmark popup can be misplaced
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox-esr102 | --- | fixed |
| firefox102 | --- | disabled |
| firefox103 | --- | disabled |
| firefox104 | --- | fixed |
People
(Reporter: stransky, Assigned: stransky)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-esr102+
|
Details | Review |
|
1.08 MB,
video/webm
|
Details |
Bookmark popup can be misplaced after some open/close.
| Assignee | ||
Comment 1•4 years ago
|
||
| Assignee | ||
Comment 2•4 years ago
|
||
| Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Set release status flags based on info from the regressing bug 1760276
| Assignee | ||
Updated•4 years ago
|
Comment 5•4 years ago
|
||
| bugherder | ||
Updated•4 years ago
|
| Assignee | ||
Comment 7•4 years ago
|
||
Comment on attachment 9283350 [details]
Bug 1777186 [Wayland] Use correct popup window to calculate parent fit r?emilio
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: Wrong popup placement on Wayland.
- User impact if declined: Wrong popup placement on Wayland.
- Fix Landed on Version: 104
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): We use a workaround to slow/flickering move-to-rect call. When popup window is placed inside toplevel one, it's safe to use plain move instead of move-to-rect.
But recently we use wrong popup to check the bounds so we may apply the workaround to wrong popup window. In this patch we fix that and use correct one.
Comment 8•4 years ago
|
||
Comment on attachment 9283350 [details]
Bug 1777186 [Wayland] Use correct popup window to calculate parent fit r?emilio
Makes life better for the distros with Wayland enabled by default. Approved for 102.2esr.
Comment 9•4 years ago
|
||
| bugherder uplift | ||
Updated•4 years ago
|
Comment 10•4 years ago
|
||
Hello Martin,
I can not reproduce the issue using the information from video in order to confirm the fix, I tested on Ubuntu 20.4 using FF build 104.0a1(20220629070023) with Wayland settings. Are there any other step that I can use in order to reproduce it? Does the issue still reproduce for you on latest Beta 104.
0b9 (https://archive.mozilla.org/pub/firefox/candidates/104.0b9-candidates/), or on ESR 102.2(https://archive.mozilla.org/pub/firefox/candidates/102.2.0esr-candidates/build2/)? Thank you.
Updated•4 years ago
|
| Assignee | ||
Comment 11•4 years ago
|
||
(In reply to Monica Chiorean from comment #10)
Hello Martin,
I can not reproduce the issue using the information from video in order to confirm the fix, I tested on Ubuntu 20.4 using FF build 104.0a1(20220629070023) with Wayland settings. Are there any other step that I can use in order to reproduce it? Does the issue still reproduce for you on latest Beta 104.
0b9 (https://archive.mozilla.org/pub/firefox/candidates/104.0b9-candidates/), or on ESR 102.2(https://archive.mozilla.org/pub/firefox/candidates/102.2.0esr-candidates/build2/)? Thank you.
It may be specific to my popup setup. Let's keep it as is then.
Description
•