http authentication name is not displayed in dialog

Bug #191801 reported by Lee Maguire
6
Affects Status Importance Assigned to Milestone
epiphany-browser (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: epiphany-browser

When logging into a site that uses http authentication the dialog for username/password
no longer displays the name/identifier of the authentication.

(see screenshot attachment)

hardy
epiphany-browser 2.21.90-0ubuntu3
(after upgrading to xulrunner-1.9 1.9~b3+nobinonly-0ubuntu1)

Tags: usability
Revision history for this message
Lee Maguire (leemaguire) wrote :
Revision history for this message
Lee Maguire (leemaguire) wrote :

Actually, the dialog issue just seems to be the tip of the iceberg. epiphany seems completely unstable after running the hardy updates.
I've reverted xulrunner.

Revision history for this message
Alexander Jones (alex-weej) wrote :

This is pretty bad for usability. :(

Revision history for this message
Pedro Villavicencio (pedro) wrote :

confirming, thanks for the report.

Changed in epiphany-browser:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Paul Bryan (pbryan) wrote :

I'm writing to make a case for increasing the importance of this bug. A number of web sites provide pertinent information in the realm; having this suppressed in the authentication dialog makes it impossible to satisfy the login requirements for such sites.

Revision history for this message
Alexander Jones (alex-weej) wrote : Re: [Bug 191801] Re: http authentication name is not displayed in dialog

All the upstream focus seems to be around the Webkit move in 2.24. It's
probably only a very minor bug though.

Additionally, the Page Info function is completely wrecked, trying to open
an itms://link will give you a very broken dialogue, about:config bugs out
big style on setting integer values, the invalid TLS certificate page "Add
Exception" button doesn't work... the list goes on.

GtkMozEmbed is basically just crap Mozilla discharge, and we should probably
just cut our losses now. Bugs like this need to be fixed indeed, but given
that the Webkit port will be usable soon, I can't see anyone being motivated
enough to hack on this code anymore. If you're keen, though, give it a go!

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is an upstream one, could you open it on bugzilla.gnome.org too?

Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in epiphany-browser (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in epiphany-browser (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.