- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 30 Sep 2024 17:00:09 +0000
- To: public-webapps@w3.org
- Message-Id: <E1svJkn-0096aP-3B@janus.w3.internal>
Issues
------
* w3c/badging (+1/-1/💬1)
1 issues created:
- The badging API is not supported on Chromium-based browsers running on Android. (by 744111)
https://github.com/w3c/badging/issues/112
1 issues received 1 new comments:
- #112 The badging API is not supported on Chromium-based browsers running on Android. (1 by reillyeon)
https://github.com/w3c/badging/issues/112
1 issues closed:
- The badging API is not supported on Chromium-based browsers running on Android. https://github.com/w3c/badging/issues/112
* w3c/FileAPI (+1/-1/💬4)
1 issues created:
- Meta - make reading algorithms more explicit (by mkruisselbrink)
https://github.com/w3c/FileAPI/issues/199 [TPAC2024]
4 issues received 4 new comments:
- #179 Consider adding `blob.dataUrl()` method, or some other analogue to `readAsDataURL` (1 by dmurph)
https://github.com/w3c/FileAPI/issues/179 [feature request] [TPAC2024]
- #157 Async factory methods for Blob and File (1 by dmurph)
https://github.com/w3c/FileAPI/issues/157 [TPAC2024]
- #140 Consider Blob.fromStream (returns a Promise<Blob>) (1 by dmurph)
https://github.com/w3c/FileAPI/issues/140 [feature request] [TPAC2024]
- #24 Add FileList constructor (1 by dmurph)
https://github.com/w3c/FileAPI/issues/24 [feature request] [TPAC2024]
1 issues closed:
- Async factory methods for Blob and File https://github.com/w3c/FileAPI/issues/157 [TPAC2024]
* w3c/gamepad (+2/-0/💬1)
2 issues created:
- It is unclear if the algorithm for gamepadconnected event matches implementations (by smaug----)
https://github.com/w3c/gamepad/issues/215
- Clarifying the mechanism for the user authorization for gamepads (by xingri)
https://github.com/w3c/gamepad/issues/214
1 issues received 1 new comments:
- #215 It is unclear if the algorithm for gamepadconnected event matches implementations (1 by nondebug)
https://github.com/w3c/gamepad/issues/215
* w3c/IndexedDB (+2/-0/💬13)
2 issues created:
- Auto-abort stuck transactions (by evanstade)
https://github.com/w3c/IndexedDB/issues/425
- Remove " The durability option is new in this edition. It is supported in Chrome 82, Edge 82, and Safari 15. " (by smaug----)
https://github.com/w3c/IndexedDB/issues/424
5 issues received 13 new comments:
- #424 Remove " The durability option is new in this edition. It is supported in Chrome 82, Edge 82, and Safari 15. " (5 by inexorabletash, smaug----)
https://github.com/w3c/IndexedDB/issues/424 [needs-pr]
- #423 Specify the exception for read failures arising due to partial data loss on the file system (4 by abhishek-shanthkumar, asutherland, evanstade)
https://github.com/w3c/IndexedDB/issues/423
- #422 TPAC 2024: Discussion Topics (1 by evanstade)
https://github.com/w3c/IndexedDB/issues/422 [TPAC2024]
- #333 Add a `closed` property on the db (2 by evanstade, jakearchibald)
https://github.com/w3c/IndexedDB/issues/333 [feature request] [TPAC2024]
- #34 Allow more explicit control over transaction lifetimes (1 by evanstade)
https://github.com/w3c/IndexedDB/issues/34 [feature request] [feedback wanted] [blink +1] [performance] [TPAC 2019] [TPAC2024]
* w3c/IntersectionObserver (+0/-0/💬1)
1 issues received 1 new comments:
- #525 Processing of intersection observers doesn't match implementations (1 by emilio)
https://github.com/w3c/IntersectionObserver/issues/525 [bug] [needs test] [actionable]
* w3c/manifest (+2/-1/💬3)
2 issues created:
- Clarify under which circumstances the `name` or `short_name` member wins (by christianliebel)
https://github.com/w3c/manifest/issues/1145
- Trim non-enum string members (`name`, `short_name`, etc.) (by christianliebel)
https://github.com/w3c/manifest/issues/1144
3 issues received 3 new comments:
- #1144 Trim non-enum string members (`name`, `short_name`, etc.) (1 by christianliebel)
https://github.com/w3c/manifest/issues/1144
- #1142 Clarify case-insensitive parsing for enum values (1 by christianliebel)
https://github.com/w3c/manifest/issues/1142
- #1138 "link capturing" on the web platform into an installed web app (1 by dmurph)
https://github.com/w3c/manifest/issues/1138 [TPAC2024]
1 issues closed:
- Trim non-enum string members (`name`, `short_name`, etc.) https://github.com/w3c/manifest/issues/1144
* w3c/screen-orientation (+0/-0/💬3)
2 issues received 3 new comments:
- #206 Add can-lock-orientation media feature to detect if locking is possible (2 by dmurph, marcoscaceres)
https://github.com/w3c/screen-orientation/issues/206
- #104 Promise for unlock()? (1 by dmurph)
https://github.com/w3c/screen-orientation/issues/104
* w3c/screen-wake-lock (+0/-0/💬6)
3 issues received 6 new comments:
- #352 Distinguish exceptions on .request() (2 by reillyeon, smaug----)
https://github.com/w3c/screen-wake-lock/issues/352
- #350 Require transient activation to request lock (3 by reillyeon, smaug----)
https://github.com/w3c/screen-wake-lock/issues/350
- #324 Should this prompt? (1 by reillyeon)
https://github.com/w3c/screen-wake-lock/issues/324
* w3c/uievents (+3/-0/💬0)
3 issues created:
- [event-algo] Remove "6.10. send click event" (by smaug----)
https://github.com/w3c/uievents/issues/386
- Proposal to support Keyboard Lock API (by xingri)
https://github.com/w3c/uievents/issues/385
- [PointerLock] Unifying the UI for user authorization for Pointer Lock API (by xingri)
https://github.com/w3c/uievents/issues/384
* w3c/web-locks (+1/-0/💬1)
1 issues created:
- Move to CR? (by saschanaz)
https://github.com/w3c/web-locks/issues/117
1 issues received 1 new comments:
- #117 Move to CR? (1 by inexorabletash)
https://github.com/w3c/web-locks/issues/117
* whatwg/dom (+0/-0/💬9)
3 issues received 9 new comments:
- #1308 Proposal: asynchronous event listeners (6 by WebReflection, annevk, flackr, mmocny, smaug----)
https://github.com/whatwg/dom/issues/1308 [needs implementer interest] [topic: events] [needs concrete proposal]
- #1287 `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (1 by ox-harris)
https://github.com/whatwg/dom/issues/1287 [topic: shadow] [needs implementer interest] [addition/proposal]
- #1213 Proposal for built-in method to synchronize elements with virtual DOM representation (2 by WebReflection, dead-claudia)
https://github.com/whatwg/dom/issues/1213 [needs implementer interest] [needs concrete proposal] [topic: nodes]
Pull requests
-------------
* w3c/manifest (+0/-0/💬3)
1 pull requests received 3 new comments:
- #1101 Add members for localization (3 by aphillips, christianliebel)
https://github.com/w3c/manifest/pull/1101
* w3c/screen-orientation (+0/-0/💬1)
1 pull requests received 1 new comments:
- #218 Consume user activation (1 by marcoscaceres)
https://github.com/w3c/screen-orientation/pull/218
* whatwg/webidl (+1/-0/💬0)
1 pull requests submitted:
- Update to HTML changes for ShadowRealms (by Ms2ger)
https://github.com/whatwg/webidl/pull/1437
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/badging
* https://github.com/w3c/contact-picker
* https://github.com/w3c/deviceorientation
* https://github.com/w3c/FileAPI
* https://github.com/w3c/gamepad
* https://github.com/w3c/geolocation-api
* https://github.com/w3c/image-resource
* https://github.com/w3c/IndexedDB
* https://github.com/w3c/IntersectionObserver
* https://github.com/w3c/manifest
* https://github.com/w3c/pointerlock
* https://github.com/w3c/push-api
* https://github.com/w3c/screen-orientation
* https://github.com/w3c/screen-wake-lock
* https://github.com/w3c/uievents
* https://github.com/w3c/web-locks
* https://github.com/w3c/web-share
* https://github.com/whatwg/dom
* https://github.com/whatwg/infra
* https://github.com/whatwg/webidl
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 September 2024 17:00:10 UTC