Closed
Bug 1403965
Opened 7 years ago
Closed 7 years ago
[OOP] The context menu is displayed in a wrong position after moving extension sidebar to right / left
Categories
(WebExtensions :: General, defect, P2)
Tracking
(firefox-esr52 unaffected, firefox-esr60 verified, firefox55 unaffected, firefox56 wontfix, firefox57 wontfix, firefox58 wontfix, firefox59 wontfix, firefox60 wontfix, firefox61 verified, firefox62 verified)
VERIFIED
FIXED
mozilla61
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox-esr60 | --- | verified |
firefox55 | --- | unaffected |
firefox56 | --- | wontfix |
firefox57 | --- | wontfix |
firefox58 | --- | wontfix |
firefox59 | --- | wontfix |
firefox60 | --- | wontfix |
firefox61 | --- | verified |
firefox62 | --- | verified |
People
(Reporter: mcoman, Assigned: mixedpuppy)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(3 files)
206.08 KB,
image/gif
|
Details | |
59 bytes,
text/x-review-board-request
|
kmag
:
review+
jcristau
:
approval-mozilla-esr60+
|
Details |
234.01 KB,
image/gif
|
Details |
[Affected versions]:
- Firefox Notes 1.8.0 rc2
- Firefox 56 and up
[Affected Platforms]:
- All Windows
[Prerequisites]:
- Have a Firefox profile with the latest "Firefox Notes" add-on version (1.8.0 rc2) installed.
[Steps to reproduce]:
1. Open the browser with the profiles from prerequisites.
2. Right click in the "Notes" sidebar.
3. Click on the "Notes" button from the sidebar.
4. Choose "Move sidebar to right / left" from the sidebar's dropdown menu.
5. Right click in the "Notes" sidebar and observe the context menu position.
[Expected result]:
- The context menu is displayed under the mouse cursor.
[Actual result]:
- The context menu is wrongly displayed in the other side of the screen.
[Regression Window]:
Last good revision: 392ed89ec2730a48d10b1cec741e86a242d28aa3
First bad revision: a625a2e9b3333a8e76982ea65f077cfded6ac224
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=392ed89ec2730a48d10b1cec741e86a242d28aa3&tochange=a625a2e9b3333a8e76982ea65f077cfded6ac224
[Notes]:
- If you move the sidebar back to the initial side the issue is no longer reproducible.
- The issue is no longer reproducible if you switch the sidebars.
- Attached a screen recording of the issue:
Reporter | ||
Updated•7 years ago
|
See Also: → https://github.com/mozilla/notes/issues/259
Reporter | ||
Comment 1•7 years ago
|
||
Kris, can you please take a look at this?
Flags: needinfo?(kmaglione+bmo)
Updated•7 years ago
|
Comment 2•7 years ago
|
||
Too late to fix this in 56.
Comment 3•7 years ago
|
||
Is it too late for 60 too? We started having user feedback about that one.
Comment 4•7 years ago
|
||
Hey David, should we up the priority of this / find an owner?
Flags: needinfo?(ddurst)
Assignee | ||
Comment 5•7 years ago
|
||
I don't think this is a webextension issue.
Updated•7 years ago
|
Assignee | ||
Comment 6•7 years ago
|
||
Correcting my last comment. Some positioning used for the context menu event is setup when the webext panel is loaded, so the context menu has incorrect coordinates. The bookmark/webpanel doesn't have the same issue, so I'll need to look into what is different between the two (I suspect though that the webpanel is not remote).
Assignee: nobody → mixedpuppy
Flags: needinfo?(ddurst)
Assignee | ||
Comment 7•7 years ago
|
||
Switching sides of the sidebar is done with the ordinal attribute. Once the sidebar is switched, the context menu has the prior screenX/Y values until something is done to the window (moving or resizing the window or resizing the sidebar fixes this). The issue here is lower level, gfx layer or dom.
Kris, any thoughts on this, or who should I talk to?
Flags: needinfo?(kmaglione+bmo)
Assignee | ||
Comment 8•7 years ago
|
||
Verifying again that event.screenX/Y are wrong as received in ContextMenu.jsm _setContext
- open sidebar on left, context click
**** coords 230 271
- move sidebar to right, context click
**** coords 212 293
- resize sidebar on right, context click
**** coords 1184 314
This is on osx (59 and nightly).
browser.tabs.remote.autostart = true causes the problem, if set to false context menus show in the correct location.
Flags: needinfo?(kmaglione+bmo)
Summary: The context menu is displayed in a wrong position after moving the "Notes" sidebar to right / left → [OOP] The context menu is displayed in a wrong position after moving extension sidebar to right / left
Assignee | ||
Comment 9•7 years ago
|
||
Fix for similar screen coordinate issues in Bug 1390445
https://searchfox.org/mozilla-central/rev/59a9a86553e9bfd9277202748ff791fd9bc0713b/toolkit/mozapps/extensions/content/extensions.js#3521-3523
See Also: → 1390445
Assignee | ||
Updated•7 years ago
|
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment 12•7 years ago
|
||
mozreview-review |
Comment on attachment 8969363 [details]
Bug 1403965 fix context menu position in extension sidebar,
https://reviewboard.mozilla.org/r/238108/#review243874
This looks ok to me but I'm not that familiar with this code. Somebody who knows the frontend code would be a better reviewer. Sorry!
Attachment #8969363 -
Flags: review?(bugmail)
Comment 13•7 years ago
|
||
mozreview-review |
Comment on attachment 8969363 [details]
Bug 1403965 fix context menu position in extension sidebar,
https://reviewboard.mozilla.org/r/238108/#review243880
::: browser/base/content/browser-sidebar.js:197
(Diff revision 2)
> +
> + let content = SidebarUI.browser.contentWindow;
> + if (content && content.updatePosition) {
> + setTimeout(() => {
> + content.updatePosition();
> + }, 1);
Why `1`? What happens if we use `0` or `Services.tm.dispatchToMainThread`?
Attachment #8969363 -
Flags: review+
Comment 14•7 years ago
|
||
What was the rationale for tracking this for 60?
Flags: needinfo?(mixedpuppy)
Assignee | ||
Comment 15•7 years ago
|
||
(In reply to Julien Cristau [:jcristau] from comment #14)
> What was the rationale for tracking this for 60?
It's fairly broken behavior in the ui, a fix should be put into 60.
Flags: needinfo?(mixedpuppy)
Assignee | ||
Comment 16•7 years ago
|
||
mozreview-review-reply |
Comment on attachment 8969363 [details]
Bug 1403965 fix context menu position in extension sidebar,
https://reviewboard.mozilla.org/r/238108/#review243880
> Why `1`? What happens if we use `0` or `Services.tm.dispatchToMainThread`?
I just went and tried both, neither work. In fact, 1 didn't work, also tried 10 and it was intermittent. I bumped it to 50 and that works.
As I recall, I initially tried with zero, it didn't work, tried it with 100 and that worked, then I bumped it down to 1. I probably forgot to build again (this file doesn't track well) when I tested that value.
Comment hidden (mozreview-request) |
Comment 18•7 years ago
|
||
Pushed by mixedpuppy@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/e2573db9d14e
fix context menu position in extension sidebar, r=kmag
Assignee | ||
Comment 19•7 years ago
|
||
STR:
1. load any extension with a sidebar
2. right click to open context menu
3. use sidebar dropdown to move sidebar to other side
3. right click to open context menu
4. repeat a few times
pass:
context menu always appears in sidebar where click occurred.
failure:
context menu appears on the opposite side from where the sidebar is.
Flags: qe-verify+
Comment 20•7 years ago
|
||
Backed out for failing browser chrome at browser/components/extensions/test/browser/test-oop-extensions/browser_ext_sidebarAction_runtime.js
Push that started the failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=e2573db9d14e05ccc90c80a5bab27a8db0d3c489
Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=175203576&repo=autoland&lineNumber=22986
Backout: https://hg.mozilla.org/integration/autoland/rev/681479cecc1f135ec182cd1ee8df3c53028d2934
Flags: needinfo?(mixedpuppy)
Comment 21•7 years ago
|
||
(In reply to Shane Caraveo (:mixedpuppy) from comment #15)
> (In reply to Julien Cristau [:jcristau] from comment #14)
> > What was the rationale for tracking this for 60?
>
> It's fairly broken behavior in the ui, a fix should be put into 60.
OK, I guess, but if this has been there since 56 the urgency right now is unclear to me.
Comment hidden (mozreview-request) |
Comment 23•7 years ago
|
||
Pushed by mixedpuppy@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/93d49d1a2688
fix context menu position in extension sidebar, r=kmag
Assignee | ||
Comment 24•7 years ago
|
||
patch updated and run through try the re-landed.
Assignee | ||
Updated•7 years ago
|
Flags: needinfo?(mixedpuppy)
Comment 25•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
Assignee | ||
Updated•7 years ago
|
tracking-firefox60:
? → ---
Updated•7 years ago
|
status-firefox-esr52:
--- → unaffected
Comment 26•7 years ago
|
||
Verified as fixed in Firefox 62.0a1 and Firefox 61.0b3. I will attach a postfix video.
Status: RESOLVED → VERIFIED
Comment 27•7 years ago
|
||
Updated•7 years ago
|
status-firefox62:
--- → verified
Comment 28•7 years ago
|
||
Please request uplift to esr60 if you think we should fix it there.
Flags: needinfo?(mixedpuppy)
Assignee | ||
Comment 29•7 years ago
|
||
Comment on attachment 8969363 [details]
Bug 1403965 fix context menu position in extension sidebar,
[Approval Request Comment]
If this is not a sec:{high,crit} bug, please state case for ESR consideration: Since esr is longer lived, it would be nice to fix this ux item.
User impact if declined: context menus appear in wrong location when users switch sidebar from side to side
Fix Landed on Version: 61
Risk to taking this patch (and alternatives if risky): low
String or UUID changes made by this patch: none
See https://wiki.mozilla.org/Release_Management/ESR_Landing_Process for more info.
Flags: needinfo?(mixedpuppy)
Attachment #8969363 -
Flags: approval-mozilla-esr60?
Comment 30•7 years ago
|
||
Comment on attachment 8969363 [details]
Bug 1403965 fix context menu position in extension sidebar,
ui glitch, fix verified in nightly and beta, approved for 60.1esr
Attachment #8969363 -
Flags: approval-mozilla-esr60? → approval-mozilla-esr60+
Comment 31•7 years ago
|
||
bugherder uplift |
Comment 32•7 years ago
|
||
Verified as fixed in ESR60
Updated•7 years ago
|
Updated•7 years ago
|
Flags: qe-verify+
Updated•7 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•