ubuntu-webapps-bugs team mailing list archive
-
ubuntu-webapps-bugs team
-
Mailing list archive
-
Message #02030
[Bug 1402723] [NEW] No visual cue in the chrome after accepting a certificate error
Public bug reported:
(initially reported as part of bug #1377194)
Steps to reproduce:
1) Browse to e.g. https://testssl-expire.disig.sk/
2) Accept the certificate error (by clicking on the "Proceed anyway" button)
3) The page with an invalid certificate loads
Expected result: there is some sort of visual cue in the chrome to signify that the connection is potentially insecure.
Current result: there is no visual cue in the chrome.
For reference, I tested firefox and chromium on desktop: firefox just
pretends nothing happened if an exception was added (i.e. it says the
connection is secure and displays a padlock icon), whereas chromium
displays a padlock with a cross over it, and the "https" part of the
address is striked through. Two rather different approaches.
** Affects: ubuntu-ux
Importance: Undecided
Status: New
** Affects: webbrowser-app
Importance: Medium
Status: Triaged
** Also affects: ubuntu-ux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to webbrowser-app.
https://bugs.launchpad.net/bugs/1402723
Title:
No visual cue in the chrome after accepting a certificate error
Status in Ubuntu UX bugs:
New
Status in Web Browser App:
Triaged
Bug description:
(initially reported as part of bug #1377194)
Steps to reproduce:
1) Browse to e.g. https://testssl-expire.disig.sk/
2) Accept the certificate error (by clicking on the "Proceed anyway" button)
3) The page with an invalid certificate loads
Expected result: there is some sort of visual cue in the chrome to signify that the connection is potentially insecure.
Current result: there is no visual cue in the chrome.
For reference, I tested firefox and chromium on desktop: firefox just
pretends nothing happened if an exception was added (i.e. it says the
connection is secure and displays a padlock icon), whereas chromium
displays a padlock with a cross over it, and the "https" part of the
address is striked through. Two rather different approaches.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1402723/+subscriptions
Follow ups
References