Bugzilla – Bug 150372
epiphany fails to continue on password protected pages
Last modified: 2006-03-07 10:14:21 UTC
When filling a form previously used in 10.0, epiphany does not suggest to use old password, does not ask for remembering password, does not remember the password. How to reproduce: - Install 10.1 with default GNOME installation. - Mount your /home. - Visit web pages with saved passwords. Password is not suggested, even if password manager displays that it's saved. - Type password and login. You are not asked for remembering password. - Login again, password was not remembered. Additional info: Epiphany was started from session manager. In 10.0 this feature was working.
Additional info: Going to Edit -> Personal data -> Passwords, I see passwords for these web pages as remembered.
From: Christian Persch Subject: epiphany bug #150372 Date: Sat, 18 Feb 2006 23:16:53 +0100 ... I want to inform you that this bug: https://bugzilla.novell.com/show_bug.cgi?id=150372 is fixed in epiphany version 1.8.5 . ...
Mon Feb 20 13:40:29 CET 2006 - sbrabec@suse.cz - Enabled password manager (#150372).
Reopening. Epiphany is not able to continue into password protected pages, if the password is not already stored in password cache. It seems to wait for password manager dialog forever.
<jpr> chpe: https://bugzilla.novell.com/show_bug.cgi?id=150372 <jpr> chpe: is that solve by your sync with xulrunner in 1.8.4 or 1.8.5? --- You are now known as | <|> Merge the chrome stuff from HEAD; it's needed in order <|> to work with password manager on xulrunner. <|> Merge prompt service from HEAD to fix the button underline <|> bug and to fix the JS context stack problem. --- You are now known as jpr <jpr> chpe: that bug morphed a bit, but the final comment is the most relevant <chpe> jpr: yes. it looks like suse just took the pref changes, but the other changes in 1.8.5 are really needed too (data/chrome + EphyDirectoryProvider stuff)
Confirming that update to 1.8.5 fixes both original bug and the new problem. Update to CVS was not yet tested. Andreas, it looks we need this update.
Comment #5 is me confirming with the maintainer.
Stanislav, please test that this really solves the issue first - if it does, do the update.
Confirmed: - If password is not in database, it asks for remembering, then continues. - If password is already in database, it is used (tested with both old password and password remembered in step 1).
*** Bug 155563 has been marked as a duplicate of this bug. ***