Tab hover preview still visible with context menu opened in certain conditions
Categories
(Firefox :: Tabbed Browser, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | disabled |
| firefox128 | --- | disabled |
| firefox129 | --- | wontfix |
| firefox130 | --- | affected |
People
(Reporter: bmaris, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
Attachments
(3 files)
Found in
- Latest Nightly 130.0a1
Affected versions
- Latest Nightly 130.0a1
Tested platforms
- Affected platforms: Windows 11 and Ubuntu 22.04
- Unaffected platforms: MacOS 13.6
Preconditions
- Set
browser.tabs.hoverPreview.enabledastrueif not already set.
Steps to reproduce
- Open a few tabs
- Restart the browser
- Right click on the pocket button and hover over the tabs
Expected result
- The preview is not shown when context menu is opened
Actual result
- The tab hover preview is shown
Regression range
- Not sure yet if this is a regression or not, will check ASAP.
Additional notes
- I noticed that this only happens only once after the browser starts/restarts, I was not able to reproduce it in the same session more than once.
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Comment 4•1 year ago
|
||
| bugherder | ||
| Reporter | ||
Comment 5•1 year ago
•
|
||
This is still reproducible, now it's a bit worse since the hover will still be on even after navigating to any tabs.
The panel will be dismissed after clicking on a tab 2 times.
Build used: https://treeherder.mozilla.org/jobs?repo=mozilla-central&revision=ef22d470bb62b9898059a38214c0b95923d74e7c
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Updated•1 year ago
|
Comment 6•1 year ago
•
|
||
Interesting, this seems to only affect context menus (as opposed to panels) on Windows, because the attribute we check for on panel instantiation is absent on Windows for some reason. I opened bug1909694 to track this.
We only rely on checking for this attribute on the first load of THP (which is lazy-loaded) -- after initialization we can listen for events on other panels and context menus. This is the reason why this can only happen the first time that a tab is hovered over in a session.
Given that this is only possible to invoke in a very small corner case, is it necessary to track this as a P1? This feel more like P3 territory imo.
Updated•1 year ago
|
| Reporter | ||
Comment 7•1 year ago
|
||
We as QA don't set priorities to bugs, we only set the severity (which on its own is debatable, in this case S4 since it's kind of an edge case), engineering sets the priority of the bugs. But I agree that this is a corner case since its happening only once at the start of a session.
Updated•1 year ago
|
Description
•