Weekly github digest (Web Platform WG specs) from W3C Webmaster via GitHub API on 2018-02-20 (public-webapps-github-weekly@w3.org from February 2018)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 20 Feb 2018 17:00:53 +0000
To: public-webapps-github-weekly@w3.org
Message-Id: <E1eoBHh-0004OT-PF@uranus.w3.org>
Issues
------
* w3c/webcomponents (+5/-14/💬105)
  5 issues created:
  - A way to implement :hover, :active, etc, for custom elements. (by trusktr)
    https://github.com/w3c/webcomponents/issues/738 
  - Some sort of guarantee on upgrade order? (by trusktr)
    https://github.com/w3c/webcomponents/issues/737 
  - It is unclear how elementFromPoint and elementsFromPoint should work (by smaug----)
    https://github.com/w3c/webcomponents/issues/736 
  - elementsFromPoint behavior is unclear (by smaug----)
    https://github.com/w3c/webcomponents/issues/735 
  - Please add &lt;map&gt; to the list of elements that support attachShadow(init) (by prushforth)
    https://github.com/w3c/webcomponents/issues/734 

  40 issues received 105 new comments:
  - #734 Please add <map> to the list of elements that support attachShadow(init) (18 by js-choi, annevk, prushforth, domenic, bkardell)
    https://github.com/w3c/webcomponents/issues/734 [needs implementer interest] [shadow-dom] 
  - #736 It is unclear how elementFromPoint and elementsFromPoint should work (6 by rniwa, annevk, matthewp, hayatoito)
    https://github.com/w3c/webcomponents/issues/736 [shadow-dom] [v1] 
  - #717 The way to access current script or current root, from Shadow DOM (5 by rniwa, annevk, TakayoshiKochi)
    https://github.com/w3c/webcomponents/issues/717 [needs implementer interest] [shadow-dom] 
  - #544 Polymer encouraged incorrect document.createElement() usage (4 by rniwa, annevk, emilio)
    https://github.com/w3c/webcomponents/issues/544 [custom-elements] [v1] 
  - #713 WebPlatform Web Components F2F 2018 (4 by rniwa, annevk, treshugart, travisleithead)
    https://github.com/w3c/webcomponents/issues/713 
  - #723 Make custom elements w/ shadowRoot { display: contents } by default (4 by rniwa, annevk, TakayoshiKochi)
    https://github.com/w3c/webcomponents/issues/723 [custom-elements] [needs implementer interest] 
  - #468 Provide a lightweight mechanism to add styles to a custom element (4 by rniwa, calebdwilliams, tomayac)
    https://github.com/w3c/webcomponents/issues/468 [custom-elements] [needs consensus] [shadow-dom] 
  - #640 Generic programs can't reliably use/manipulate documents via the DOM (3 by annevk, mrmr1993, isiahmeadows)
    https://github.com/w3c/webcomponents/issues/640 [shadow-dom] 
  - #652 Close this repository in the future (3 by rniwa, annevk, TakayoshiKochi)
    https://github.com/w3c/webcomponents/issues/652 
  - #300 Support Custom Pseudo-elements (3 by trusktr, rniwa, annevk)
    https://github.com/w3c/webcomponents/issues/300 [shadow-dom] [v2] 
  - #567 accessibility considerations: states and behaviors (3 by rniwa, annevk, Zambonifofex)
    https://github.com/w3c/webcomponents/issues/567 [custom-elements] 
  - #735 elementsFromPoint behavior is unclear (3 by rakina, smaug----, hayatoito)
    https://github.com/w3c/webcomponents/issues/735 
  - #719 Interface/class-based selector (3 by rniwa, annevk)
    https://github.com/w3c/webcomponents/issues/719 [custom-elements] [needs implementer interest] 
  - #726 Named slots and the slot attribute requirement (3 by rniwa, cary-smith)
    https://github.com/w3c/webcomponents/issues/726 [needs implementer interest] [shadow-dom] 
  - #511 Add <a> to safelist of elements that can call attachShadowRoot (3 by annevk, TakayoshiKochi)
    https://github.com/w3c/webcomponents/issues/511 [needs implementer interest] [shadow-dom] 
  - #658 Why do we really need hyphens? (2 by trusktr, annevk)
    https://github.com/w3c/webcomponents/issues/658 [custom-elements] 
  - #159 ARIA custom element API (2 by rniwa, annevk)
    https://github.com/w3c/webcomponents/issues/159 [custom-elements] [needs concrete proposal] [needs implementer interest] 
  - #552 Should ARIA 2.0 have a role corresponding to every HTML element? (2 by annevk)
    https://github.com/w3c/webcomponents/issues/552 [custom-elements] [v2] 
  - #559 [IDEA] deferred upgrade for Custom Elements. (2 by trusktr, annevk)
    https://github.com/w3c/webcomponents/issues/559 [custom-elements] [question] 
  - #566 Is there a way to retrieve the localName from a custom element constructor? (2 by annevk)
    https://github.com/w3c/webcomponents/issues/566 [custom-elements] [v2] 
  - #715 Undefined specification for @keyframe scope on slotted content (2 by annevk, TakayoshiKochi)
    https://github.com/w3c/webcomponents/issues/715 [shadow-dom] [v1] 
  - #730 If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (2 by annevk, OvermindDL1)
    https://github.com/w3c/webcomponents/issues/730 
  - #606 Unexpected upgrade timing when appending an element and script together (2 by rniwa, annevk)
    https://github.com/w3c/webcomponents/issues/606 [custom-elements] [needs consensus] [v1] 
  - #737 Some sort of guarantee on custom element lifecycle order of events (2 by Jamesernator, annevk)
    https://github.com/w3c/webcomponents/issues/737 
  - #738 A way to implement :hover, :active, etc, for custom elements. (2 by rniwa, emilio)
    https://github.com/w3c/webcomponents/issues/738 [custom-elements] [needs implementer interest] 
  - #619 Consider adding a childrenChangedCallback or something (2 by trusktr, annevk)
    https://github.com/w3c/webcomponents/issues/619 [custom-elements] [v2] 
  - #665 Which standard defines :defined (1 by TakayoshiKochi)
    https://github.com/w3c/webcomponents/issues/665 [custom-elements] [v1] 
  - #675 Detecting finally-distributed nodes. (1 by annevk)
    https://github.com/w3c/webcomponents/issues/675 
  - #678 Disconnected Events (1 by annevk)
    https://github.com/w3c/webcomponents/issues/678 
  - #553 Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (1 by annevk)
    https://github.com/w3c/webcomponents/issues/553 
  - #184 <iframe> and the History API (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/184 [needs consensus] [shadow-dom] [v1] 
  - #187 Need callback for form submit data (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/187 [custom-elements] [needs implementer interest] 
  - #671 Custom Element - untrackable upgrade (1 by annevk)
    https://github.com/w3c/webcomponents/issues/671 [custom-elements] [enhancement] 
  - #78 Support `>>>` combinator in static profile (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/78 [needs consensus] [needs implementer interest] [shadow-dom] 
  - #718 Bulk property updates (1 by annevk)
    https://github.com/w3c/webcomponents/issues/718 
  - #729 Input requested on ARIA/HTML role parity (1 by annevk)
    https://github.com/w3c/webcomponents/issues/729 
  - #725 Interfaces for web components (1 by annevk)
    https://github.com/w3c/webcomponents/issues/725 
  - #479  {DocumentOrShadowRoot or Slot}.activePath (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/479 [needs consensus] [needs implementer interest] [shadow-dom] 
  - #614 fullscreenchange should be dispatched on each ancestor shadow root (1 by annevk)
    https://github.com/w3c/webcomponents/issues/614 [shadow-dom] 
  - #615  components v1 native implementation - inner components problem (1 by annevk)
    https://github.com/w3c/webcomponents/issues/615 [custom-elements] [question] 

  14 issues closed:
  - Make custom elements w/ shadowRoot { display: contents } by default https://github.com/w3c/webcomponents/issues/723 [custom-elements] [needs implementer interest] 
  - Add <a> to safelist of elements that can call attachShadowRoot https://github.com/w3c/webcomponents/issues/511 [needs implementer interest] [shadow-dom] 
  - Consider adding a childrenChangedCallback or something https://github.com/w3c/webcomponents/issues/619 [custom-elements] [v2] 
  - Generic programs can't reliably use/manipulate documents via the DOM https://github.com/w3c/webcomponents/issues/640 [shadow-dom] 
  - Please add <map> to the list of elements that support attachShadow(init) https://github.com/w3c/webcomponents/issues/734 [needs implementer interest] [shadow-dom] 
  - Detecting finally-distributed nodes. https://github.com/w3c/webcomponents/issues/675 
  - Why do we really need hyphens? https://github.com/w3c/webcomponents/issues/658 [custom-elements] 
  - accessibility considerations: states and behaviors https://github.com/w3c/webcomponents/issues/567 [custom-elements] 
  - Should ARIA 2.0 have a role corresponding to every HTML element? https://github.com/w3c/webcomponents/issues/552 [custom-elements] [v2] 
  - Interfaces for web components https://github.com/w3c/webcomponents/issues/725 
  - Disconnected Events https://github.com/w3c/webcomponents/issues/678 
  - [IDEA] deferred upgrade for Custom Elements. https://github.com/w3c/webcomponents/issues/559 [custom-elements] [question] 
  - If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? https://github.com/w3c/webcomponents/issues/730 
  - Input requested on ARIA/HTML role parity https://github.com/w3c/webcomponents/issues/729 

* w3c/FileAPI (+0/-0/💬13)
  1 issues received 13 new comments:
  - #97 Support `Response` in `URL.createObjectURL` (13 by bmeck, guest271314)
    https://github.com/w3c/FileAPI/issues/97 

* w3c/gamepad (+0/-6/💬11)
  10 issues received 11 new comments:
  - #63 Add [Exposed] to all interfaces (2 by annevk, sgraham)
    https://github.com/w3c/gamepad/issues/63 
  - #65 About the id (1 by sgraham)
    https://github.com/w3c/gamepad/issues/65 
  - #5 It is not defined what the value of Gamepad.index should be after disconnecting the gamepad (1 by sgraham)
    https://github.com/w3c/gamepad/issues/5 
  - #7  Need to spec better support for control mapping (1 by sgraham)
    https://github.com/w3c/gamepad/issues/7 [v2] 
  - #10 Connected Attribute appears to serve no purpose if the Gamepad object is a snapshot (1 by sgraham)
    https://github.com/w3c/gamepad/issues/10 
  - #11  Order in which index entries should be reused is unspecified (1 by sgraham)
    https://github.com/w3c/gamepad/issues/11 
  - #13 Specify exact length of array returned by Navigator.getGamepads() (1 by sgraham)
    https://github.com/w3c/gamepad/issues/13 
  - #52 Only 4 Gamepads? (1 by sgraham)
    https://github.com/w3c/gamepad/issues/52 
  - #57 Standard mapping image should be described in text (1 by sgraham)
    https://github.com/w3c/gamepad/issues/57 
  - #61 Timeline to Recommendation? (1 by LJWatson)
    https://github.com/w3c/gamepad/issues/61 

  6 issues closed:
  - Timeline to Recommendation? https://github.com/w3c/gamepad/issues/61 
  - Connected Attribute appears to serve no purpose if the Gamepad object is a snapshot https://github.com/w3c/gamepad/issues/10 
  - Only 4 Gamepads? https://github.com/w3c/gamepad/issues/52 
  - It is not defined what the value of Gamepad.index should be after disconnecting the gamepad https://github.com/w3c/gamepad/issues/5 
  - Specify exact length of array returned by Navigator.getGamepads() https://github.com/w3c/gamepad/issues/13 
  -  Order in which index entries should be reused is unspecified https://github.com/w3c/gamepad/issues/11 

* w3c/manifest (+0/-1/💬1)
  1 issues received 1 new comments:
  - #589 Richer splash screen backgrounds (1 by tomayac)
    https://github.com/w3c/manifest/issues/589 

  1 issues closed:
  - Fix references to lower case in spec https://github.com/w3c/manifest/issues/602 

* w3c/push-api (+1/-0/💬1)
  1 issues created:
  - pushManager.subscribe should replace applicationServerKey if different (by collimarco)
    https://github.com/w3c/push-api/issues/291 

  1 issues received 1 new comments:
  - #291 pushManager.subscribe should replace applicationServerKey if different (1 by kitcambridge)
    https://github.com/w3c/push-api/issues/291 

* w3c/webstorage (+1/-0/💬2)
  1 issues created:
  - Make session/localstorage iteratable (by jimmywarting)
    https://github.com/w3c/webstorage/issues/8 

  1 issues received 2 new comments:
  - #8 Make session/localstorage iteratable (2 by jimmywarting, annevk)
    https://github.com/w3c/webstorage/issues/8 

* w3c/uievents (+2/-0/💬0)
  2 issues created:
  - May the state of modifier keys influence MouseEvent.button? (by jfirebaugh)
    https://github.com/w3c/uievents/issues/184 
  - Declare keypress event should be fired when pressing Enter, Shift + Enter and Ctrl + Enter (by masayuki-nakano)
    https://github.com/w3c/uievents/issues/183 

* w3c/clipboard-apis (+4/-3/💬6)
  4 issues created:
  - The "context is editable"-condition in the fire event-algorithm needs clarification (by hugoholgersson)
    https://github.com/w3c/clipboard-apis/issues/69 
  - Spec does not auto-deploy when changes are made (by garykac)
    https://github.com/w3c/clipboard-apis/issues/68 
  - Should we have an API to return the set of readable/writable data types? (by garykac)
    https://github.com/w3c/clipboard-apis/issues/67 
  - When called without gesture, return an error describing rejection (by owencm)
    https://github.com/w3c/clipboard-apis/issues/66 

  4 issues received 6 new comments:
  - #66 When called without gesture, return an error describing rejection (2 by owencm, garykac)
    https://github.com/w3c/clipboard-apis/issues/66 
  - #68 Spec does not auto-deploy when changes are made (2 by garykac, siusin)
    https://github.com/w3c/clipboard-apis/issues/68 
  - #67 Should we have an API to return the set of readable/writable data types? (1 by garykac)
    https://github.com/w3c/clipboard-apis/issues/67 
  - #57 Should clipboard actions consider whether selection has focus? (1 by hugoholgersson)
    https://github.com/w3c/clipboard-apis/issues/57 

  3 issues closed:
  - Spec does not auto-deploy when changes are made https://github.com/w3c/clipboard-apis/issues/68 
  - Should clipboard actions consider whether selection has focus? https://github.com/w3c/clipboard-apis/issues/57 
  - Define each event type is composed or not, update the spec https://github.com/w3c/clipboard-apis/issues/61 

* w3c/selection-api (+0/-0/💬2)
  2 issues received 2 new comments:
  - #84 Background section is a mess (1 by hugoholgersson)
    https://github.com/w3c/selection-api/issues/84 
  - #94 No definition of hidden selections (1 by hugoholgersson)
    https://github.com/w3c/selection-api/issues/94 



Pull requests
-------------
* w3c/webcomponents (+0/-1/💬0)
  1 pull requests merged:
  - aggravate => aggregate
    https://github.com/w3c/webcomponents/pull/724 

* w3c/FileAPI (+0/-0/💬4)
  1 pull requests received 4 new comments:
  - #68 Remove definition of Blob.close() and all related terms. (4 by annevk, guest271314)
    https://github.com/w3c/FileAPI/pull/68 

* w3c/manifest (+2/-2/💬2)
  2 pull requests submitted:
  - Use infra spec and data-cite (by kenchris)
    https://github.com/w3c/manifest/pull/655 
  - Update the Service Worker object to not conflict with SW WebIDL (by kenchris)
    https://github.com/w3c/manifest/pull/654 

  2 pull requests received 2 new comments:
  - #530 feat: Add splashscreens member + purpose (closes #510) (1 by tomayac)
    https://github.com/w3c/manifest/pull/530 
  - #654 Update the Service Worker object to not conflict with SW WebIDL (1 by kenchris)
    https://github.com/w3c/manifest/pull/654 

  2 pull requests merged:
  - Use infra spec and data-cite
    https://github.com/w3c/manifest/pull/655 
  - Update the Service Worker object to not conflict with SW WebIDL
    https://github.com/w3c/manifest/pull/654 

* w3c/uievents (+1/-1/💬0)
  1 pull requests submitted:
  - single character typo fix (by ahulab)
    https://github.com/w3c/uievents/pull/182 

  1 pull requests merged:
  - single character typo fix
    https://github.com/w3c/uievents/pull/182 

* w3c/clipboard-apis (+0/-2/💬5)
  2 pull requests received 5 new comments:
  - #58 Emphasize visability in the "pick target"-algorithm (3 by garykac, hugoholgersson)
    https://github.com/w3c/clipboard-apis/pull/58 
  - #62 Make all clipboard events composed by default. (2 by garykac, TakayoshiKochi)
    https://github.com/w3c/clipboard-apis/pull/62 

  2 pull requests merged:
  - Make all clipboard events composed by default.
    https://github.com/w3c/clipboard-apis/pull/62 
  - Emphasize visability in the "pick target"-algorithm
    https://github.com/w3c/clipboard-apis/pull/58 


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
Received on Tuesday, 20 February 2018 17:00:58 UTC