Closed
Bug 1675420
Opened 4 years ago
Closed 4 years ago
Fix browser/base/content/test/about/browser_aboutCertError.js for Fission
Categories
(Firefox :: Security, task, P1)
Firefox
Security
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox84 | --- | fixed |
People
(Reporter: neha, Assigned: timhuang)
References
Details
Attachments
(1 file)
browser/base/content/test/about/browser_aboutCertError.js was re-enabled for Fission in bug 1643607 but has since been disabled again because of timeout.
|
Reporter | |
Comment 1•4 years ago
|
||
Tim, can you look into this as you've previously fixed it in bug 1643607? Thanks!
Flags: needinfo?(tihuang)
See Also: → 1643607
|
|
Reporter | |
Updated•4 years ago
|
Fission Milestone: --- → M6c
|
Assignee | |
Comment 2•4 years ago
|
||
Yeah, sure.
Assignee: nobody → tihuang
Status: NEW → ASSIGNED
Flags: needinfo?(tihuang)
|
|
Assignee | |
Comment 4•4 years ago
|
||
In this particular case, the BrowserReloadSkipCache() won't work in
Fission mode. The content prinicpal will be a Null principal and it
will end with a security error when trying to load a view-source:
URL with a null principal as the triggering principal.
In order to fix this issue, we change to use gBrowser.reloadWithFlags()
to reload the page.
|
||
Updated•4 years ago
|
Attachment #9186639 -
Attachment description: Bug 1675420 - Fix the timeout issue of browser_aboutCertError.js in Fission mode. r?johannh → Bug 1675420 - Cache the content principal before change the remoteness in BrowserReloadWithFlags() r?johannh
Pushed by tihuang@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/48c70dd7ad9f Cache the content principal before change the remoteness in BrowserReloadWithFlags() r=johannh
|
||
Comment 6•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox84:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•