HTTPS-Only: Add UI to manage exceptions from about:preferences
Categories
(Core :: DOM: Security, enhancement, P3)
Tracking
()
People
(Reporter: julianwels, Assigned: julianwels)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-backlog1] )
Attachments
(2 files)
Most permissions and even ETP have some sort of UI to manage exceptions in about:preferences#privacy.
HTTPS-Only mode users will probably need something similar to manage their current exceptions. Also, some websites behave in unpredictable ways when upgraded to HTTPS, which may prevent users from accessing per-site or error-page UI to add an exception. In these cases, the user could always use the UI in about:preferences to exempt sites from there.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Next week is Proton hand-off so ideally I would look at this the week of March 8. Is that too late? Please let me know if I am a blocker.
Comment 5•4 years ago
•
|
||
Can you please share the Figma file with me?
And, why do we not offer "Exceptions" when enabled for Private Windows only?
Assignee | ||
Comment 6•4 years ago
|
||
Figma: https://www.figma.com/file/WJb99TrcbCStWpO2Etyl4H/HTTPS-Only-Mode?node-id=3%3A812
And, why do we not offer "Exceptions" when enabled for Private Windows only?
Permissions set in private browsing and 'normal' browsing are not shared. So exceptions set in this UI do not apply to private windows, and exceptions set in private windows don't show up in this UI. (Also everything gets deleted once you close a private window, so there's no need to manage stuff ^^)
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 8•4 years ago
|
||
Since copy and design are done, I think I can clear Arthurs needinfo request :)
Comment 9•4 years ago
|
||
Backed out changeset ccdbd76fc479 (bug 1662710) for Browser-chrome failures in toolkit/components/passwordmgr/test/browser/browser_exceptions_dialog.js. CLOSED TREE
Log:
https://treeherder.mozilla.org/logviewer?job_id=340970970&repo=autoland&lineNumber=32369
https://treeherder.mozilla.org/logviewer?job_id=340970634&repo=autoland&lineNumber=2637
Push with failures:
https://treeherder.mozilla.org/jobs?repo=autoland&group_state=expanded&revision=ccdbd76fc4799b318a00241e05f41c6e691c7110
Backout:
https://hg.mozilla.org/integration/autoland/rev/4f4f341eff6a89e87e9f22b2dc50458d5e868499
Comment 11•4 years ago
|
||
Comment 12•4 years ago
|
||
bugherder |
Comment 13•4 years ago
|
||
Is this worth calling out in firefox 90 release notes? (If yes, see https://wiki.mozilla.org/Release_Management/Release_Notes#Nomination_in_Bugzilla)
Assignee | ||
Comment 14•4 years ago
|
||
Release Note Request
Why is this notable: Exceptions were possible before, but could only be managed on a per-site basis, which many users didn't know.
Affects Firefox for Android: No
Links: Support Page (is not updated yet, but hopefully will be when 90 releases)
Updated•4 years ago
|
Description
•