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
{{ message }}
This repository has been archived by the owner on Feb 4, 2018. It is now read-only.
This should trigger an event in the same manner skate does. This should probably be called something like emit(), trigger() or dispatch() instead of simulate(), because it's not really "simulating" an event.
// Should be able to pass a string and it will emit an Event or fallback go CustomEventmount(<something/>).emit('my-event',options);// Should be able to emit a user-provided event instance, too.mount(<something/>).emit(newMouseEvent());
The text was updated successfully, but these errors were encountered:
Well it depends on how it will work, if there will be more logic than current skatejs/emit it's more like simulation than raw emit/dispatch
For instance according to my findings input event has composed flag set to true but change event has it set to false. So if we want to remove confusion and simply allow developer to call emit('input') and set proper composed flag it would be more of simulation than pure emit. Maybe this is rare case and rest of the events will be straightforward, so then it might be good idea to keep with simple emit and leave it up to documentation.
Quite frankly I couldn't even find where composed flag is in spec for input event ¯_(ツ)_/¯
all Events which extend from base Event have composed:falsehttps://dom.spec.whatwg.org/#interface-event only if they are overridden (all events which inherit from UIEvent), like in input case, the composed is changed.
Also here is very nice summary(although old v0 spec) which events are not propagated ( composed ):
This should trigger an event in the same manner skate does. This should probably be called something like
emit()
,trigger()
ordispatch()
instead ofsimulate()
, because it's not really "simulating" an event.The text was updated successfully, but these errors were encountered: