desktop-packages team mailing list archive

[Rolf Leggewie <181893@xxxxxxxxxxxxxxxxxx>]

Andrea, thank you for your work.

** Changed in: epiphany-browser (Ubuntu)
       Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to epiphany-extensions in Ubuntu.
https://bugs.launchpad.net/bugs/181893

Title:
  Adding a certificate exception for non-trusted HTTPS sites is
  difficult

Status in Epiphany Browser:
  Expired
Status in “epiphany-browser” package in Ubuntu:
  Fix Released
Status in “epiphany-extensions” package in Ubuntu:
  Invalid
Status in “xulrunner-1.9” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: epiphany-browser

  SUMMARY
  Epiphany's handling of adding HTTPS certificates is not as streamlined as it could be. Presently users are presented with an error, and they then must click "Or you can add an exception…" then "Add exception..." then they must re-enter the URL with the problem, press "Get Certificate" and "Confirm Security Exception"

  Problems with the current solution:
  1. it requires a lengthy sequence of steps
  2. some of the steps look like doing the same thing twice "I want to add an exception"... "no, I really want to add an exception!"
  3. it requires re-entering the problematic URL. Not all users will really understand what this means. Some users will have clicked on a link to get to the page. They then have to copy the URL from the location bar, or realise that it can be selected for copy+paste, which is not entirely obvious.
  4. Once you press "Confirm Security Exception", you still are presented with the original error and need to reload the page

  Early comments on this bug describe earlier handling, which was far
  more obscure again.

  Please note, you do not need to report each non-working site
  individually in this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epiphany-browser/+bug/181893/+subscriptions