- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 3 Jun 2014 08:54:53 +0300
- To: Jacob Rossi <Jacob.Rossi@microsoft.com>
- Cc: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
small typo and tweak (to make it flow better): (meaning that a new *event* path ... the "at the time it left the tree" on first reading seems to imply timing of when the event(s) should be dispatched. maybe put that part in parentheses instead of the final bit? "(at the time it was removed from the tree), meaning that..." don't have easy access to the previous discussion, but what happens again if the parent node is also gone? does it try to find THAT node's parent? should the spec say something about this too? -- Patrick H. Lauke > On 3 Jun 2014, at 08:39, Jacob Rossi <Jacob.Rossi@microsoft.com> wrote: > > Hi folks, > > Based on Action-98, I've created a proposed change to resolve this issue. Please let me know if it is not satisfactory. We can discuss on tomorrow's call also. > > https://dvcs.w3.org/hg/pointerevents/rev/f07f819eaf5e > > -Jacob > > -----Original Message----- > From: bugzilla@jessica.w3.org [mailto:bugzilla@jessica.w3.org] > Sent: Tuesday, June 3, 2014 1:38 AM > To: public-pointer-events@w3.org > Subject: [Bug 24923] What should happen to the mouse events if pointer event listener removes the target from document or hides it? > > https://www.w3.org/Bugs/Public/show_bug.cgi?id=24923 > > Jacob Rossi [MSFT] <jrossi@microsoft.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |RESOLVED > Resolution|--- |FIXED > > --- Comment #21 from Jacob Rossi [MSFT] <jrossi@microsoft.com> --- As asked in Action-98, I think this is the simplest change to describe this > behavior: > > https://dvcs.w3.org/hg/pointerevents/rev/f07f819eaf5e > > Feedback welcomed. > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
Received on Tuesday, 3 June 2014 05:55:20 UTC