You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a page that loads form elements dynamically after load. In order to catch events fired by these elements I have attached to the event further up the DOM like this:
However after the first text box I interact with none of the ones I interact with after that fire the event correctly.
I'm using the latest Chrome on OSX.
Tracing through it quickly the problem seems to be with how the event is bound if isSupported(elem) is false using the dlgtTo events. Anyways I'd try for a fix, but give that this library is attempting to be 100% cross-browser compatible I think it might be a bit hard.
Anyways an alternative fallback I've taken the approach of just polling any focused textboxes every 500ms or so. This approach could simply be "skipped" for browser that properly support the new "input" events. It isn't perfect, but it works for most scenarios.
The text was updated successfully, but these errors were encountered:
I have a page that loads form elements dynamically after load. In order to catch events fired by these elements I have attached to the event further up the DOM like this:
However after the first text box I interact with none of the ones I interact with after that fire the event correctly.
I'm using the latest Chrome on OSX.
Tracing through it quickly the problem seems to be with how the event is bound if
isSupported(elem)
is false using thedlgtTo
events. Anyways I'd try for a fix, but give that this library is attempting to be 100% cross-browser compatible I think it might be a bit hard.Anyways an alternative fallback I've taken the approach of just polling any focused textboxes every 500ms or so. This approach could simply be "skipped" for browser that properly support the new "input" events. It isn't perfect, but it works for most scenarios.
The text was updated successfully, but these errors were encountered: