Change HTTPS Only Mode error copy to give the sense of "protection"
Categories
(Core :: DOM: Security, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox79 | --- | verified |
People
(Reporter: arthur, Assigned: ckerschb)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active][tor-P2])
Attachments
(7 files)
We got some feedback that the HTTPS Only Mode error page can look scary. Can we revise the copy to make it very concise, and give users the sense that "Firefox is Protecting You"? See attached image as one idea for how this might look.
The strings in https://hg.mozilla.org/mozilla-central/rev/ae277f656dc4#l28.3 look alright to me, but they do seem pretty verbose. I have noticed that similar error messages displayed for badssl . com pages have a "What can you do about it?" subsection or bullet points that allows the immediate subtext to be short without losing the additional explanation.
If the mockup is being considered, I think the title text could use some copy-editing since it gives me the "x is Watching You" vibes. Otherwise, I think the shortening of the subtext is a good start.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
I think this is what we were shooting for, but I am happy to update the text if we get to a conclusion.
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Comment 4•5 years ago
|
||
Arthur, the patch is ready to review and I think what we want. Can you help me get signoff on the string updates? Once approved, we could get it reviewed and landed. Thanks!
Reporter | ||
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Please see notes and questions, as well as a draft revision on the final page of the doc: https://docs.google.com/document/d/1ujx32a9dzlWxGHBNRMBKSaM9S92aKPVygm7M4ukYDEs/edit#bookmark=id.vc9yzcacmt3s
Comment 6•5 years ago
|
||
This message copy has been revised. Before I send it to legal, please take a look and flag any l10n concerns. Thank you! https://docs.google.com/document/d/1ujx32a9dzlWxGHBNRMBKSaM9S92aKPVygm7M4ukYDEs/edit#bookmark=id.v6j0j3khqdqp
Comment 7•5 years ago
|
||
No concerns on the content, but mostly on the length of the main button's label (Accept the Risk and Continue to Site
). I'd like to make sure the layout works if the translated text is significantly longer than English.
Assignee | ||
Comment 8•5 years ago
|
||
This is how it will look like in the end.
Comment 9•5 years ago
|
||
We use that same button copy on our Certificate messages so it should be okay? https://badssl.com/
Comment 10•5 years ago
|
||
(In reply to Christoph Kerschbaumer [:ckerschb] from comment #8)
Created attachment 9158310 [details]
firefox_detected_security_issue.pngThis is how it will look like in the end.
-"What could be causing this?" should be bolded.
-Can we also move it down one line to associate it with the bullet points (and dissociate it from the opening line)?
Thank you!
Comment 11•5 years ago
•
|
||
(In reply to Meridel from comment #9)
We use that same button copy on our Certificate messages so it should be okay? https://badssl.com/
That's only Accept the Risk and Continue
, isn't it?
Having said that, I realize we already have translations, so you can take a look at Dutch for example (+35%)
https://transvision.flod.org/string/?entity=toolkit/toolkit/about/aboutHttpsOnlyError.ftl:about-httpsonly-button-make-exception&repo=gecko_strings
Again, that's more a layout concern than content (unless layout can't do anything about it). If everyone is fine with a very long button on one line, I'm OK with it.
Assignee | ||
Comment 12•5 years ago
|
||
(In reply to Meridel from comment #10)
-"What could be causing this?" should be bolded.
-Can we also move it down one line to associate it with the bullet points (and dissociate it from the opening line)?
Sure.
(In reply to Francesco Lodolo [:flod] from comment #11)
That's only
Accept the Risk and Continue
, isn't it?
Yeah, that makes sense to me actually - thanks!
Comment 13•5 years ago
|
||
I think the mock-up in comment #8 looks pretty good!
I like how the top bullet point covers the most common scenario, while the less-likely one is explained in the bottom bullet point. It's a small change, and I think users will appreciate the implied distinction between the two cases.
Apologies for the ping. I will keep content like comment #1 and comment #13 in the forums next time.
Comment 14•5 years ago
|
||
Can we plug the Dutch version of "Accept the Risk and Continue to Site" into the design and see how this looks?
Comment 16•5 years ago
|
||
Thank you. I don't like how the button breaks to two lines on mobile. Let's shorten the button copy to: Accept the Risk and Continue
Can you please try this new copy in Dutch so I can see if the button on mobile looks okay? Thank you.
Comment 17•5 years ago
|
||
(I pulled the translation from Pontoon Machinery)
Comment 18•5 years ago
|
||
I just noticed the current version of the patch already has "Accept the Risk and Continue", so I think we can just keep it like that.
Comment 19•5 years ago
|
||
Ah right, thank you. Michael, this error message copy has been updated. I don't think any of the changes have legal implications but flagging for you just in case: https://docs.google.com/document/d/1ujx32a9dzlWxGHBNRMBKSaM9S92aKPVygm7M4ukYDEs/edit#bookmark=id.v6j0j3khqdqp
Thank you!
Assignee | ||
Comment 20•5 years ago
|
||
FWIW, this is how the final error page would look in production!
Updated•5 years ago
|
Comment 21•5 years ago
|
||
Looks good, thank you!
Comment 22•5 years ago
|
||
Comment 23•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 24•5 years ago
•
|
||
Verified fixed on Firefox beta 79.0b2 (20200630191632) and Nightly 80.0a1 (2020-07-01) (20200701093012) on Windows 10 and Ubuntu 18.04.4.
Updated•5 years ago
|
Reporter | ||
Updated•4 years ago
|
Description
•