Side navigation
#12421 closed enhancement (patchwelcome)
Opened August 29, 2012 10:05AM UTC
Closed August 30, 2012 02:27PM UTC
Native autocomplete/autofill doesn't trigger change events in IE
Reported by: | maranomynet | Owned by: | |
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | git |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
This is a known "feature" in IE, but seems like just the kind of thing that jQuery should correct - like bubbling, etc.
Here's a reduced test: http://jsfiddle.net/xf9Dw/4/
Here's one possible fix: http://stackoverflow.com/a/8249622
Attachments (0)
Change History (3)
Changed August 29, 2012 12:28PM UTC by comment:1
Changed August 30, 2012 02:23PM UTC by comment:2
Actually, the "firing multiple times" bit only applied to the second, simpler/cruder solution. The first one fires only when an actual change has been made.
I thought this could be baked into an event-binding hook to apply it transparently to only inputs that need it.
Fixing this issue would make change
events far more reliable and useful.
Changed August 30, 2012 02:27PM UTC by comment:3
resolution: | → patchwelcome |
---|---|
status: | new → closed |
I've been through these several times myself, but if anyone else would like to revisit them and look for a solution I'd be glad to work with them.
There are many cases like this where you simply trade off one problem for another. Note that the SO thread says "If you don't care about onchange firing multiple times" but people DO care about those sort of things and by doing that you turn an autocomplete-only problem into a happens-every-time problem. Then we get even more bug reports about that.
An application-level workaround seems best here because only the app creator knows whether their code has been designed to deal with the workaround.