W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2014

RE: [Bug 21951] [CR] pointermove dispatching when button state changes

From: Jacob Rossi <Jacob.Rossi@microsoft.com>
Date: Fri, 28 Feb 2014 23:41:40 +0000
To: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
Message-ID: <8d5b064106974d8fba66dc7953fe129c@BY2PR03MB457.namprd03.prod.outlook.com>
FYI - See text below and let me know if you have any issues with this change. Thanks!

-Jacob

-----Original Message-----
From: bugzilla@jessica.w3.org [mailto:bugzilla@jessica.w3.org] 
Sent: Friday, February 28, 2014 3:41 PM
To: public-pointer-events-bugzilla@w3.org
Subject: [Bug 21951] [CR] pointermove dispatching when button state changes

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21951


Jacob Rossi [MSFT] <jrossi@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Jacob Rossi [MSFT] <jrossi@microsoft.com> --- Fixed text in the following change:
https://dvcs.w3.org/hg/pointerevents/rev/a9862eea23f5



"A user agent MUST fire a pointer event named pointermove when a pointer changes coordinates. Additionally, when a pointer changes button state, pressure, tilt, or contact geometry (e.g. width and height) and the circumstances produce no other pointer events defined in this specification then a user agent MUST fire a pointer event named pointermove."

--
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 28 February 2014 23:42:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:26 UTC