Closed
Bug 1058395
Opened 12 years ago
Closed 12 years ago
Use clearer language to describe the impact of disabling different content blocking
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: Unfocused, Unassigned)
References
Details
For mixed content blocking we say "Disable protection for now".
For tracking protection we say "Disable protection".
There is a difference - disabling content blocking is for the lifetime of that tab, while disabling tracking protection is until it's re-enabled again and affects all tabs.
Some people have found that the language used doesn't make that clear to them - the language difference is too subtle, which leads to either confusion or assuming they're the same.
So maybe we can find some clearer language to use here.
Flags: firefox-backlog+
Updated•12 years ago
|
Flags: qe-verify?
Comment 1•12 years ago
|
||
(In reply to Blair McBride [:Unfocused] from comment #0)
> For tracking protection we say "Disable protection".
This was intended to be "Disable protection for this site". Is that clear enough?
Comment 2•12 years ago
|
||
Just chatted with phlsa on irc. His feedback was that
"Disable protection for now" with mixed content is clear enough to indicate temporary disabling (see also https://bugzilla.mozilla.org/show_bug.cgi?id=1041748#c6)
"Disable protection for this site" for tracking protection is enough to indicated that the site is unblocked until the user re-enables it.
Comment 3•12 years ago
|
||
From https://bugzilla.mozilla.org/show_bug.cgi?id=1058348#c6 it looks like it is OK to close this bug since phlsa is indeed UX.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Target Milestone: --- → Firefox 34
Updated•12 years ago
|
Iteration: --- → 34.3
Updated•12 years ago
|
Flags: qe-verify? → qe-verify-
You need to log in
before you can comment on or make changes to this bug.
Description
•