Closed
Bug 1483025
Opened 7 years ago
Closed 7 years ago
Search within Add-ons Manager stopped working
Categories
(Core :: DOM: Security, defect)
Tracking
()
VERIFIED
FIXED
mozilla63
| Tracking | Status | |
|---|---|---|
| firefox-esr52 | --- | unaffected |
| firefox-esr60 | --- | unaffected |
| firefox61 | --- | unaffected |
| firefox62 | --- | unaffected |
| firefox63 | --- | verified |
People
(Reporter: philipp, Assigned: jkt)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(2 files)
str in a new profile:
- open about:addons
- go to the extensions section
- type a query into the "search on addons.mozilla.org" field & hit enter
instead of opening a new tab with search results from amo nothing is happening and the browser console shows:
> Error: Required argument triggeringPrincipal missing within loadOneTab tabbrowser.js:1378:13
this regressed recently with bug 1362034.
| Assignee | ||
Updated•7 years ago
|
Assignee: nobody → jkt
| Assignee | ||
Comment 2•7 years ago
|
||
Comment 4•7 years ago
|
||
Comment on attachment 9001640 [details]
Bug 1483025 - add in principal for about:addons search.
:Gijs (he/him) has approved the revision.
Attachment #9001640 -
Flags: review+
| Assignee | ||
Comment 5•7 years ago
|
||
I filed a follow up for the search opening in a new tab: https://bugzilla.mozilla.org/show_bug.cgi?id=1484717
Pushed by jkingston@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a72f317a470e
add in principal for about:addons search. r=Gijs
| Assignee | ||
Updated•7 years ago
|
Blocks: require-triggering-principal
Comment 7•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Updated•7 years ago
|
status-firefox-esr52:
--- → unaffected
Comment 8•7 years ago
|
||
Verified as fixed in FF 63.0a1 (20180821100053) using Windows10x64 and MacOS 10.13.2.
I will attach a postfix video.
Updated•7 years ago
|
Status: RESOLVED → VERIFIED
Updated•7 years ago
|
Comment 9•7 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•