The technical information link on cert error pages is confusing

VERIFIED FIXED in Firefox 51

Status

Core Graveyard
Security: UI
P1
normal
VERIFIED FIXED
a year ago
a year ago

People

(Reporter: johannh, Assigned: Alessio, Mentored)

Tracking

unspecified
mozilla51
Bug Flags:
qe-verify +

Firefox Tracking Flags

(firefox51 verified)

Details

(Whiteboard: [fxprivacy] [good first bug])

Attachments

(1 attachment)

(Reporter)

Description

a year ago
This is a followup from Bug 1290927:

STR:

Go to https://wrong.host.badssl.com/

- click on Advanced -> SSL_ERROR_BAD_CERT_DOMAIN
- you can see some technical information now
- scroll up to show the SSL_ERROR_BAD_CERT_DOMAIN link again
- click the link, expecting to be taken to the technical info panel again
- nothing happens, because the panel is "hidden" now

Problem:

This is confusing. Hiding the panel has no use since it is already largely out of sight of the user when they clicked the link for the second time. No other information is hidden by showing the panel, why would the user want to close it?

Also I would argue that having what appears to be a link toggle between two non-apparent states is an anti-pattern.

My suggestion: Let's not close the technical information section after it was opened the first time.
(Reporter)

Comment 1

a year ago
Bram, what do you think? :)
Flags: needinfo?(bram)
(In reply to Johann Hofmann [:johannh] from comment #0)
> My suggestion: Let's not close the technical information section after it
> was opened the first time.

I see what you’re saying, and I agree. Let’s not close the technical information after you expand it. Instead, if you click on that link again, we simply go to the anchor again. Makes sense?
Flags: needinfo?(bram)
(Reporter)

Comment 3

a year ago
Makes sense! I'll get a patch! Thanks! :)
(Reporter)

Comment 4

a year ago
Thinking about it, this is an excellent good first bug. Here's how to solve it:

At https://dxr.mozilla.org/mozilla-central/rev/fe895421dfbe1f1f8f1fc6a39bb20774423a6d74/browser/base/content/aboutNetError.xhtml#425, simply remove the call to toggleDisplay() and instead always set the display style of `debugInfo` to "block".

If you're completely new to contributing to Firefox check out https://developer.mozilla.org/en-US/docs/Tools/Contributing to get started.
Flags: qe-verify+
Keywords: good-first-bug
Whiteboard: [fxprivacy] [good first bug] [triage]
(Reporter)

Updated

a year ago
Mentor: jhofmann@mozilla.com
(In reply to Johann Hofmann [:johannh] from comment #4)
> Thinking about it, this is an excellent good first bug. Here's how to solve
> it:
> 
> At
> https://dxr.mozilla.org/mozilla-central/rev/
> fe895421dfbe1f1f8f1fc6a39bb20774423a6d74/browser/base/content/aboutNetError.
> xhtml#425, simply remove the call to toggleDisplay() and instead always set
> the display style of `debugInfo` to "block".
> 
> If you're completely new to contributing to Firefox check out
> https://developer.mozilla.org/en-US/docs/Tools/Contributing to get started.

This is actually more complicated.  In order to comply with the requirements stated here https://bugzilla.mozilla.org/show_bug.cgi?id=1290927#c18,  it would be necessary to add another button next to the "Copy text to clipboard" labeled either "Dismiss" or "Cancel" to eliminate the technical info.
(Reporter)

Comment 6

a year ago
(In reply to Bill Gianopoulos [:WG9s] from comment #5)
> This is actually more complicated.  In order to comply with the requirements
> stated here https://bugzilla.mozilla.org/show_bug.cgi?id=1290927#c18,  it
> would be necessary to add another button next to the "Copy text to
> clipboard" labeled either "Dismiss" or "Cancel" to eliminate the technical
> info.

No. If you read this patch again Bram clearly states

> Let’s not close the technical information after you expand it.

Closing the technical info is not required, it's not visible to the user anymore anyway.

If you want to have such a button please file a follow-up bug where we can discuss the benefits.
(Reporter)

Updated

a year ago
Assignee: nobody → alessioscarapazzi
Status: NEW → ASSIGNED
(In reply to Johann Hofmann [:johannh] from comment #6)
> (In reply to Bill Gianopoulos [:WG9s] from comment #5)
> > This is actually more complicated.  In order to comply with the requirements
> > stated here https://bugzilla.mozilla.org/show_bug.cgi?id=1290927#c18,  it
> > would be necessary to add another button next to the "Copy text to
> > clipboard" labeled either "Dismiss" or "Cancel" to eliminate the technical
> > info.
> 
> No. If you read this patch again Bram clearly states
> 
> > Let’s not close the technical information after you expand it.
> 
> Closing the technical info is not required, it's not visible to the user
> anymore anyway.
> 
> If you want to have such a button please file a follow-up bug where we can
> discuss the benefits.

OK but when you click on the link you provided it opens a several page scroll thing of certificates to import with a "Copy text to clipboard" thing that there seems to be no way to dismiss I thought this was exactly the same issue.
(In reply to Bill Gianopoulos [:WG9s] from comment #7)
> (In reply to Johann Hofmann [:johannh] from comment #6)
> > (In reply to Bill Gianopoulos [:WG9s] from comment #5)
> > > This is actually more complicated.  In order to comply with the requirements
> > > stated here https://bugzilla.mozilla.org/show_bug.cgi?id=1290927#c18,  it
> > > would be necessary to add another button next to the "Copy text to
> > > clipboard" labeled either "Dismiss" or "Cancel" to eliminate the technical
> > > info.
> > 
> > No. If you read this patch again Bram clearly states
> > 
> > > Let’s not close the technical information after you expand it.
> > 
> > Closing the technical info is not required, it's not visible to the user
> > anymore anyway.
> > 
> > If you want to have such a button please file a follow-up bug where we can
> > discuss the benefits.
> 
> OK but when you click on the link you provided it opens a several page
> scroll thing of certificates to import with a "Copy text to clipboard" thing
> that there seems to be no way to dismiss I thought this was exactly the same
> issue.

clicking on something that opens something there is no way to dismiss.
(Reporter)

Comment 9

a year ago
> OK but when you click on the link you provided it opens a several page
> scroll thing of certificates to import with a "Copy text to clipboard" thing
> that there seems to be no way to dismiss I thought this was exactly the same
> issue.

No, that's a separate issue, but I understand what you mean. Feel free to open a bug.

> clicking on something that opens something there is no way to dismiss.

Technically you can simply click the [Advanced] button again to hide it, which is about as obvious as clicking the link.
(Assignee)

Comment 10

a year ago
Created attachment 8782602 [details] [diff] [review]
Disabled toggle in debugInfo on aboutNetError
(Assignee)

Updated

a year ago
Attachment #8782602 - Flags: review?(jhofmann)
(Reporter)

Comment 11

a year ago
Comment on attachment 8782602 [details] [diff] [review]
Disabled toggle in debugInfo on aboutNetError

Review of attachment 8782602 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good, thanks! There is a test that includes opening the technical info already, so we shouldn't need to add one.

Since I'm not a peer I'll let Gijs take another look at it. Thanks!
Attachment #8782602 - Flags: review?(jhofmann)
Attachment #8782602 - Flags: review?(gijskruitbosch+bugs)
Attachment #8782602 - Flags: review+
Attachment #8782602 - Flags: review?(gijskruitbosch+bugs) → review+
(Reporter)

Comment 12

a year ago
https://treeherder.mozilla.org/#/jobs?repo=try&revision=fff6f503ca7f
(Reporter)

Comment 13

a year ago
Great! Now this needs a run on our try server, to check if tests are still green. (https://wiki.mozilla.org/ReleaseEngineering/TryServer). I just did that for you, but in the future you might want to consider getting your own try access. I've also set the checkin-needed flag. This flag signals that we want the patch merged. If the try looks good, someone will come around and check it in for us.
Keywords: good-first-bug → checkin-needed
Iteration: --- → 51.2 - Aug 29
Priority: -- → P1

Comment 14

a year ago
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f0a49e4df7c7
Disable toggle in debugInfo on aboutNetError. r=johannh, r=Gijs
Keywords: checkin-needed

Comment 15

a year ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/f0a49e4df7c7
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
status-firefox51: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
QA Contact: paul.silaghi
Verified fixed FX 51.0a1 (2016-08-23) Win 7, Ubuntu 14.04, OS X 10.12
Status: RESOLVED → VERIFIED
status-firefox51: fixed → verified
(Reporter)

Updated

a year ago
Whiteboard: [fxprivacy] [good first bug] [triage] → [fxprivacy] [good first bug]
(Assignee)

Comment 17

a year ago
:johannh is this all good here? I've lost myself in all the flags :D Is there a wiki about flags or how does the flow works?
(Reporter)

Comment 18

a year ago
Alessio, everything is great. This is RESOLVED which means it's, well, resolved. Your code is currently in Nightly but will "ride the trains" on version 51 all the way to stable eventually. The VERIFIED flag just means that someone from QA looked at it to make sure this works as expected.

Don't worry about the whole Whiteboard stuff, that's mostly specific to the team that owns the component.

You can read up on the workflow again here if you want https://developer.mozilla.org/en-US/docs/Tools/Contributing (It's by the DevTools team but most of it applies to all of Firefox).

I absolutely encourage you to work on some more stuff that look interesting to you. The whole flow starts to make total sense once you solve a couple of bugs. :)

A good starting point for that is http://www.joshmatthews.net/bugsahoy/

Thanks for contributing!!!
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.