Evaluate the usefulness of toolkit/mozapps/extensions/test/mochitest/test_bug887098.html
Categories
(Toolkit :: Add-ons Manager, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: ckerschb, Assigned: tschuster, NeedInfo)
References
Details
Attachments
(1 file)
Within Bug 1670244 we are starting to perform IPC based Principal vetting when receiving a Principal from the Content Process. In turn, this hardening effort will effectively block content to load about:mozilla as requested by this line:
SpecialPowers.wrap(iwin).location.href = "about:mozilla";
Ultimately opening up the question if that test is still relevant. For now we will explicitly opt-out of perform IPC based principal vetting for the test, but we should re-evaluate how useful that test in it's current form is. Options are (a) re-writing, (b) removing.
Updated•5 years ago
|
Comment 1•2 years ago
|
||
With the InstallTrigger implementation being disabled everywhere (bug 1772901), is this test still useful?
Comment 2•2 years ago
|
||
We should get a peer to review, but I think yes, we can delete the test.
| Assignee | ||
Comment 3•1 year ago
|
||
The current state of InstallTrigger seems to be that the property exists (again, see bug 1950440), but it doesn't do anything (bug 1772901) and window.InstallTrigger === null.
I would like to remove this test now, because it's blocking the removal of the dom.security.enforceIPCBasedPrincipalVetting pref.
| Assignee | ||
Comment 4•1 year ago
|
||
window.InstallTrigger is just null nowadays and this test blocks the
removal of the dom.security.enforceIPCBasedPrincipalVetting pref.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
Description
•