460338 - Rephrase Clear Private Data's "Authenticated Sessions"

Status: VERIFIED FIXED

(Firefox :: General, defect)

Description

[Johnathan Nightingale [:johnath]]

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.

Comment 1

[Johnathan Nightingale [:johnath]]

Attachment: Change to "Active Logins", update accesskey, rev entities

Comment 2

[Alex Faaborg [:faaborg] (Firefox UX)]

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

Comment 3

[Mike Connor [:mconnor]]

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.

Comment 4

[Johnathan Nightingale [:johnath]]

Landed.

http://hg.mozilla.org/mozilla-central/rev/98a09198ccc8

Comment 5

[Marcia Knous [:marcia]]

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

Comment 6

[Marcia Knous [:marcia]]

I have updated the relevant Litmus test cases to reflect this verbiage change.

Comment 7

[Marek Stępień [:marcoos, inactive]]

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.

Comment 8

[Johnathan Nightingale [:johnath]]

(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.