PEP Team Meeting – Oct 27 2016

Scott fixed the problem with updating W3C tests
- https://github.com/jquery/PEP/issues/314
- https://github.com/jquery/PEP/pull/317
- Still need to finish pulling in the updated tests, but that requires updating our existing automation
Marius updated ChromeDriver to work with latest Chrome
- https://github.com/jquery/PEP/pull/319
The next version of Chrome stable with ship with Pointer Events enabled, so we will need to change how we run local tests.
Marius has been working on parsing CSS rules from test files to generate the touch-action attributes.

PEP Team Meeting – Oct 20 2016

Everyone is very busy
- Let’s all commit to automating at least one test per week
Scott will look into the problem with updating to the latest W3C tests
- https://github.com/jquery/PEP/issues/314

PEP Team Meeting – Sep 29 2016

0.4.2 released
- Not yet announced
- Still need to update gh-pages
pressure should be 0 for pointerup events
- W3C discussion: https://github.com/w3c/pointerevents/issues/146
- PR: https://github.com/jquery/PEP/pull/313
- Merged

PEP Team Meeting – Sep 22 2016

pressure should be 0 for pointerup events
- W3C discussion: https://github.com/w3c/pointerevents/issues/146
- PR: https://github.com/jquery/PEP/pull/313
Can’t update tests
- https://github.com/jquery/PEP/issues/314
Need to document the testing process
- https://github.com/jquery/PEP/issues/315

PEP Team Meeting – Sep 08 2016

Need clarification on spec wording of "the element with the default touch behavior" for touch-action.
- For the common case of scrolling it's pretty simple - just walk up until you hit a scroller.
- If you add an overflow:scroll element as a descendant of a touch-action:none region, you should get scrolling back (consider component composition scenarios).
- As you walk up the ancestor chain, you're intersecting all the touch-actions.
- Chrome implementation for touch-action detection: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/input/TouchActionUtil.cpp?q=computeEffectiveTouchAction&sq=package:chromium&l=47&dr=CSs
It’s not worth adding the passive event listeners because Safari will end up being the only browser without native PointerEvents and it doesn’t have native support for all touch-action values.
There’s nothing holding up the 0.4.2 release at this point.

PEP Team Meeting – Sep 01 2016

Marius created a PR for passive event listeners and touch-action
- https://github.com/jquery/PEP/pull/309
- Need clarification on "nearest ancestor with default touch behavior" from https://www.w3.org/TR/pointerevents/#h3_the-touch-action-css-property
Release a new version as soon as passive event listeners land

PEP Team Meeting – Aug 18 2016

Marius is looking into passive event listeners

PEP Team Meeting – Aug 04 2016

Use InputDeviceCapabilities.firesTouchEvents to detect mouse events from touch events
- https://github.com/jquery/PEP/issues/307
- https://github.com/jquery/PEP/blob/35d17d8a391998c8c2128abff52d17bf7a5c452d/src/mouse.js#L33-L49
InputDeviceCapabilities.pointerMovementScrolls
- http://wicg.github.io/InputDeviceCapabilities/#dom-inputdevicecapabilities-pointermovementscrolls
- Let's say you have a carousel that you would swipe with a finger, but could select text with a mouse (and then use buttons to navigate). Instead of using pointerType to detect that and limiting it to touch and mouse, you could check if the pointer would normally cause scrolling.
Adding direction-specific touch-action values: up, down, left, right
- https://github.com/w3c/pointerevents/issues/6
- Edge has agreed to add them, but it will take them about a year.
Changing pointer capture from a modification of event targeting to a modification of hit testing
- Chrome team will create a branch of the spec that changes the behavior
Would like to see implicit capture for all pointer types, but there is concern from others that implicit capture for mouse will break the web
- https://github.com/w3c/pointerevents/issues/125
- Created a Chrome extension to mimic implicit capture
  - https://github.com/scottgonzalez/implicit-pointer-capture
Adding events around :active style
- https://github.com/w3c/pointerevents/issues/124
- So you can programmatically detect if a button would still be clicked if you released the pointer, based on how much movement has occurred since pressing down
gotpointercapture will now always be delayed until the next pointermove. gotpointercapture and lostpointercapture will always copy their properties from the event that caused them to be fired.
- https://github.com/w3c/pointerevents/issues/32
- https://github.com/w3c/pointerevents/issues/113
New method: hasPointerCapture()
- https://github.com/w3c/pointerevents/issues/121

PEP Team Meeting – Jul 21 2016

Pointer Events Hackathon
- Next week, so no PEP meeting
Update the README during releases
- https://github.com/jquery/PEP/issues/249
- Scott sent a pull request
  - https://github.com/jquery/PEP/pull/306
  - Merged
Support CSS touch-action instead of custom attribute
- https://github.com/jquery/PEP/issues/151
- Setting style.touchAction as a property is preserved in all browsers, only the style attribute is sanitized by the browsers.
  - Even changing styles via style.cssText and setAttribute(‘style’, …) doesn’t kill custom properties on the style property.

PEP Team Meeting – Jul 14 2016

Need to detect mouseup outside of window
- https://github.com/jquery/PEP/issues/279
- Marius has a pull request
  - https://github.com/jquery/PEP/pull/297
  - Merged
Pointer Events Hackathon
- July 26-27
- Browser vendors + jQuery
- Goals:
  - Identify implementation differences
  - Determine if the spec needs to change for any compat issues
  - Understand compat implications of removing hit testing while down
  - Improve test coverage as needed
Discussion about multi-pointer gestures and touch-action
- https://github.com/w3c/pointerevents/issues/29