Closed Bug 460338 Opened 11 years ago Closed 11 years ago

Rephrase Clear Private Data's "Authenticated Sessions"

Categories

(Firefox :: General, defect)

defect
Not set

Tracking

()

VERIFIED FIXED

People

(Reporter: johnath, Assigned: johnath)

Details

Attachments

(1 file)

From discussion with mconnor and Alex, this is the most jargon-y of the strings in that dialog, which is saying something.  Even people who know what "caches" and "offline website data" are might still not be able to clearly articulate what this one means.

Even just "Logged in sites" or "Active Logins" would be clearer, I think.

Should be nearly a one-liner, once we have a plausibly better string.

Should remember to update the support page linked to from the (?) icon too.
OS: Mac OS X → All
Hardware: PC → All
Assignee: nobody → johnath
Status: NEW → ASSIGNED
Attachment #344978 - Flags: ui-review?(faaborg)
Attachment #344978 - Flags: review?(mconnor)
Comment on attachment 344978 [details] [diff] [review]
Change to "Active Logins", update accesskey, rev entities

yay for user centric terminology as opposed to implementation centric terminology
Attachment #344978 - Flags: ui-review?(faaborg) → ui-review+
Comment on attachment 344978 [details] [diff] [review]
Change to "Active Logins", update accesskey, rev entities

To be fair, we just didn't think about the term enough, it was overly precise to a fault, rather than implementation-centric.
Attachment #344978 - Flags: review?(mconnor) → review+
Landed.

http://hg.mozilla.org/mozilla-central/rev/98a09198ccc8
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
verified fixed using  Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b2pre) Gecko/20081105 Minefield/3.1b2pre and  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081105 Minefield/3.1b2pre
Status: RESOLVED → VERIFIED
Flags: in-litmus?
I have updated the relevant Litmus test cases to reflect this verbiage change.
Flags: in-litmus? → in-litmus+
Correct me, if I'm wrong, but if this item only applies to HTTP Auth logins, then it would be confusing to users, as it won't clear cookie-based logins.
(In reply to comment #7)
> Correct me, if I'm wrong, but if this item only applies to HTTP Auth logins,
> then it would be confusing to users, as it won't clear cookie-based logins.

The difficulty of articulating that distinction (what about sessions authenticated by client certificates?) is why bug 463187 proposes to remove the checkbox, and clear them implicitly when cookies or history (or both) are cleared.
You need to log in before you can comment on or make changes to this bug.