1517987 - Consider saving form history when a form is "submitted" without a `submit` event

Status: UNCONFIRMED

(Toolkit :: Form Manager, enhancement, P3)

Description

[Xidorn Quan [:xidorn] UTC+10]

The login page is: https://secure.backblaze.com/user_signin.htm

The email field tag is:
<input class="bz-input email-field" name="email-field" type="text" placeholder="Email" value="">

There is no autocomplete dropdown shows up even after I've logged in via that several times. If I change the name to "email" then it works, but if I keep the name as-is, neither changing `type` to `email` nor adding `autocomplete="email"` works.

I'm not sure what's the heuristic here... but I would expect this to work somehow.

Comment 1

[Matthew N. [:MattN]]

Are you expecting form history to fill an email you previously submitted or the username of a saved login?

Comment 2

[Xidorn Quan [:xidorn] UTC+10]

Either is better than nothing. Ideally username of login, but since it uses separate pages for email and password, I can see there may be difficulties...

Comment 3

[Matthew N. [:MattN]]

The two solutions belong in two different components so that's why I was asking… We already have a bug for using a saved username but as you said that's hard and won't be fixed anytime soon (bug 348941).

The reason it's not saved in form history is probably because there is no <form> submission. We could use the same heuristics we use for password manager to handle this but that may cause us to save a lot more form history and my actually be a net negative if it clutters up the form history.

Comment 4

[Xidorn Quan [:xidorn] UTC+10]

There might be other heuristics we can use, for example in this case, the text field has placeholder "Email", and its name "email-field" also contains "email" so that might be usable as well...

Alternatively, for bug 348941, maybe we can track this kind of page sequence that a page followed by another page with just a password input, in which case we can backtrack the previous page to assume it may have a username field.

Comment 5

[Xidorn Quan [:xidorn] UTC+10]

Note that, Chrome can correctly save the email address somehow, probably via form autofill (rather than login, as their password saving dialog doesn't contain the email address). Maybe we should just improve our heuristic for detecting email field.

Comment 6

[Matthew N. [:MattN]]

(In reply to Xidorn Quan [:xidorn] UTC+11 from comment #5)

Note that, Chrome can correctly save the email address somehow, probably via form autofill (rather than login, as their password saving dialog doesn't contain the email address). Maybe we should just improve our heuristic for detecting email field.

yeah, we started on that in bug 1364602 but it stalled.