PEP Team Meeting – Jun 11 2015

Logo
- https://github.com/jquery/PEP/issues/161
- Agreed on https://github.com/jquery/PEP/issues/161#issuecomment-109401366
Marius sent a PR to fix the firing of boundary events during capture
- https://github.com/jquery/PEP/pull/195
- Need to check if this is covered by an existing W3C test
- If not, write a new one and submit to W3C
John-David Dalton and Alex Lu will work on W3C test automation
Hammer.js team to help with support for CSS touch-action
- https://github.com/jquery/PEP/issues/151

PEP Team Meeting – Jun 04 2015

Landed the sparse array implementation for PointerMap
Jacob to see if we can get a Microsoft intern to automate the W3C tests
Jacob to review https://github.com/jquery/PEP/pull/168
- Improve pointerdown/up events and buttons property in combination with mouse events

Stuart proposed a PointerMap update
- Two approaches to choose from:
  - Map: https://github.com/jquery/PEP/pull/189
  - SparseArrayMap: https://github.com/jquery/PEP/pull/190
- Use sparse array implementation
- Using an object, while more straight-forward, is actually slower: https://jsperf.com/performance-of-array-vs-object/17
Stuart working on dispatcher improvements
- https://github.com/jquery/PEP/issues/188
No PEWG call this week
- Still waiting to discuss Web Driver tests and events after pointer capture is released

Style guide landed
- Alex updating quotes to use double quotes
Functional tests landed
Scott looking into failing unit tests
No PEWG call this week
- Still waiting to discuss Web Driver tests and events after pointer capture is released

Style guide
- https://github.com/jquery/PEP/pull/185
- Ready to land?
  - Yes
Functional tests
- https://github.com/jquery/PEP/pull/184
- Ready to land?
  - Yes
Scott started looking into failing unit tests
- Bad detection of MSPointerEvent in test setup
- Need to determine what is and isn’t tested right now and if there are tests that don’t make sense to keep.

Marius replaced Esperanto with Rollup for builds
- https://github.com/jquery/PEP/pull/284
- Merged
Marius created a PR for ensuring mouse is always an active pointer
- https://github.com/jquery/PEP/pull/282
- Differentiates between active pointer and active buttons state
  - https://www.w3.org/TR/pointerevents/#h2_glossary
Ongoing discussion in W3C about whether pointer IDs should be consistent across frames and whether cross-frame capturing should be allowed
- https://github.com/w3c/pointerevents/issues/52
- https://github.com/w3c/pointerevents/issues/59
Marius created a PR which adds more tests
- https://github.com/jquery/PEP/pull/281
There’s a W3C discussion about whether over/out/enter/leave events should be fired during capture
- https://github.com/w3c/pointerevents/issues/61
Need to handle scenarios where browsers don’t trigger mouseup
- https://github.com/jquery/PEP/issues/279
- https://github.com/jquery/PEP/issues/286

Style guide implemented
- https://github.com/jquery/PEP/pull/185
- Using JSCS and JSHint for linting
- Using JSCS for automated whitespace fixes
- Need discussion on property access spacing: https://github.com/jquery/PEP/pull/185#discussion_r29373592
  - Settle on no spaces inside brackets
- Alex to update quotes after
Initial functional tests implemented
- https://github.com/jquery/PEP/pull/184
- Scott to implement some changes to reduce boilerplate
Random pointerId for mouse-initiated events
- https://github.com/jquery/PEP/issues/186
- Leave as-is

Released 0.3.0
M4rius is working on suppressing over/out/enter/leave events during pointer capture
- https://github.com/jquery/PEP/issues/177
Style guide
- Use jQuery style guide, but reduce the use of whitespace
- No spaces inside parenthesized bodies

Ready to release
- Scott and Alex did some manual testing in lots of browsers/devices
- Aim for release on Monday
- Scott and Jacob to work on blog post
Scott, Alex, and Jacob should have time next week to work on automating W3C tests

ES3 support
- https://github.com/jquery/PEP/issues/174
- For now continue to rely on ES5 features
- Look into a custom build that replaces the use of ES5 features that can’t be properly polyfilled (to avoid the use of es5-sham)
- Only a concern for less than a year, until Microsoft officially drops support for IE8
W3C tests
- Replace the test harness reporter with a custom reporter that accumulates the results and passes them to Intern
Ready to release?
- Do some manual testing first
jquery/PEP vs. jquery.pep.js
- https://github.com/jquery/PEP/issues/176
- Nothing for us to do