Navid Zolghadr

Again we come back to my original question that I'm not sure what the code does in this library. How do we get there in that code? Is that a...

@smaug---- you are right. I was playing with the code and found the same problem. Here is a small code that reproduces the problem without this library: https://output.jsbin.com/geliweq I agree...

I see. I remember reading the first common parent of mousedown/up targets for click. I don't seem to find it anywhere in uievents spec though. That's what Chrome does. Edge...

@colinhowe FYI as he was the author of the original CL. This CL addresses #1165 in a more spec compliant way. @DanielRuf I fixed the test here. The slow test...

@mustaqahmed might know better of the status. To the best of my knowledge, it was already implemented at least in Chromium.

I have a confusion about considering a "storage" to be just _cold_ or _hot_. For example in today's GCP offerings there are multiple storage classes all of which are accessible...

cc @majido @mustaq Can you clarify a little more about what the EventPort would look like? So is it like the main thread will create an EventPort object (which is...

I like a few properties of this proposal you are suggesting: 1. We are sending the "event carrier object" (regardless of what we call it) through existing mechanisms (i.e. postMessage)....

> Not sure I understand this question. One can always create a new EventPort. My understanding is that when we pass an object (such as EventPort) as [per spec](https://html.spec.whatwg.org/multipage/web-messaging.html#message-ports) the...

> Ownership of EventPort is moved, but not ownership of the original EventTarget. That's my point. So the creator of the EventPort (say main thread) cannot stop the events anymore...