Weekly github digest (Web Platform WG specs) from W3C Webmaster via GitHub API on 2017-11-07 (public-webapps-github-weekly@w3.org from November 2017)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 07 Nov 2017 17:00:29 +0000
To: public-webapps-github-weekly@w3.org
Message-Id: <E1eC7Ej-0001TT-8G@uranus.w3.org>
Issues
------
* w3c/webcomponents (+12/-2/💬102)
  12 issues created:
  - Do not specify template binding syntax in spec, make configurable  (by vidhill)
    https://github.com/w3c/webcomponents/issues/697
  - [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (by kethinov)
    https://github.com/w3c/webcomponents/issues/695
  - [templates] What is declareCallback? (by domenic)
    https://github.com/w3c/webcomponents/issues/693
  - [proposals]: Template Instantiation typo? (by danatcofo)
    https://github.com/w3c/webcomponents/issues/690
  - [templates] Unclear usage of markdown-like syntax in state object (by TimvdLippe)
    https://github.com/w3c/webcomponents/issues/689
  - Consider ${foo} instead of {{foo}} (by jdanyow)
    https://github.com/w3c/webcomponents/issues/688
  - [templates] API for updating (by domenic)
    https://github.com/w3c/webcomponents/issues/685
  - [templates] No need for -Callback suffix (by domenic)
    https://github.com/w3c/webcomponents/issues/684
  - [templates] Maybe each {{ ~ }} should be its own text node? (by domenic)
    https://github.com/w3c/webcomponents/issues/683
  - [templates] How featureful should the default processor be? (by domenic)
    https://github.com/w3c/webcomponents/issues/682
  - [templates] Is a global registry of template processors the right idea? (by domenic)
    https://github.com/w3c/webcomponents/issues/681
  - [templates] Parts APIs surface concerns (by domenic)
    https://github.com/w3c/webcomponents/issues/680

  18 issues received 102 new comments:
  - #682 [templates] How featureful should the default processor be? (17 by tclzcja, domenic, stramel, justinfagnani, rniwa, caridy)
    https://github.com/w3c/webcomponents/issues/682
  - #683 [templates] Maybe each {{ ~ }} should be its own text node? (16 by rniwa, annevk, justinfagnani)
    https://github.com/w3c/webcomponents/issues/683
  - #688 [templates] Consider ${foo} instead of {{foo}} (14 by domenic, MikeKovarik, tabatkins, stramel, kafein, annevk, rniwa, matthewp, caridy)
    https://github.com/w3c/webcomponents/issues/688
  - #488 [idea] Allow custom element naming on a per-shadow-root basis. (12 by WebReflection, trusktr, caridy, AlessandroEmm)
    https://github.com/w3c/webcomponents/issues/488
  - #695 [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (11 by vidhill, wiredearp, kethinov, justinfagnani, calebdwilliams, caridy)
    https://github.com/w3c/webcomponents/issues/695
  - #678 Disconnected Events (9 by rniwa, pemrouz)
    https://github.com/w3c/webcomponents/issues/678
  - #654 Custom attribute names conflicting with built-in attribute names (4 by rniwa, robdodson)
    https://github.com/w3c/webcomponents/issues/654
  - #658 Why do we really need hyphens? (4 by trusktr, Nektro, matthew-dean)
    https://github.com/w3c/webcomponents/issues/658
  - #641 Agenda for W3C TPAC 2017 (Web Components) (3 by rniwa, smaug----)
    https://github.com/w3c/webcomponents/issues/641
  - #681 [templates] Is a global registry of template processors the right idea? (3 by rniwa, Jamesernator)
    https://github.com/w3c/webcomponents/issues/681
  - #690 [proposals]: Template Instantiation typo? (2 by stramel, danatcofo)
    https://github.com/w3c/webcomponents/issues/690
  - #530 Should <link rel="stylesheet"> work inside shadow DOM? (1 by olanod)
    https://github.com/w3c/webcomponents/issues/530
  - #680 [templates] Parts APIs surface concerns (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/680
  - #684 [templates] No need for -Callback suffix (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/684
  - #685 [templates] API for updating (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/685
  - #689 [templates] Unclear usage of markdown-like syntax in state object (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/689
  - #693 [templates] What is declareCallback? (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/693
  - #697 [templates] Do not specify template binding syntax in spec, make configurable  (1 by rniwa)
    https://github.com/w3c/webcomponents/issues/697

  2 issues closed:
  - [templates] Unclear usage of markdown-like syntax in state object https://github.com/w3c/webcomponents/issues/689
  - [proposals]: Template Instantiation typo? https://github.com/w3c/webcomponents/issues/690

* w3c/screen-orientation (+0/-3/💬1)
  1 issues received 1 new comments:
  - #99 Orientation angle cannot be precisely mapped to orientation type for devices with 1:1 screen size ratio (1 by pozdnyakov)
    https://github.com/w3c/screen-orientation/issues/99

  3 issues closed:
  - Confusiong between "_pending-promise_" and "doc's pending promise" https://github.com/w3c/screen-orientation/issues/94
  - Event firing needs fixes https://github.com/w3c/screen-orientation/issues/93
  - Add [Exposed] to all interfaces https://github.com/w3c/screen-orientation/issues/106

* w3c/uievents (+1/-0/💬1)
  1 issues created:
  - Bug in spec? event.key and casing (by keithamus)
    https://github.com/w3c/uievents/issues/169

  1 issues received 1 new comments:
  - #147 Add specification for AltGraph key & modifier behaviour (1 by drwez)
    https://github.com/w3c/uievents/issues/147

* w3c/input-events (+0/-0/💬1)
  1 issues received 1 new comments:
  - #38 Replace StaticRange with a dictionary or figure out if normal Ranges could be used (1 by ojanvafai)
    https://github.com/w3c/input-events/issues/38

* w3c/dom (+1/-0/💬0)
  1 issues created:
  - legacyOutputDidListeners and dispatch event (by plehegar)
    https://github.com/w3c/dom/issues/165



Pull requests
-------------
* w3c/webcomponents (+9/-8/💬6)
  9 pull requests submitted:
  - Fix some typos, missing formating and erroneous Markdown in Template-Instantiation.md (by rkusa)
    https://github.com/w3c/webcomponents/pull/699
  - Add a missing parenthesis (by koba04)
    https://github.com/w3c/webcomponents/pull/698
  - Replace Em dash with hyphen minus (by koba04)
    https://github.com/w3c/webcomponents/pull/696
  - Fix template instantiation examples (by zcei)
    https://github.com/w3c/webcomponents/pull/694
  - Fix Handlebars typos (by padamczewski)
    https://github.com/w3c/webcomponents/pull/692
  - Fix Markdown styles of Template-Instantiation (by koba04)
    https://github.com/w3c/webcomponents/pull/691
  - Copy edits for all remaining parts (by sideshowbarker)
    https://github.com/w3c/webcomponents/pull/687
  - Copy edits to sections 3.1 and 3.2 (by sideshowbarker)
    https://github.com/w3c/webcomponents/pull/686
  - Copy-edits to Use Cases & Background sections (by sideshowbarker)
    https://github.com/w3c/webcomponents/pull/679

  5 pull requests received 6 new comments:
  - #696 Replace Em dash with hyphen minus (2 by koba04)
    https://github.com/w3c/webcomponents/pull/696
  - #691 Fix Markdown styles of Template-Instantiation (1 by koba04)
    https://github.com/w3c/webcomponents/pull/691
  - #694 Fix template instantiation examples (1 by zcei)
    https://github.com/w3c/webcomponents/pull/694
  - #698 Add a missing parenthesis (1 by koba04)
    https://github.com/w3c/webcomponents/pull/698
  - #699 Fix some typos, missing formating and erroneous Markdown in Template-Instantiation.md (1 by siusin)
    https://github.com/w3c/webcomponents/pull/699

  8 pull requests merged:
  - Add a missing parenthesis
    https://github.com/w3c/webcomponents/pull/698
  - Fix some typos, missing formating and erroneous Markdown in Template-Instantiation.md
    https://github.com/w3c/webcomponents/pull/699
  - Replace Em dash with hyphen minus
    https://github.com/w3c/webcomponents/pull/696
  - Fix template instantiation examples
    https://github.com/w3c/webcomponents/pull/694
  - Fix Markdown styles of Template-Instantiation
    https://github.com/w3c/webcomponents/pull/691
  - Fix Handlebars typos
    https://github.com/w3c/webcomponents/pull/692
  - Copy edits to sections 3.1 and 3.2
    https://github.com/w3c/webcomponents/pull/686
  - Copy-edits to Use Cases & Background sections
    https://github.com/w3c/webcomponents/pull/679

* w3c/screen-orientation (+6/-5/💬9)
  6 pull requests submitted:
  - Fix event firing (by pozdnyakov)
    https://github.com/w3c/screen-orientation/pull/112
  - Add [SameObject] to the `Screen.orientation` attribute (by pozdnyakov)
    https://github.com/w3c/screen-orientation/pull/111
  - Reference correct promise at the "apply an orientation lock" operation (by pozdnyakov)
    https://github.com/w3c/screen-orientation/pull/110
  - Clean-up anchors and definitions (by alexshalamov)
    https://github.com/w3c/screen-orientation/pull/109
  - Fix all ReSpec warnings (by alexshalamov)
    https://github.com/w3c/screen-orientation/pull/108
  - Add [Exposed=Window] extended attribute to ScreenOrientation interface (by alexshalamov)
    https://github.com/w3c/screen-orientation/pull/107

  6 pull requests received 9 new comments:
  - #107 Add [Exposed=Window] extended attribute to ScreenOrientation interface (2 by marcoscaceres, alexshalamov)
    https://github.com/w3c/screen-orientation/pull/107
  - #108 Fix all ReSpec warnings (2 by mounirlamouri, alexshalamov)
    https://github.com/w3c/screen-orientation/pull/108
  - #112 Fix event firing (2 by mounirlamouri, pozdnyakov)
    https://github.com/w3c/screen-orientation/pull/112
  - #109 Clean-up anchors and definitions (1 by alexshalamov)
    https://github.com/w3c/screen-orientation/pull/109
  - #110 Reference correct promise at the "apply an orientation lock" operation (1 by pozdnyakov)
    https://github.com/w3c/screen-orientation/pull/110
  - #111 Add [SameObject] to the `Screen.orientation` attribute (1 by mounirlamouri)
    https://github.com/w3c/screen-orientation/pull/111

  5 pull requests merged:
  - Reference correct promise at the "apply an orientation lock" operation
    https://github.com/w3c/screen-orientation/pull/110
  - Clean-up anchors and definitions
    https://github.com/w3c/screen-orientation/pull/109
  - Add [SameObject] to the `Screen.orientation` attribute
    https://github.com/w3c/screen-orientation/pull/111
  - Fix event firing
    https://github.com/w3c/screen-orientation/pull/112
  - Fix all ReSpec warnings
    https://github.com/w3c/screen-orientation/pull/108

* w3c/DOM-Parsing (+0/-1/💬2)
  1 pull requests received 2 new comments:
  - #32 Ask for tests for normative changes in CONTRIBUTING.md (2 by foolip, travisleithead)
    https://github.com/w3c/DOM-Parsing/pull/32

  1 pull requests merged:
  - Ask for tests for normative changes in CONTRIBUTING.md
    https://github.com/w3c/DOM-Parsing/pull/32


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, 7 November 2017 17:00:32 UTC