Open
Bug 1746173
Opened 3 years ago
Updated 11 days ago
Consider to fire background request within https-first for TYPE_SAVEAS_DOWNLOAD
Categories
(Core :: DOM: Security, task, P2)
Core
DOM: Security
Tracking
()
NEW
People
(Reporter: t.yavor, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
No description provided.
Reporter | ||
Updated•3 years ago
|
Assignee: nobody → lyavor
Comment 1•3 years ago
|
||
Currently we fire a background request for all TYPE_DOCUMENT
loads, which allows us to improve the usability of https-first. If the browser can not render a load of TYPE_DOCUMENT, we start downloading the file. To make sure we have consistent behaviour for all
of our downloads we should consider firing the same background request not only for load of TYPE_DOCUMENT
but also for loads of TYPE_SAVEAS_DOWNLOAD
.
Updated•3 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [domsecurity-active]
Updated•1 year ago
|
Assignee: t.yavor → nobody
Status: ASSIGNED → NEW
Updated•1 year ago
|
Flags: needinfo?(rezapuranmeisam4)
Updated•1 year ago
|
Flags: needinfo?(rezapuranmeisam4)
Updated•1 year ago
|
Flags: needinfo?(fbraun)
Updated•1 year ago
|
Severity: -- → S3
Comment 4•3 months ago
|
||
Not a blocker for landing HTTPS-First by default.
Updated•2 months ago
|
Blocks: https-first-release
Updated•11 days ago
|
No longer blocks: https-first-release
You need to log in
before you can comment on or make changes to this bug.
Description
•