{"action":"opened","issue":{"url":"https://api.github.com/repos/w3c/pointerevents/issues/33","labels_url":"https://api.github.com/repos/w3c/pointerevents/issues/33/labels{/name}","comments_url":"https://api.github.com/repos/w3c/pointerevents/issues/33/comments","events_url":"https://api.github.com/repos/w3c/pointerevents/issues/33/events","html_url":"https://github.com/w3c/pointerevents/issues/33","id":130201932,"number":33,"title":"Value of button attribute for pointermove event","user":{"login":"bethge","id":522575,"avatar_url":"https://avatars.githubusercontent.com/u/522575?v=3","gravatar_id":"","url":"https://api.github.com/users/bethge","html_url":"https://github.com/bethge","followers_url":"https://api.github.com/users/bethge/followers","following_url":"https://api.github.com/users/bethge/following{/other_user}","gists_url":"https://api.github.com/users/bethge/gists{/gist_id}","starred_url":"https://api.github.com/users/bethge/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bethge/subscriptions","organizations_url":"https://api.github.com/users/bethge/orgs","repos_url":"https://api.github.com/users/bethge/repos","events_url":"https://api.github.com/users/bethge/events{/privacy}","received_events_url":"https://api.github.com/users/bethge/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-01-31T22:30:41Z","updated_at":"2016-01-31T22:30:41Z","closed_at":null,"body":"We have noticed an inconsistency when it comes to the `button` attribute of a `pointermove` event (https://github.com/jquery/PEP/pull/267).\r\n\r\nIn IE 11 and Edge, any `pointermove`, that does not express a button state transition, has `button: -1`.\r\n\r\nIn OSX and Win - FF 44 (with flag) a `pointermove`'s `button` attribute mirrors the `mousemove`'s `button` attribute, with the extension of `button: -1`, if no button is pressed.\r\n\r\nAccording to the specification: https://www.w3.org/TR/pointerevents/#chorded-button-interactions `button` and `buttons` are inherited from: https://www.w3.org/TR/DOM-Level-3-Events/#attributes-2, which states:\r\n> The value of button is not updated for events not caused by the depression/release of a mouse button. In these scenarios, take care not to interpret the value 0 as the left button, but rather as the un-initialized value.\r\n\r\nIs there an expected value of `button` for a `pointermove` with a button pressed and no button state transition? Is `button: -1` the new _un-initialized value_?\r\n\r\nThe current situation for `mousemove` is quite diverse and varies across OS and browsers, with `button: 0` for Win IE and Win FF and `button: 0/1/2` (matching the currently pressed button) for OSX Safari, OSX FF, OSX CH and Win CH. Might PE be an opportunity to form a consistent behaviour?\r\n\r\nP.S.: The same holds for `pointerenter`, `pointerover`, `pointerleave` and `pointerout`."}}