Weekly github digest (Web Platform WG specs)

Issues
------
* w3c/webcomponents (+0/-0/💬30)
  3 issues received 30 new comments:
  - #468 Provide a lightweight mechanism to add styles to a custom element (21 by domenic, annevk, ojanvafai, hayatoito, tomalec, rniwa)
    https://github.com/w3c/webcomponents/issues/468 [custom-elements] [needs concrete proposal] [shadow-dom] 
  - #587 Non-class based example of customElement.define() (5 by trusktr, justinfagnani)
    https://github.com/w3c/webcomponents/issues/587 
  - #187 Need callback for form submit data (4 by annevk, tkent-google)
    https://github.com/w3c/webcomponents/issues/187 [custom-elements] [needs concrete proposal] [needs consensus] 

* w3c/manifest (+0/-0/💬1)
  1 issues received 1 new comments:
  - #658 New Boolean members to control interaction with related applications (1 by mgiuca)
    https://github.com/w3c/manifest/issues/658 

* w3c/screen-orientation (+0/-0/💬1)
  1 issues received 1 new comments:
  - #113 Where are terms 'primary' and 'secondary' defined within spec? (1 by xfq)
    https://github.com/w3c/screen-orientation/issues/113 

* w3c/uievents (+9/-1/💬14)
  9 issues created:
  - [Question] select change + mousedown behavior (by nuragic)
    https://github.com/w3c/uievents/issues/201 
  - Need procedural algorithms for all events (by garykac)
    https://github.com/w3c/uievents/issues/200 
  - Need algorithm for how composition events are fired (by garykac)
    https://github.com/w3c/uievents/issues/199 
  - Need algorithm for how input events are fired (by garykac)
    https://github.com/w3c/uievents/issues/198 
  - Need algorithm for how mouse click events are fired (by garykac)
    https://github.com/w3c/uievents/issues/197 
  - Need algorithm for how mouse events are fired (by garykac)
    https://github.com/w3c/uievents/issues/196 
  - Need algorithm for how focus events are fired (by garykac)
    https://github.com/w3c/uievents/issues/195 
  - Define "event constructing steps" for complicated events (by annevk)
    https://github.com/w3c/uievents/issues/194 
  - Standardizing event.layerX and event.layerY (by WebReflection)
    https://github.com/w3c/uievents/issues/193 

  10 issues received 14 new comments:
  - #193 Standardizing event.layerX and event.layerY (2 by WebReflection, annevk)
    https://github.com/w3c/uievents/issues/193 
  - #195 Need algorithm for how focus events are fired (2 by garykac, domenic)
    https://github.com/w3c/uievents/issues/195 
  - #197 Need algorithm for how mouse click events are fired (2 by garykac, domenic)
    https://github.com/w3c/uievents/issues/197 
  - #142 Need algorithm for how events are fired for key presses (2 by domenic)
    https://github.com/w3c/uievents/issues/142 
  - #194 Define "event constructing steps" for complicated events (1 by annevk)
    https://github.com/w3c/uievents/issues/194 
  - #196 Need algorithm for how mouse events are fired (1 by domenic)
    https://github.com/w3c/uievents/issues/196 
  - #198 Need algorithm for how input events are fired (1 by garykac)
    https://github.com/w3c/uievents/issues/198 
  - #199 Need algorithm for how composition events are fired (1 by garykac)
    https://github.com/w3c/uievents/issues/199 
  - #135 Standardize layerX/layerY on MouseEvent (1 by WebReflection)
    https://github.com/w3c/uievents/issues/135 
  - #156 Support queryKeyCap (1 by garykac)
    https://github.com/w3c/uievents/issues/156 [Proposal] 

  1 issues closed:
  - Standardizing event.layerX and event.layerY https://github.com/w3c/uievents/issues/193 

* w3c/clipboard-apis (+0/-1/💬1)
  1 issues received 1 new comments:
  - #59 Request TAG review for initial (text only) API (1 by garykac)
    https://github.com/w3c/clipboard-apis/issues/59 

  1 issues closed:
  - Request TAG review for initial (text only) API https://github.com/w3c/clipboard-apis/issues/59 

* w3c/editing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #171 make need of execCommand to hide table controls go away on FF (1 by masayuki-nakano)
    https://github.com/w3c/editing/issues/171 [awaits feedback from Firefox] 

* w3c/input-events (+0/-0/💬1)
  1 issues received 1 new comments:
  - #78 Further developer guidance regarding political status of Level 1 (for Mozilla, Microsoft) and Level 2 (Google) (1 by js-choi)
    https://github.com/w3c/input-events/issues/78 

* w3c/dom (+0/-1/💬2)
  1 issues received 2 new comments:
  - #175 CfC: Move DOM 4.1 to Candidate Recommendation (2 by therealglazou, chaals)
    https://github.com/w3c/dom/issues/175 [question] 

  1 issues closed:
  - CfC: Move DOM 4.1 to Candidate Recommendation https://github.com/w3c/dom/issues/175 [question] 




Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/webcomponents
* https://github.com/w3c/FileAPI
* https://github.com/w3c/filesystem-api
* https://github.com/w3c/gamepad
* https://github.com/w3c/manifest
* https://github.com/w3c/manifest-csp
* https://github.com/w3c/pointerlock
* https://github.com/w3c/push-api
* https://github.com/w3c/screen-orientation
* https://github.com/w3c/workers
* https://github.com/w3c/websockets
* https://github.com/w3c/webmessaging
* https://github.com/w3c/webstorage
* https://github.com/w3c/eventsource
* https://github.com/w3c/ime-api
* https://github.com/w3c/uievents
* https://github.com/w3c/uievents-code
* https://github.com/w3c/uievents-key
* https://github.com/w3c/clipboard-apis
* https://github.com/w3c/editing
* https://github.com/w3c/selection-api
* https://github.com/w3c/input-events
* https://github.com/w3c/microdata
* https://github.com/w3c/2dcontext
* https://github.com/w3c/DOM-Parsing
* https://github.com/w3c/dom