input-for-workers
input-for-workers copied to clipboard
WICG
Specification for exposing input events to workers
I was really excited about this proposal, and repeatedly end up back at this repo, hoping some progress has been made with it. Even if it was only in Chrome...
Introduce a mirror event target to have an EventPort property.
Similar to MessagePort, if the API had an EventPort, it could be sent to subworkers and such. And EventPort could have a way filter out unnecessary events, or probably rather...
The expectation is that when on calls `worker.addEventTarget(target)` on main thread, the worker will receive the delegated target via the following handler. ```js // in worker addEventListener("eventtargetadded", ({delegated_target}) => {...
``` dictionary EventDelegationOptions { any context; }; ``` The proposed API proposed a `context` member that can be used when delegating an event target to a worker. It mentions that...
[Section 3](https://wicg.github.io/input-for-workers/#dispatching-a-pointerevent-to-the-eventdelegate) of the spec discusses the fork and dispatch semantic but it is very sparse. We should add the following: - Order of dispatch, is there any ordering gauranteed?...