Closed
Bug 1193339
Opened 9 years ago
Closed 9 years ago
[UX] Provide design for Control Center detail view when insecure password fields are present
Categories
(Firefox :: General, defect, P1)
Firefox
General
Tracking
()
RESOLVED
FIXED
Iteration:
43.3 - Sep 21
Tracking | Status | |
---|---|---|
firefox43 | --- | affected |
People
(Reporter: Paolo, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxprivacy] [ux])
We'll need an initial design of the subview shown in the Control Center when insecure password fields are present, for review.
Updated•9 years ago
|
Flags: qe-verify-
Flags: firefox-backlog+
Whiteboard: [fxprivacy] → [fxprivacy] [ux]
Updated•9 years ago
|
Priority: -- → P1
Comment 2•9 years ago
|
||
(In reply to Tanvi Vyas [:tanvi] from comment #1)
> I think Aislinn has a mock already.
Here's the mock. Tanvi - do you have any copy suggestions for the sub-panel or is what I have ok?
https://www.dropbox.com/s/x6bpn7w71icruyh/password%20final.png?dl=0
Paolo - the lock asset is in this folder:
https://www.dropbox.com/sh/b9k8vpir2tcllx2/AADcBOdgDEz3gSUSayWHIGMHa?dl=0
Flags: needinfo?(agrigas)
Comment 4•9 years ago
|
||
Hi Aislinn! Thanks for the mockups. It is great to see this happening! Below are some suggests for the copy.
For "Your login could be compromised" we could try:
a) "Your login information could be compromised"
b) "Your login data could be compromised"
And for "The login form fields on this page are not secure and your information could be compromised" we could try:
"The login data you enter on this page is not secure and could be compromised"
since I'm not sure if users will know what "form fields" are and the whole page is insecure (not just the login fields).
Comment 5•9 years ago
|
||
(In reply to Tanvi Vyas [:tanvi] from comment #4)
> Hi Aislinn! Thanks for the mockups. It is great to see this happening!
> Below are some suggests for the copy.
>
> For "Your login could be compromised" we could try:
> a) "Your login information could be compromised"
> b) "Your login data could be compromised"
>
> And for "The login form fields on this page are not secure and your
> information could be compromised" we could try:
> "The login data you enter on this page is not secure and could be
> compromised"
> since I'm not sure if users will know what "form fields" are and the whole
> page is insecure (not just the login fields).
Ok - how about for now we go with:
Main Panel: "Your login could be compromised."
Sub-panel:"The login information you enter on this page is not secure and could be compromised."
Comment 6•9 years ago
|
||
(In reply to agrigas from comment #5)
> Ok - how about for now we go with:
> Main Panel: "Your login could be compromised."
> Sub-panel:"The login information you enter on this page is not secure and
> could be compromised."
Sounds good!
Updated•9 years ago
|
Priority: P1 → P2
Comment 7•9 years ago
|
||
I think this bug actually blocks 1179961 (instead of depends on it). Since this is the UX bug and bug 1179961 is an implementation bug.
Updated•9 years ago
|
Status: NEW → RESOLVED
Iteration: --- → 43.3 - Sep 21
Closed: 9 years ago
Priority: P2 → P1
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•