Closed Bug 1194938 Opened 9 years ago Closed 9 years ago

Leave "run by" and "verified by" in "Secure Connection" dialog to "More Information"

Categories

(Firefox :: General, defect, P4)

Product:
Firefox
Component:
General
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: annevk, Unassigned)

References

Details

(Whiteboard: [fxprivacy])

These details are not helping our users and yet get a fairly complicated piece of UI. "More Information" already contains this information, exposing it more prominently is not worth it.
Whiteboard: [fxprivacy] → [fxprivacy] [triage]
Priority: -- → P4
Whiteboard: [fxprivacy] [triage] → [fxprivacy]
Blocks: 1188565
(In reply to Anne (:annevk) from comment #0) > These details are not helping our users and yet get a fairly complicated > piece of UI. "More Information" already contains this information, exposing > it more prominently is not worth it. To be clear, you want to get rid of the subview entirely unless if MCB is happening? With this information removed, then the subview would not contain any extra information over the main view. Unless if MCB is happening, then we have some button controls there.
I see why the "verified by" might not be helpful, but I think we should keep the "run by" to tell the users what company the website is run by and where they are located.
(In reply to Brian Grinstead [:bgrins] from comment #1) > To be clear, you want to get rid of the subview entirely unless if MCB is > happening? Yes. Tanvi, if not already present, we could add it to "More Information". And if it's really that vital, we should just include it in the main view (only the location, as the name is already in the header).
(In reply to Anne (:annevk) from comment #3) > (In reply to Brian Grinstead [:bgrins] from comment #1) > > To be clear, you want to get rid of the subview entirely unless if MCB is > > happening? > > Yes. > > Tanvi, if not already present, we could add it to "More Information". And if > it's really that vital, we should just include it in the main view (only the > location, as the name is already in the header). There's only so much info we can show in the main view of the control center. There are bugs on file to add other section(s) of the 'more information' popup directly into the control center (permissions, for instance). And as those get added we need to be careful to make sure that the CC doesn't end up becoming too big or cluttered. Anyway, forwarding this to Aislinn to get her opinion.
Flags: needinfo?(agrigas)
Thanks for your feedback Anne - we think this design provides the necessary detail without having to go into the 'More Info' modal and provides the right hierarchy for users that want to dig deeper and do more advanced actions like disabling mixed content blocking or learning more about why the page security state is not secure. This pattern of giving high level overview and more detail is one we carry throughout the control center (security block and permissions). We plan to track and test usage so we can see engagement on that sub-panel to further learn from our design.
Flags: needinfo?(agrigas)
By "we" you mean the UX team? What exactly is the value in "verified by" and "run by" then?
(In reply to Anne (:annevk) from comment #6) > By "we" you mean the UX team? What exactly is the value in "verified by" and > "run by" then? In a previous bug, we have changed having both verified by and run by in the top section. https://bugzilla.mozilla.org/show_bug.cgi?id=1191044 Having details for website owners/developers and advanced users to quickly see focused information on a site's connection status we feel is important. We're aiming to transition most content away from the model into a new more scannable design. And yes, the UX team.
Right, when I discussed that bug with with Daniel it was not clear to him either why we were showing this information over other information from the certificate, or the cipher used. Neither "run by" nor "verified by" are interesting enough even for advanced users. Access to the certificate and more detailed connection information as Chrome provides seems more appealing.
(In reply to Anne (:annevk) from comment #8) > Right, when I discussed that bug with with Daniel it was not clear to him > either why we were showing this information over other information from the > certificate, or the cipher used. Neither "run by" nor "verified by" are > interesting enough even for advanced users. Access to the certificate and > more detailed connection information as Chrome provides seems more appealing. We can always add more detailed information over time as we learn more from the current design. Google does include the verified info and its on the second tab so similarly hidden a layer down. We have talked about adding in more techinical details but it wasn't in scope for V1.
It's still not clear to me we have good rationale for including "run by" and "verified by" in the UI other than Google doing it.
(In reply to Anne (:annevk) from comment #10) > It's still not clear to me we have good rationale for including "run by" and > "verified by" in the UI other than Google doing it. Per commment #7 above - we are not. That recently changed and is not yet in Nightly.
Bug 1191044 only affected EV certificates. "Verified by" is included for other certificate types as well. What did I miss from comment 7?
(In reply to Anne (:annevk) from comment #12) > Bug 1191044 only affected EV certificates. "Verified by" is included for > other certificate types as well. What did I miss from comment 7? This bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1191044
As I said, that bug only affects EV certificates. Also, the patch attached in that bug seems to have made it into Nightly.
(In reply to Anne (:annevk) from comment #14) > As I said, that bug only affects EV certificates. Also, the patch attached > in that bug seems to have made it into Nightly. The verified and run by text only showed on EV certs. Its not shown otherwise...
See comment 12, "verified by" is used for all certificates. But again, what I contest is that either of these provides useful information to advanced users.
We're going to go forward with what we have and will re-address adding in additional security info down the road.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Blocks: 1216897
No longer blocks: 1188565
You need to log in before you can comment on or make changes to this bug.