Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 120 users
Status: Fixed
Closed: Oct 2016
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Legal: ----
Launch-M-Approved: 54-Beta
Launch-M-Target: 54-Stable-Exp, 55-Stable
Launch-Privacy: ----
Launch-Security: ----
Launch-Status: ----
Launch-Test: ----
Launch-UI: ----
Product-Review: ----

Sign in to add a comment
Ship Pointer Events API
Project Member Reported by, Mar 15 2013 Back to list

Change description:
Pointer Events unifies the web event model for touch, mouse, and pen input. It is designed to address concerns with the Touch Events spec.

Changes to API surface:
Adds the PointerEvent interface, as well as several new Pointer Event Types, and other changes. See spec for details.

WebKit bug:
Comment from W3C:
Apple's view:

Support in other browsers: current (expected)
Internet Explorer: IE10 
Firefox: Planned
Safari: Not planned

Do not confuse with the similarly named point-events CSS property:
Comment 1 by, Mar 16 2013
Blockedon: chromium:162757
Blockedon: chromium:258459
We will first ad support for touch-action in a way that benefits touch events while being compatible with pointer events ( issue 258459 ).
Labels: -M-X
Comment 4 by, Apr 30 2014
Blocking: chromium:246536
Labels: Hotlist-Input-Dev
Comment 7 by, Aug 15 2014
Blocking: -chromium:246536
Comment 8 Deleted
Comment 9 by, Feb 27 2015
You can continue the discussion at  issue 162757 .
Status: Assigned
Blockedon: chromium:471824
Blocking: chromium:246536
Blocking: chromium:392584
Blocking: chromium:454704
Blocking: chromium:269917
Blockedon: 606896
Blockedon: 608497
Blockedon: -608497
Labels: PointerEvent
Components: Blink>Input
Blockedon: 625678
Labels: Launch-M-Approved-54-Beta Launch-M-Target-54-Stable-Exp Launch-M-Target-55-Stable
Status: Started
Summary: Ship Pointer Events API (was: Support for Pointer Events)
Launch bug: issue 625678.  Approved for M54 field trial: 50% beta, 1% stable.

Approved intent to ship:!topic/blink-dev/UY1EfjaGF_E

Barring any surprises, Pointer Events should be enabled in Chrome 55 by default (reaching stable early December).
Description: Show this description
Blockedon: 631897
Blockedon: -606896
Status: Fixed
on android chrome 57, i find that pointevent will occur pointerdown,pointermove,pointercancel when touchmove on a  div  htmlelement, it only occurs one pointermove event.
in w3 spec, i find "After having fired the pointerdown event, if the pointer is subsequently used to manipulate the page viewport (e.g. panning or zooming)." 
why use pointerevent or not touchevent?
touchevent will occur many touchmove events but pointer event only occur only one pointermove when touch move on pages.
i find that many pages use pointers occurs some js errors,because occure only one pointermove and pointercancel,such as on android chrome 57
#27 - please, file a new issue for this. You can comment here with the issue number.
Re #27 I'd suggest filing an issue with the actual spec as Chrome's behavior is correct (but I'll pre-empt it by saying that if you intend to catch pointer moves instead of regular panning/zooming/scrolling then you need to set an appropriate touch-action on the div
Re #29 thank you ,i add css touch-action none ,both event occurs 
Sign in to add a comment