Closed
Bug 1500536
Opened 6 years ago
Closed 6 years ago
Add disclaimer/warning page when accessing the new "about:config" page
Categories
(Toolkit :: Preferences, enhancement, P3)
Toolkit
Preferences
Tracking
()
RESOLVED
FIXED
mozilla66
People
(Reporter: vcote, Assigned: Kammueller)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Warn the user about possible negative effects when changing settings in the "about:config" page. Add an "I accept" button for the user to proceed.
Reporter | ||
Updated•6 years ago
|
Summary: Add disclaimer/warning page when accessing the "about:config" page → Add disclaimer/warning page when accessing the new "about:config" page
Updated•6 years ago
|
Priority: P3 → P2
Updated•6 years ago
|
Priority: P2 → P3
Assignee | ||
Comment 1•6 years ago
|
||
Do we need to render the webpage in JS or would a redirection (from aboutconfig-landing.html to aboutconfig.html) be okay?
Flags: needinfo?(paolo.mozmail)
Comment 2•6 years ago
|
||
We need it to be in a single page, since eventually this page will be served from the well-known "about:config" URI.
Flags: needinfo?(paolo.mozmail)
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → matthias
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•6 years ago
|
||
Comment 4•6 years ago
|
||
Thanks! I'm quite busy this week but I'll see if I can find some additional time to review the patches, if not I'll be able to do the review next week.
Assignee | ||
Comment 5•6 years ago
|
||
No hurries =)
I've got plenty of time until next Wednesday (inclusive). After that my time will be pretty limited.
Pushed by paolo.mozmail@amadzone.org:
https://hg.mozilla.org/integration/mozilla-inbound/rev/da2e64513160
Added disclaimer page for the new about:config. r=paolo
Comment 7•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Updated•6 years ago
|
status-firefox65:
--- → ?
Updated•6 years ago
|
Updated•6 years ago
|
QA Whiteboard: [good first verify]
You need to log in
before you can comment on or make changes to this bug.
Description
•