Proposed agenda for May 11 2016 call

Hi Patrick:

In tomorrow's meeting, we would like to focus mostly on "transition events
around capturing" because there are quite a few issues along this line:

1. Main Issue: Should a captured pointer send transition events by default?
https://github.com/w3c/pointerevents/issues/61

  Related issues:
  1a. While pointer is captured the boundary of the capturing element
should be itself and all its children
    https://github.com/w3c/pointerevents/issues/62
    Proposed fix: Clarified definition of capturing element borders
    https://github.com/w3c/pointerevents/pull/63

  1b. Incorrect order of the events in process pending pointer capture
section
    https://github.com/w3c/pointerevents/issues/39
    Proposed fix: Reorder the events in process pending pointer capture
    https://github.com/w3c/pointerevents/pull/40

  1c. Determine when boundary events are fired after capture is released
    https://github.com/w3c/pointerevents/issues/15


2. Issue: Spec implies lost/gotpointercapture is delayed until the next
pointer event but Edge does otherwise
  https://github.com/w3c/pointerevents/issues/32


Feel free to drop items from above to accommodate other topics.

Mustaq