Bug 164219 – Autofill doesn't fire change event

• Status: NEW
• Component: Forms

[David Gasperoni]

Created attachment 293412 [details]
Screencast illustrating the problem

When a form was filled before, some suggestions will appear in a dropdown under the specific input field. I suppose these are the ones that one can purge from Preferences, Autofill, Other forms.

If one selects one of the options, the `change` event for that input field. This means callbacks tied to those fields are not triggered.

[David Gasperoni]

Created attachment 293413 [details]
Screencast illustrating the problem

[David Gasperoni]

Still an issue in Safari Technology Preview release 26.

[Karel Bilek]

This is still an issue in 2024, for number inputs.

Text field seems to correctly trigger change event. However, number field seems to not trigger any change event.

Should I record another recording? It's a very straightforward issue with straigtforward repro.

[Ahmad Saleem]

(In reply to Karel Bilek from comment #3)
> This is still an issue in 2024, for number inputs.
> 
> Text field seems to correctly trigger change event. However, number field
> seems to not trigger any change event.
> 
> Should I record another recording? It's a very straightforward issue with
> straigtforward repro.

Yes please. Straightforward repo would be helpful.

[Karel Bilek]

Created attachment 470443 [details]
Simple HTML illustrating the bug

/echo-post is a simple script that replies to POST by echoing its input. It is not that important for this bug report, it just needs to be there.

[Karel Bilek]

Created attachment 470444 [details]
Screen recording with the problem

[Karel Bilek]

Okay. I made a small repro and I put it here

https://karelbilek.com/static/safari-repro/

The form and both its fields log all events to the textarea below.

There is a dumb POST echo at https://karelbilek.com/echo-post which replies to all POST requests with all form fields.

To reproduce:

1. first, you fill something in the form, put Submit. (This is to make Safari offer you the autofill.)
2. then, after the successful form submit, you click back.
3. you click on autofill on both the fields.

You can see that the text autofill correctly triggers change event. However, the number input autofill doesn't trigger anything. (The only thing that gets triggered are the mouse events from all the movements, but that is irrelevant here.)

Note that Chrome doesn't have this issue, because it doesn't offer autocomplete at all on number inputs. Safari does.

( This is a root cause for this svelte bug that I just reported to svelte - svelte doesn't correctly bind the number value, because it doesn't get any event triggered.

https://github.com/sveltejs/svelte/issues/10841 )

[Karel Bilek]

Note that this might be a different issue than the original bug from 2016, I can open as a new bug if needed.

[Karel Bilek]

When I run a debug build of Safari, I see

```
FormMetadata.js:3:86383: CONSOLE JS ERROR InvalidStateError: The input element's type ('number') does not support selection.
```

That seem to get close to the root of the problem?

[Karel Bilek]

FormMetadata.js seems to be from Safari/macOS itself, not from WebKit, as far as I can tell.

[Karel Bilek]

From all I can tell something like that is here, from Apple's Chrome extension

https://gist.github.com/AngeloD2022/fc105f77e999c024dff937f792875507

but I am really flying blind here

it seems to be Apple's proprietary js that has some bug and tries to do select JS event on number field which is impossible. (And so it might be Safari bug and not WebKit bug.)