Open
Bug 1488509
Opened 6 years ago
Updated 2 years ago
[remote-dbg-next] Addon manifest URL is not working for remote Runtime Page
Categories
(DevTools :: about:debugging, defect, P3)
DevTools
about:debugging
Tracking
(Not tracked)
NEW
People
(Reporter: jdescottes, Unassigned)
References
(Blocks 2 open bugs)
Details
When connected to a remote runtime, we cannot simply open the manifest URL in a tab to display it, we will need something different.
Reporter | ||
Updated•6 years ago
|
Priority: P5 → P3
Reporter | ||
Updated•6 years ago
|
Blocks: remote-debugging-ng
Reporter | ||
Updated•6 years ago
|
No longer blocks: remote-debugging-ng-m1
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
I will give a few more details: - in a runtime page, each addon shows a Manifest URL link - clicking on this link should open the manifest for the addon in a new tab This feature is currently only working in This Firefox. It should work for remote runtimes (or be hidden). Note that after this bug was filed we: 1 - hid the addons from Remote runtime pages (because it was considered too buggy) 2 - made the viewport too narrow, so much that it hides the links even on the This Firefox page
Updated•6 years ago
|
Priority: P3 → P2
Reporter | ||
Comment 3•6 years ago
|
||
When enabling extensions for USB and network runtimes, we also hid the manifest URL for them. It is only shown for this Firefox now. Technically I think this lowers the priority on this issue, and we might downgrade it to P3 if we need to make room for more urgent bugs.
Updated•6 years ago
|
Priority: P2 → P3
Reporter | ||
Updated•2 years ago
|
Blocks: webextension-debugging
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•