Some TabContextMenu items are blank label at first time
Categories
(Firefox :: Tabbed Browser, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox67 | --- | unaffected |
firefox67.0.1 | --- | unaffected |
firefox68 | --- | fixed |
firefox69 | --- | verified |
People
(Reporter: alice0775, Assigned: Gijs)
References
(Regression)
Details
(Keywords: regression, reproducible)
Attachments
(2 files)
(deleted),
image/png
|
Details | |
(deleted),
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details |
Reproducible: always
Steps To reproduce:
- Right mousedown on empty space of content area
- Keeping mousedown, move mouse pointer to tab
- Then, mouseup
Actual Results:
Some TabContextMenu items are blank label
Expected Results:
No blank label
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a1cfb4874e277b523330f3595ac138897b49f41a&tochange=028c0eff90a7ad121827f45040699bbca433c5e7
Regressed by:
028c0eff90a7ad121827f45040699bbca433c5e7 Brian — Bug 1523763 - Move tab context menu strings to FTL file loaded on-demand. r=Gijs,flod
Reporter | ||
Updated•6 years ago
|
Comment 1•5 years ago
|
||
Gijs, thoughts on how to address this?
Assignee | ||
Comment 2•5 years ago
|
||
I think we have a few options:
- detect mousemoves/mouseovers as well, which is a little sad-making, perhaps, from a perf perspective
- add fallback in onpopupshowing or oncontextmenu, which might cause a flash of unlocalized content, I guess?
- move from mousedown to mouseup on windows (and/or linux? mac context menus appear onmousedown...) and/or use both
- add some kind of complicated helper that intercepts an initial context menu showing, cancels it, and then re-opens it when l10n is ready
I'd be inclined to go for 2 or 3, but I'd like a second opinion. Jared, Dão, what do you think?
Comment 3•5 years ago
|
||
Can we add a capturing {once: true} mousedown event listener on the whole window and just initialize on that?
Assignee | ||
Comment 4•5 years ago
|
||
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #3)
Can we add a capturing {once: true} mousedown event listener on the whole window and just initialize on that?
Apparently I was confused and we already have a mouseover listener? I don't know off-hand why that wouldn't fire in the steps in comment #0...
Comment 5•5 years ago
|
||
The mouseover listener is only on the tabContainer. I assume holding down the right mousebutton while dragging it skips the mouseover event.
Assignee | ||
Comment 6•5 years ago
|
||
Updated•5 years ago
|
Comment 8•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Assignee | ||
Comment 10•5 years ago
|
||
Alice, can you confirm this is fixed for you?
Reporter | ||
Comment 11•5 years ago
|
||
Yes. It was fixed!.
No longer reproduced on latest Nightly69.0a1.
Build ID 20190603101337
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Assignee | ||
Comment 12•5 years ago
|
||
Comment on attachment 9069059 [details]
Bug 1555453 - use contextmenu event as backup to ensure we always localize the context menu, r?jaws
Beta/Release Uplift Approval Request
- User impact if declined: Broken context menu in some cases
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: n/a
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Very small frontend-only patch, still got lots of beta runway.
- String changes made/needed: nope
Assignee | ||
Comment 13•5 years ago
|
||
Marking verified per comment #11 - thanks Alice!
Comment 14•5 years ago
|
||
Comment on attachment 9069059 [details]
Bug 1555453 - use contextmenu event as backup to ensure we always localize the context menu, r?jaws
approved for 68.0b8
Comment 15•5 years ago
|
||
bugherder uplift |
Description
•