Closed
Bug 1236815
Opened 10 years ago
Closed 10 years ago
No offer to save password if submit button is not separated into div
Categories
(Toolkit :: Password Manager, defect)
Toolkit
Password Manager
Tracking
()
RESOLVED
INVALID
People
(Reporter: max, Unassigned)
Details
Attachments
(3 files)
ff43-screenshot.jpg
User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 Iceweasel/42.0
Build ID: 20151104073603
Steps to reproduce:
FF-43.0.3, linux, 32 bits (downloaded from mozilla.org)
I have the file (I open it through https, not locally)
------pwd.html------
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
</head>
<script>
function handleAuth() {
var username = document.getElementById("user").value;
var password = document.getElementById("password").value;
document.getElementById("info").textContent = "auth: " + username + ":" + password;
}
</script>
<body>
<form id="auth" action="javascript:handleAuth();">
<input id="user" type="text" name="user">
<input id="password" type="password" name="password">
<!-- <div><button value="Get">Get</button></div> -->
<button value="Get">Get</button>
</form>
<div id="info"></div>
</body>
</html>
----------------------
I enter some username and password and press "Get"
Actual results:
There is no offer to save the password
It works at other sites
***It works if I put the "Get" button into a div, like the commented line***
I've seen it worked in iceweasel-31.4.0, so could be a regression
Expected results:
FF should propose saving the password.
|
Reporter | |
Comment 3•10 years ago
|
||
Adding the Browser console output. There is one difference with success case (except the first line): at line 11 Username field value is empty, while in success case it is filled.
|
|
Reporter | |
Comment 4•10 years ago
|
||
This seems to be caused by my window manager. There was a hook on "leave window" which was setting some properties on the firefox window, which, as far as I understand, was causing immediate close of the offer popup. For some mysterious reason it depends on the document.
You can close this issue I think.
|
||
Comment 5•10 years ago
|
||
RESOLVED INVALID ("not a Mozilla bug") according to comment #4 by the reporter.
@Max: On bugs which _you_ reported, you may change most aspects of the bug (including the Status/Resolution), even if you lack "editbugs" permissions.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•