Closed
Bug 1742368
Opened 2 years ago
Closed 2 years ago
Write `https-first` test where extensions opens a new `http` tab
Categories
(Core :: DOM: Security, task, P3)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
96 Branch
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | fixed |
People
(Reporter: ckerschb, Assigned: robwu)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Within Bug 1742351 we annotated browser_ext_tabs_create.js and always use https for opening the tab and then the matching mechanism.
Within this Bug we should write a test where the load starts out http but then matches https. In other words, we want a test for a real-world https-first upgrading scenario.
|
Reporter | |
Comment 1•2 years ago
|
||
Copying over comment from Rob from the Phab review:
We should have a test that checks the observed events of tabs.onUpdated (and probably also some webNavigation events). That can be done in a follow-up.
|
Assignee | |
Comment 2•2 years ago
|
||
|
||
Updated•2 years ago
|
Assignee: nobody → rob
Status: NEW → ASSIGNED
Pushed by rob@robwu.nl: https://hg.mozilla.org/integration/autoland/rev/67888a3f12c1 Add http cases in browser_ext_tabs_create.js with https-first r=ckerschb
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox96:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•