[remote-dbg-next] The context menu on dom inspector of tab which opened from about:debugging differs from normal dom inspector
Categories
(DevTools :: about:debugging, defect, P1)
Tracking
(firefox66 verified, firefox67 verified, firefox68 verified)
People
(Reporter: daisuke, Assigned: daisuke)
References
(Blocks 1 open bug)
Details
Attachments
(6 files, 3 obsolete files)
Assignee | ||
Comment 1•7 years ago
|
||
Assignee | ||
Comment 2•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Updated•7 years ago
|
Comment 3•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Comment 4•7 years ago
|
||
It seems that the issue only occurs when we attach events on iframe elements. If fixing the underlying issue is too complicated, let's simply do this.
Comment 5•7 years ago
|
||
Here is the fix for the markup view for instance.
Assignee | ||
Comment 6•7 years ago
|
||
This will be fixed after resolving bug 1519332.
Assignee | ||
Comment 7•7 years ago
|
||
Since the platform won't fix the event propagation, we fix this from devtools side.
I'll try with Julian's approach from now.
Assignee | ||
Comment 8•7 years ago
|
||
I have investigated the difference of both normal devtools and devtools-toolbox.
https://docs.google.com/spreadsheets/d/15p6gZ77QBaVvQzS8srHVXCAjZ3NqU7UT28olWnCYPqo/edit?usp=sharing
I will proceed with following approach.
Firstly, make context menu of devtools to show correctly. From result of investigation, the targets are MarkupView, ComputedView in Inspector and Storage. And I'd like to discuss about the rest of points such as show/hide the contentAreaContextMenu.
Assignee | ||
Comment 9•7 years ago
|
||
Assignee | ||
Comment 10•7 years ago
|
||
Depends on D17457
Assignee | ||
Comment 11•7 years ago
|
||
Depends on D17458
Assignee | ||
Comment 12•7 years ago
|
||
Depends on D17459
Assignee | ||
Comment 13•7 years ago
|
||
To control the context menu from outside.
Depends on D17460
Comment 14•7 years ago
|
||
Thanks a lot for the patches so far Daisuke! As discussed I'd like us to get more feedback for the last 3 patches in the queue. I think we can split the bug. Can you file a followup to "Hide default/webcontent context menu items in about:devtools-toolbox" and move the 3 last patches there?
My only other comment would be: do you think we can add a mochitest to check that the context menu of the markup view is correct?
Assignee | ||
Comment 15•7 years ago
|
||
Thanks, Julian!
I filed bug 1522400.
Also, yes, I'll add a mochitest for the context menu on markup view.
Comment 16•7 years ago
|
||
Comment on attachment 9038739 [details]
Bug 1515265: Hide the context menu on about:devtools-toolbox when target was not text input field. r=jdescottes!
Revision D17459 was moved to bug 1522400. Setting attachment 9038739 [details] to obsolete.
Comment 17•7 years ago
|
||
Comment on attachment 9038740 [details]
Bug 1515265: Hide unnecessary menuitems from the context menu. r=jdescottes!
Revision D17460 was moved to bug 1522400. Setting attachment 9038740 [details] to obsolete.
Comment 18•7 years ago
|
||
Comment on attachment 9038741 [details]
Bug 1515265: Move a logic which avoids to inspect to ContextMenuChild. r=jdescottes!
Revision D17461 was moved to bug 1522400. Setting attachment 9038741 [details] to obsolete.
Assignee | ||
Comment 19•7 years ago
|
||
Depends on D17458
Comment 20•7 years ago
|
||
Comment 21•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e51312da073f
https://hg.mozilla.org/mozilla-central/rev/635099091943
https://hg.mozilla.org/mozilla-central/rev/319ae34add89
Comment 22•6 years ago
|
||
I've verified this issue on latest Nightly 68.0a1, Firefox dev edition 67.0, release 66.0.1 => on all versions the issue won't occur.
Description
•