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
In HTML, all form control input events are composed 12.
Presently, we are not instantiating input events with { composed: true }. See for example fillIn and select. I have not looked if there are other places. It probably makes sense to make this change in fireEvent itself similar to how bubbles is true by default.
The
composed
property determines whether an event that occurs in shadow DOM will bubble to the host element.Link to MDN docs.
In HTML, all form control input events are composed 1 2.
Presently, we are not instantiating input events with
{ composed: true }
. See for example fillIn and select. I have not looked if there are other places. It probably makes sense to make this change infireEvent
itself similar to how bubbles is true by default.Footnotes
Search for "Fire an event named input" on https://html.spec.whatwg.org/multipage/input.html and https://html.spec.whatwg.org/multipage/form-elements.html. ↩
Change events are not composed. ↩
The text was updated successfully, but these errors were encountered: