Closed
Bug 1419230
Opened 7 years ago
Closed 7 years ago
Username and password not auto-fill on bualuang.co.th
Categories
(Toolkit :: Password Manager: Site Compatibility, defect, P3)
Toolkit
Password Manager: Site Compatibility
Tracking
()
RESOLVED
DUPLICATE
of bug 1147563
People
(Reporter: ananuti, Unassigned)
References
()
Details
I have saved username and password for https://www.bualuang.co.th/. Signon debug: 07:27:12.216 adding <unavailable> to loginFormRootElements for <unavailable> LoginManagerContent.jsm:1592 07:27:12.222 onDOMFormHasPassword: <unavailable> <unavailable> LoginManagerContent.jsm:379 07:27:12.225 _detectInsecureFormLikes "https://www.bualuang.co.th/" LoginManagerContent.jsm:489 07:27:12.482 nsLoginManager:Searching for logins nsLoginManager.js:396 07:27:12.504 Login storage:_searchLogins: returning 0 logins for Object { hostname: "https://www.bualuang.co.th", formSubmitURL: "https://www.bualuang.co.th" } with options Object { schemeUpgrades: true } storage-json.js:359 07:27:12.508 LoginManagerParent:sendLoginDataToChild: 0 deduped logins LoginManagerParent.jsm:220 07:27:12.232 adding <unavailable> to loginFormRootElements for <unavailable> LoginManagerContent.jsm:1592 07:27:12.257 _detectInsecureFormLikes "https://www.bualuang.co.th/" LoginManagerContent.jsm:489 07:27:12.484 Invalid chrome URI: / 07:27:12.510 cacheRecipes: for: "https://www.bualuang.co.th" LoginRecipes.jsm:207 07:27:12.511 _fillForm <unavailable> LoginManagerContent.jsm:1019
Comment 1•7 years ago
|
||
Maybe the form action changed? Or the subdomain?
Component: Password Manager → Password Manager: Site Compatibility
Priority: -- → P3
Reporter | ||
Comment 2•7 years ago
|
||
Looks like the latter, subdomain.
This site has:
> document.getElementById("form_login").action ="https://ent.bualuang.co.th/am/nigol_sw.php";
Comment 3•7 years ago
|
||
ok, then you're looking for bug 1147563 and bug 1200472
Comment 4•5 years ago
|
||
The website is insecure. This should be the reason why the credentials aren't auto-filled. I am looking for confirmation, if possible. If it should auto-fill, then it should be fixed by the change done for its duplicate.
Flags: needinfo?(MattN+bmo)
Comment 5•5 years ago
|
||
Where do you see that it's insecure? When I visit the site over https: I don't see errors.
The fix for bug 1147563 doesn't affect autofill, it only affects autocomplete.
Flags: needinfo?(MattN+bmo)
You need to log in
before you can comment on or make changes to this bug.
Description
•