Web Applications Working Group - Activity in 2022
No matches.
TR publications
-
8 documents published.
-
ARIA in HTML published as a Recommendation. History of ARIA in HTML
-
Web Share API published as a Proposed Recommendation. History of Web Share API
-
Web Share API published as a Candidate Recommendation Draft. History of Web Share API
-
Web Application Manifest published as a Working Draft. History of Web Application Manifest
-
Selection API published as a Working Draft. History of Selection API
-
Screen Orientation published as a Working Draft. History of Screen Orientation
-
Gamepad published as a Working Draft. History of Gamepad
-
Contact Picker API published as a First Public Working Draft. History of Contact Picker API
-
GitHub
w3c/FileAPI
-
3 issues opened.
-
Function signature change: reading all bytes from a stream w3c/FileAPI#187, by @noamr.
-
Byte stream support for `stream()`? w3c/FileAPI#186, by @saschanaz.
-
Broken references in File API w3c/FileAPI#185, by @dontcallmedom-bot.
-
-
1 issue received 1 new comment.
w3c/manifest
-
1 issue opened.
-
fetched icons fail in chrome when same-origin policy is present w3c/manifest#1065, by @elandorr.
-
-
1 issue closed.
-
TPAC 2022 status report w3c/manifest#1046.
-
-
2 issues received 2 new comments.
-
w3c/manifest#663 (1 comment by @vincentmorneau)
-
Add manifest option for PWAs to be registered as scheme/protocol handlers w3c/manifest#846 (1 comment by @hanguokai)
-
w3c/uievents
-
2 issues opened.
-
definition of MouseEvent.clientX and clientY seems wrong w3c/uievents#339, by @allan-bonadio.
-
Wheel event groups are not defined w3c/uievents#338, by @dlrobertson.
-
w3c/ServiceWorker
-
2 issues opened.
-
Function signature change: reading all bytes from a stream w3c/ServiceWorker#1666, by @noamr.
-
`registerProtocolHandler` support triggering events in service worker instead of navigating to page w3c/ServiceWorker#1665, by @hanguokai.
-
-
4 issues received 8 new comments.
-
`registerProtocolHandler` support triggering events in service worker instead of navigating to page w3c/ServiceWorker#1665 (3 comments by @hanguokai)
-
How should import() work in service workers? w3c/ServiceWorker#1585 (3 comments by @jimmywarting, @mikemaccana)
-
Cache API Vary header processing should be clarified w3c/ServiceWorker#1609 (1 comment by @madsruben)
-
w3c/contact-picker
-
1 issue closed.
-
Prepare for W3C FPWD w3c/contact-picker#50.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Post FPWD updates w3c/contact-picker#53, by @himorin.
-
Update link to editor's draft as contact-api repo was renamed in cont… w3c/contact-picker#52, by @vivienlacourba.
-
-
1 pull request merged.
-
Update link to editor's draft as contact-api repo was renamed in cont… w3c/contact-picker#52.
-
-
1 pull request received 3 new comments.
w3c/badging
-
5 issues opened.
-
A means to associate a badge with an installed application w3c/badging#97, by @marcoscaceres.
-
Selectively exposing the API could be a fingerprinting vector w3c/badging#95, by @marcoscaceres.
-
Disassociate badging from manifest w3c/badging#94, by @marcoscaceres.
-
Should third-parties be allowed to use the API? w3c/badging#93, by @marcoscaceres.
-
Deal with non-fully active documents w3c/badging#92, by @marcoscaceres.
-
-
9 issues closed.
-
Notification Background Updates w3c/badging#28.
-
Would the browser icon also show a badge for "badged tabs"? w3c/badging#77.
-
badging without installing pwa w3c/badging#85.
-
Broken references in Badging API w3c/badging#89.
-
Android support, at least w3c/badging#87.
-
Should OS failures setting the badge reject the promise? w3c/badging#61.
-
Feature: Get current badge value w3c/badging#73.
-
Hide the badge or setting count to 0 w3c/badging#79.
-
TPAC 2022 status report w3c/badging#88.
-
-
15 issues received 31 new comments.
-
Selectively exposing the API could be a fingerprinting vector w3c/badging#95 (2 comments by @fallaciousreasoning, @marcoscaceres)
-
Should third-parties be allowed to use the API? w3c/badging#93 (2 comments by @fallaciousreasoning, @marcoscaceres)
-
Deal with non-fully active documents w3c/badging#92 (2 comments by @fallaciousreasoning, @marcoscaceres)
-
Would the browser icon also show a badge for "badged tabs"? w3c/badging#77 (1 comment by @marcoscaceres)
-
Should OS failures setting the badge reject the promise? w3c/badging#61 (1 comment by @marcoscaceres)
-
3 pull requests opened.
-
Spec rewrite to address open issues w3c/badging#98, by @marcoscaceres.
-
Switch WebApps WG w3c/badging#96, by @deniak.
-
Editorial: fixup global/this usage w3c/badging#91, by @marcoscaceres.
-
-
3 pull requests merged.
-
Switch WebApps WG w3c/badging#96.
-
Editorial: fixup global/this usage w3c/badging#91.
-
-
1 pull request closed.
-
chore: Fix broken links to within scope defintion w3c/badging#90.
-
-
2 pull requests received 2 new comments.
w3c/gamepad
-
2 issues opened.
-
Add a means to test the API w3c/gamepad#175, by @marcoscaceres.
-
move vibrationActuator to main spec w3c/gamepad#173, by @marcoscaceres.
-
-
1 issue closed.
-
TPAC 2022 status report w3c/gamepad#169.
-
-
1 issue received 9 new comments.
-
1 pull request opened.
-
Update getGamepads to include steps for copying gamepads w3c/gamepad#172, by @nondebug.
-
-
1 pull request merged.
-
extensions: Add vibrationActuator and dual-rumble effect w3c/gamepad#163.
-
-
3 pull requests received 10 new comments.
-
Enhance Gamepad interface description for Touch w3c/gamepad#168 (6 comments by @bradleyneedham, @marcoscaceres, @nondebug)
-
extensions: Add vibrationActuator and dual-rumble effect w3c/gamepad#163 (2 comments by @cabanier, @marcoscaceres)
-
w3c/web-share
-
3 issues opened.
-
Support additional media types? w3c/web-share#258, by @ktk.
-
Indicate explicitly the intent of the Web Share API regarding cross-origin w3c/web-share#255, by @siusin.
-
Is implemented w3c/web-share#254, by @lemanschik.
-
-
2 issues closed.
-
Indicate explicitly the intent of the Web Share API regarding cross-origin w3c/web-share#255.
-
Is implemented w3c/web-share#254.
-
-
2 issues received 5 new comments.
-
Indicate explicitly the intent of the Web Share API regarding cross-origin w3c/web-share#255 (1 comment by @siusin)
-
2 pull requests opened.
-
Fix capitalisation of heading w3c/web-share#257, by @Krinkle.
-
Editorial: address Proposed Recommendation Feedback w3c/web-share#256, by @marcoscaceres.
-
-
2 pull requests merged.
-
Fix capitalisation of heading w3c/web-share#257.
-
Editorial: address Proposed Recommendation Feedback w3c/web-share#256.
-
w3c/IndexedDB
-
1 issue closed.
-
Status report and planning for TPAC 2021 w3c/IndexedDB#364.
-
-
1 issue received 1 new comment.
-
w3c/IndexedDB#224 (1 comment by @jimmywarting)
-
-
1 pull request received 1 new comment.
w3c/screen-orientation
-
1 pull request opened.
-
Tidied up document using tidy-html5 w3c/screen-orientation#241, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: relocate page visibility change step to HTML w3c/screen-orientation#240.
-
w3c/web-locks
-
1 issue opened.
-
Call for Consensus: publish First Public Working Draft w3c/web-locks#112, by @marcoscaceres.
-
-
1 issue closed.
-
TPAC 2022 status report w3c/web-locks#111.
-
-
1 issue received 1 new comment.
w3c/uievents-code
-
1 issue opened.
-
Unicode terminology w3c/uievents-code#36, by @xfq.
-
-
1 issue received 1 new comment.
w3c/uievents-key
-
2 issues opened.
-
Update UAX #15 to the latest version w3c/uievents-key#59, by @xfq.
-
Definition of 'string' w3c/uievents-key#58, by @xfq.
-
w3c/pointerlock
-
1 issue opened.
-
Feature Request: Allow for a pointerevent-scoped pointerlock with less restrictions w3c/pointerlock#81, by @Strepto.
-
-
2 issues received 3 new comments.
-
Feature Request: Allow for a pointerevent-scoped pointerlock with less restrictions w3c/pointerlock#81 (2 comments by @mustaqahmed, @Strepto)
-
w3c/pointerlock#42 (1 comment by @BlobTheKat)
-
w3c/webappswg
-
1 issue received 1 new comment.
-
Explore the possibility of doing more joint deliverables with DAS w3c/webappswg#90 (1 comment by @anssiko)
-
w3c/push-api
-
1 issue opened.
-
New push subscription MUST have an endpoint that's different from the original w3c/push-api#357, by @collimarco.
-
-
2 issues received 2 new comments.
-
New push subscription MUST have an endpoint that's different from the original w3c/push-api#357 (1 comment by @collimarco)
TR publications
-
9 documents published.
-
Web Share API published twice as a Candidate Recommendation Draft. History of Web Share API
-
File API published twice as a Working Draft. History of File API
-
Screen Orientation published 3 times as a Working Draft. History of Screen Orientation
-
Web Application Manifest published twice as a Working Draft. History of Web Application Manifest
-
Participants
-
1 participant joined.
-
Simon Pieters (Mozilla Foundation) joined.
-
-
1 participant left.
-
Simon Pieters (Mozilla Foundation) left.
-
GitHub
w3c/web-locks
-
2 issues closed.
-
Replace Origin references with Storage Key w3c/web-locks#74.
-
2 issues received 5 new comments.
-
TPAC 2022 status report w3c/web-locks#111 (3 comments by @inexorabletash, @marcoscaceres, @saschanaz)
-
Throwing a thenable object in locks.requests callback will implicitly invoke its `.then()` w3c/web-locks#77 (2 comments by @inexorabletash)
-
-
1 pull request merged.
-
Adopt terms from Storage spec w3c/web-locks#75.
-
-
1 pull request received 10 new comments.
w3c/manifest
-
2 issues opened.
-
Ability to override the back button behavior w3c/manifest#1064, by @christianliebel.
-
ReSpec errors for navigate and origin references w3c/manifest#1061, by @alancutter.
-
-
5 issues received 11 new comments.
-
Ability to override the back button behavior w3c/manifest#1064 (4 comments by @christianliebel, @kenchris)
-
`id` member reuse in MiniApps Manifest (no `document URL`) w3c/manifest#1048 (2 comments by @dmurph, @espinr)
-
Add option to disable built-in navigation gestures w3c/manifest#1041 (1 comment by @petermakeswebsites)
-
-
2 pull requests opened.
-
Fix broken active-document reference w3c/manifest#1063, by @alancutter.
-
Export processed manifest and application context definitions w3c/manifest#1062, by @alancutter.
-
-
3 pull requests merged.
-
Export processed manifest and application context definitions w3c/manifest#1062.
-
Define an algorithm for launching a web app w3c/manifest#1056.
-
Fix broken active-document reference w3c/manifest#1063.
-
-
2 pull requests received 18 new comments.
-
editorial: Move the definition of display-mode back to APPMANIFEST. w3c/manifest#1039 (1 comment by @ewilligers)
w3c/FileAPI
-
2 pull requests opened.
-
Editorial: slice blob should use nullable args w3c/FileAPI#184, by @dlrobertson.
-
editorial: make Blob.slice a separate algorithm w3c/FileAPI#183, by @dlrobertson.
-
-
2 pull requests merged.
-
Editorial: slice blob should use nullable args w3c/FileAPI#184.
-
editorial: make Blob.slice a separate algorithm w3c/FileAPI#183.
-
-
2 pull requests received 10 new comments.
-
editorial: make Blob.slice a separate algorithm w3c/FileAPI#183 (6 comments by @annevk, @dlrobertson, @mkruisselbrink, @w3cbot)
-
Editorial: slice blob should use nullable args w3c/FileAPI#184 (4 comments by @annevk, @dlrobertson, @w3cbot)
-
w3c/uievents-code
-
1 issue received 5 new comments.
w3c/uievents-key
-
1 issue received 5 new comments.
w3c/screen-orientation
-
1 issue opened.
-
Switch to "navigables" instead of browsing contexts w3c/screen-orientation#238, by @marcoscaceres.
-
-
2 issues closed.
-
Switch to "navigables" instead of browsing contexts w3c/screen-orientation#238.
-
"reject and nullify the current lock promise" and tasks w3c/screen-orientation#234.
-
-
1 issue received 6 new comments.
-
Add can-lock-orientation media feature to detect if locking is possible w3c/screen-orientation#206 (6 comments by @annevk, @makotokato, @marcoscaceres)
-
-
2 pull requests opened.
-
Editorial: relocate page visibility change step to HTML w3c/screen-orientation#240, by @marcoscaceres.
-
Editorial: switch to navigables w3c/screen-orientation#239, by @marcoscaceres.
-
-
2 pull requests merged.
-
Editorial: switch to navigables w3c/screen-orientation#239.
-
Editorial: rewrite parallel steps w3c/screen-orientation#236.
-
-
1 pull request closed.
-
Restrict locking to visible documents w3c/screen-orientation#230.
-
-
4 pull requests received 10 new comments.
-
Consume user activation w3c/screen-orientation#218 (4 comments by @LJWatson, @marcoscaceres, @michaelwasserman)
-
Prevent hidden documents from locking orientation w3c/screen-orientation#232 (3 comments by @makotokato, @marcoscaceres)
-
Editorial: relocate page visibility change step to HTML w3c/screen-orientation#240 (2 comments by @marcoscaceres)
-
w3c/ServiceWorker
-
3 issues opened.
-
How to get correct connectStart/End values of a proxied http request inside service worker? w3c/ServiceWorker#1663, by @xiaofud.
-
clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` w3c/ServiceWorker#1662, by @JakobJingleheimer.
-
Add claim option to register() w3c/ServiceWorker#1661, by @alancutter.
-
-
1 issue received 1 new comment.
-
w3c/ServiceWorker#977 (1 comment by @nnmrts)
-
-
1 pull request opened.
-
Increment encoded/decoded body size for constructed responses w3c/ServiceWorker#1664, by @noamr.
-
-
2 pull requests merged.
-
Increment encoded/decoded body size for constructed responses w3c/ServiceWorker#1664.
-
Abort with fetch controller's error in Handle Fetch w3c/ServiceWorker#1655.
-
-
1 pull request received 2 new comments.
-
Abort with fetch controller's error in Handle Fetch w3c/ServiceWorker#1655 (2 comments by @jakearchibald, @nidhijaju)
-
w3c/gamepad
-
1 issue received 3 new comments.
-
Please don't restrict to a secure context w3c/gamepad#145 (3 comments by @aguegu, @dinther, @marcoscaceres)
-
w3c/manifest-app-info
-
1 issue opened.
-
Should the `string` type point to https://infra.spec.whatwg.org/#string? w3c/manifest-app-info#61, by @tomayac.
-
w3c/web-share
-
1 issue opened.
-
Call for consensus: publish as a Proposed Recommendation w3c/web-share#253, by @marcoscaceres.
-
-
2 issues closed.
-
Call for consensus: publish as a Proposed Recommendation w3c/web-share#253.
-
Permissions policy 'self' is at risk w3c/web-share#169.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Editorial: remove feature at risk for Permissions Policy w3c/web-share#252, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: remove feature at risk for Permissions Policy w3c/web-share#252.
-
w3c/webappswg
-
1 issue opened.
-
Explore the possibility of doing more joint deliverables with DAS w3c/webappswg#90, by @marcoscaceres.
-
-
1 issue closed.
-
Initiate wide review of Web Share API w3c/webappswg#27.
-
-
2 issues received 3 new comments.
-
Explore the possibility of doing more joint deliverables with DAS w3c/webappswg#90 (2 comments by @anssiko, @marcoscaceres)
-
-
1 pull request opened.
-
Proposal: Add join deliverables w3c/webappswg#89, by @marcoscaceres.
-
w3c/uievents
-
1 issue received 4 new comments.
w3c/IndexedDB
-
1 issue opened.
-
1 issue closed.
-
1 issue received 8 new comments.
-
Clarify expected index key generation behavior when extracting a key from a value using a key path list w3c/IndexedDB#394 (8 comments by @iartemiev, @inexorabletash)
-
TR publications
-
20 documents published.
-
The Screen Orientation API published 15 times as a Working Draft. History of The Screen Orientation API
-
Web Application Manifest published as a Working Draft. History of Web Application Manifest
-
File API published twice as a Working Draft. History of File API
-
Gamepad published as a Working Draft. History of Gamepad
-
Participants
-
3 participants joined.
-
Alan Cutter (Google LLC) joined.
-
He Huang (Lenovo) joined.
-
Ruilong Lian (Dingdao) joined.
-
-
2 participants left.
-
Travis Leithead (W3C Invited Experts) left.
-
Yongjun Kim (Samsung Electronics Co., Ltd.) left.
-
-
1 organization joined.
-
Lenovo joined.
-
GitHub
w3c/manifest
-
5 issues opened.
-
About updating the manifest w3c/manifest#1060, by @NhutTran98.
-
Manifest: property 'src' ignored, URL is invalid. w3c/manifest#1059, by @wenanoshe.
-
W3c w3c/manifest#1057, by @fieropheonix6.
-
chrome://credits/ w3c/manifest#1053, by @fieropheonix6.
-
-
3 issues closed.
-
Manifest: property 'src' ignored, URL is invalid. w3c/manifest#1059.
-
W3c w3c/manifest#1057.
-
chrome://credits/ w3c/manifest#1053.
-
-
5 issues received 13 new comments.
-
Manifest: property 'src' ignored, URL is invalid. w3c/manifest#1059 (7 comments by @dmurph, @marcoscaceres, @wenanoshe)
-
About updating the manifest w3c/manifest#1060 (3 comments by @alancutter, @marcoscaceres, @NhutTran98)
-
-
2 pull requests opened.
-
chore: update "processing a manifest"'s signature w3c/manifest#1058, by @nicolo-ribaudo.
-
Define an algorithm for launching a web app w3c/manifest#1056, by @alancutter.
-
-
1 pull request merged.
-
chore: update "processing a manifest"'s signature w3c/manifest#1058.
-
-
2 pull requests received 18 new comments.
-
Define an algorithm for launching a web app w3c/manifest#1056 (15 comments by @alancutter, @marcoscaceres)
-
chore: update "processing a manifest"'s signature w3c/manifest#1058 (3 comments by @marcoscaceres, @nicolo-ribaudo, @w3cbot)
-
w3c/ServiceWorker
-
1 issue opened.
-
Notion of a "session" across same-origin navigations w3c/ServiceWorker#1660, by @noamr.
-
-
1 issue received 1 new comment.
-
allow service workers to created nested dedicated workers w3c/ServiceWorker#1529 (1 comment by @ian97531)
-
-
2 pull requests opened.
-
Editorial: HTML removed JavaScript from the realm w3c/ServiceWorker#1659, by @annevk.
-
Update usages of module fetching html algorithms w3c/ServiceWorker#1658, by @nicolo-ribaudo.
-
-
3 pull requests received 7 new comments.
-
Update usages of module fetching html algorithms w3c/ServiceWorker#1658 (4 comments by @nicolo-ribaudo, @triple-underscore, @w3cbot)
-
Editorial: HTML removed JavaScript from the realm w3c/ServiceWorker#1659 (2 comments by @annevk, @w3cbot)
-
Abort with fetch controller's error in Handle Fetch w3c/ServiceWorker#1655 (1 comment by @nidhijaju)
-
w3c/screen-orientation
-
9 issues opened.
-
Split out the safety checks into a shared algorithm w3c/screen-orientation#237, by @marcoscaceres.
-
"reject and nullify the current lock promise" and tasks w3c/screen-orientation#234, by @annevk.
-
"reject and nullify the current lock promise" nit w3c/screen-orientation#233, by @annevk.
-
Clarify manifest's fullscreen can be considered a pre-lock condition. w3c/screen-orientation#224, by @marcoscaceres.
-
Should hidden documents be allowed to change the orientation? w3c/screen-orientation#221, by @marcoscaceres.
-
HTML integration w3c/screen-orientation#219, by @marcoscaceres.
-
Moving window from one screen to another w3c/screen-orientation#211, by @marcoscaceres.
-
Require a gesture? w3c/screen-orientation#210, by @marcoscaceres.
-
Specify .lock() / .unlock() dependency on fullscreen API w3c/screen-orientation#209, by @marcoscaceres.
-
-
31 issues closed.
-
"reject and nullify the current lock promise" nit w3c/screen-orientation#233.
-
Deal with fragment navigation w3c/screen-orientation#87.
-
Orientation angle to orientation type mapping for 2-in-1 devices w3c/screen-orientation#101.
-
Specify .lock() / .unlock() dependency on fullscreen API w3c/screen-orientation#209.
-
Deprecate angle? w3c/screen-orientation#162.
-
Spec is unclear about how locks work across multiple screens and display context switches w3c/screen-orientation#105.
-
Clarification on animation frame task w3c/screen-orientation#136.
-
Link Screen Orientation with Fullscreen more cleanly w3c/screen-orientation#62.
-
Test coverage w3c/screen-orientation#119.
-
Clarify how to initialize the screen orientation w3c/screen-orientation#145.
-
Definition of default orientation w3c/screen-orientation#150.
-
Doublecheck lock(), event, re/unlock() behaviors w3c/screen-orientation#151.
-
unlocking during event dispatching is undefined w3c/screen-orientation#173.
-
Privacy notes are overly dismissive w3c/screen-orientation#181.
-
Should the -secondary orientations be exposed? w3c/screen-orientation#188.
-
Page visibility transition can fire when false/true/false happens within a frame w3c/screen-orientation#179.
-
lock() should not fail if another lock() is called in the change event w3c/screen-orientation#184.
-
Heads up: refs to `pagevisibility` (external now visibile) about to be removed w3c/screen-orientation#205.
-
Clarify manifest's fullscreen can be considered a pre-lock condition. w3c/screen-orientation#224.
-
Orientation angle cannot be precisely mapped to orientation type for devices with 1:1 screen size ratio w3c/screen-orientation#99.
-
Nested browsing contexts cannot be accessed `in parallel` w3c/screen-orientation#193.
-
Apply an orientation lock rejects its own newly created promise w3c/screen-orientation#198.
-
Browsing contexts do not have a document w3c/screen-orientation#192.
-
Face up and face down w3c/screen-orientation#168.
-
Clarify in which animation frame task events are fired w3c/screen-orientation#97.
-
Moving window from one screen to another w3c/screen-orientation#211.
-
Add internationalization considerations section w3c/screen-orientation#194.
-
Replace usage of "responsible document" w3c/screen-orientation#207.
-
Status report and planning for TPAC 2021 w3c/screen-orientation#204.
-
TPAC 2022 status report w3c/screen-orientation#208.
-
Improve hooks with Page Visibility. w3c/screen-orientation#77.
-
-
2 issues reopened.
-
Complete self-reviews w3c/screen-orientation#201, by @marcoscaceres.
-
Promise for unlock()? w3c/screen-orientation#104, by @marcoscaceres.
-
-
30 issues received 53 new comments.
-
Add can-lock-orientation media feature to detect if locking is possible w3c/screen-orientation#206 (12 comments by @annevk, @domenic, @marcoscaceres, @saschanaz)
-
w3c/screen-orientation#150 (3 comments by @marcoscaceres)
-
w3c/screen-orientation#101 (2 comments by @marcoscaceres)
-
"reject and nullify the current lock promise" and tasks w3c/screen-orientation#234 (1 comment by @marcoscaceres)
-
Specify .lock() / .unlock() dependency on fullscreen API w3c/screen-orientation#209 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#162 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#105 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#136 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#62 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#119 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#145 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#151 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#173 (1 comment by @marcoscaceres)
-
Page visibility transition can fire when false/true/false happens within a frame w3c/screen-orientation#179 (1 comment by @marcoscaceres)
-
lock() should not fail if another lock() is called in the change event w3c/screen-orientation#184 (1 comment by @marcoscaceres)
-
Heads up: refs to `pagevisibility` (external now visibile) about to be removed w3c/screen-orientation#205 (1 comment by @marcoscaceres)
-
Clarify manifest's fullscreen can be considered a pre-lock condition. w3c/screen-orientation#224 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#99 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#168 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#97 (1 comment by @annevk)
-
w3c/screen-orientation#87 (1 comment by @annevk)
-
Add internationalization considerations section w3c/screen-orientation#194 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#77 (1 comment by @marcoscaceres)
-
-
20 pull requests opened.
-
Editorial: rewrite parallel steps w3c/screen-orientation#236, by @marcoscaceres.
-
Editorial: always null check orientationPendingPromise w3c/screen-orientation#235, by @marcoscaceres.
-
Prevent hidden documents from locking orientation w3c/screen-orientation#232, by @marcoscaceres.
-
Allow unlock() to return a promise w3c/screen-orientation#231, by @marcoscaceres.
-
Restrict locking to visible documents w3c/screen-orientation#230, by @marcoscaceres.
-
Only unlock top-level docs w3c/screen-orientation#229, by @marcoscaceres.
-
Tidied up document using tidy-html5 w3c/screen-orientation#228, by @marcoscaceres.
-
Tidied up document using tidy-html5 w3c/screen-orientation#227, by @marcoscaceres.
-
Minor index.html cleanup w3c/screen-orientation#226, by @michaelwasserman.
-
Tidied up document using tidy-html5 w3c/screen-orientation#225, by @marcoscaceres.
-
chore: Request full screen + Small fixes w3c/screen-orientation#223, by @marcoscaceres.
-
chore: add demo page w3c/screen-orientation#222, by @marcoscaceres.
-
Editorial: rewrite of handle page visibility changes w3c/screen-orientation#220, by @marcoscaceres.
-
Consume user activation w3c/screen-orientation#218, by @marcoscaceres.
-
Clarify that locking to every orientation might not be supported w3c/screen-orientation#217, by @marcoscaceres.
-
Editorial: fix walk down all documents from top w3c/screen-orientation#216, by @marcoscaceres.
-
Rewrite privacy considerations section w3c/screen-orientation#215, by @marcoscaceres.
-
Tidied up document using tidy-html5 w3c/screen-orientation#214, by @marcoscaceres.
-
Adjust dfn markup of "change" event w3c/screen-orientation#213, by @tidoust.
-
Tidied up document using tidy-html5 w3c/screen-orientation#212, by @marcoscaceres.
-
-
12 pull requests merged.
-
Editorial: always null check orientationPendingPromise w3c/screen-orientation#235.
-
Only unlock top-level docs w3c/screen-orientation#229.
-
Tidied up document using tidy-html5 w3c/screen-orientation#228.
-
Tidied up document using tidy-html5 w3c/screen-orientation#227.
-
Rewrite privacy considerations section w3c/screen-orientation#215.
-
Minor index.html cleanup w3c/screen-orientation#226.
-
chore: Request full screen + Small fixes w3c/screen-orientation#223.
-
chore: add demo page w3c/screen-orientation#222.
-
Editorial: fix walk down all documents from top w3c/screen-orientation#216.
-
Editorial: rewrite of handle page visibility changes w3c/screen-orientation#220.
-
Clarify that locking to every orientation might not be supported w3c/screen-orientation#217.
-
Adjust dfn markup of "change" event w3c/screen-orientation#213.
-
-
3 pull requests closed.
-
Tidied up document using tidy-html5 w3c/screen-orientation#225.
-
Tidied up document using tidy-html5 w3c/screen-orientation#212.
-
Tidied up document using tidy-html5 w3c/screen-orientation#214.
-
-
10 pull requests received 64 new comments.
-
Rewrite privacy considerations section w3c/screen-orientation#215 (20 comments by @annevk, @marcoscaceres)
-
Consume user activation w3c/screen-orientation#218 (14 comments by @marcoscaceres, @saschanaz, @smaug----)
-
Editorial: rewrite parallel steps w3c/screen-orientation#236 (6 comments by @annevk, @marcoscaceres)
-
Prevent hidden documents from locking orientation w3c/screen-orientation#232 (3 comments by @annevk, @marcoscaceres)
-
Allow unlock() to return a promise w3c/screen-orientation#231 (3 comments by @annevk, @marcoscaceres)
-
Clarify that locking to every orientation might not be supported w3c/screen-orientation#217 (3 comments by @annevk, @marcoscaceres)
-
Editorial: rewrite of handle page visibility changes w3c/screen-orientation#220 (2 comments by @marcoscaceres)
-
Editorial: always null check orientationPendingPromise w3c/screen-orientation#235 (1 comment by @annevk)
-
w3c/push-api
-
1 issue received 1 new comment.
-
Documentation: It's not clear how to specify the push service w3c/push-api#355 (1 comment by @marcoscaceres)
-
w3c/gamepad
-
1 issue closed.
-
"current settings object's relevant global object" is not defined w3c/gamepad#170.
-
-
1 issue received 1 new comment.
-
GamepadHapticActuator pulse should support frequency parameter w3c/gamepad#148 (1 comment by @cabanier)
-
-
1 pull request merged.
-
Replace "current settings object's relevant global object" w3c/gamepad#171.
-
-
3 pull requests received 3 new comments.
w3c/IndexedDB
-
1 issue received 4 new comments.
-
Clarify the handling of +0 and -0 in keys w3c/IndexedDB#375 (4 comments by @inexorabletash, @marcoscaceres, @szewai)
-
w3c/FileAPI
-
1 issue reopened.
-
Christoc90 w3c/FileAPI#181, by @Christoc90.
-
-
2 pull requests opened.
-
Meta: export Blob's get stream algorithm w3c/FileAPI#182, by @annevk.
-
Correct typo in example blob URL w3c/FileAPI#180, by @wh0.
-
-
2 pull requests merged.
-
Meta: export Blob's get stream algorithm w3c/FileAPI#182.
-
Correct typo in example blob URL w3c/FileAPI#180.
-
-
1 pull request received 1 new comment.
w3c/badging
-
1 issue opened.
-
Broken references in Badging API w3c/badging#89, by @dontcallmedom-bot.
-
-
1 pull request opened.
-
chore: Fix broken links to within scope defintion w3c/badging#90, by @NotWoods.
-
w3c/using-aria
-
1 issue opened.
-
Example in second rule is wrong because tab has "Children Presentational" w3c/using-aria#58, by @JAWS-test.
-
w3c/uievents
-
1 issue opened.
-
Remove load/unload/abort/error events w3c/uievents#335, by @annevk.
-
w3c/manifest-app-info
-
1 issue closed.
-
consider ranaming "platform" w3c/manifest-app-info#55.
-
-
1 pull request merged.
-
Add form_factor field to screenshot member w3c/manifest-app-info#59.
-
-
1 pull request received 2 new comments.
w3c/web-share
-
1 issue received 1 new comment.
TR publications
-
4 documents published.
-
ARIA in HTML published as a Recommendation. History of ARIA in HTML
-
Web Share API published as a Candidate Recommendation Draft. History of Web Share API
-
Indexed Database API 3.0 published as a Working Draft. History of Indexed Database API 3.0
-
UI Events published as a Working Draft. History of UI Events
-
Past meetings
Participants
-
6 participants joined.
-
Andrey Zaytsev (Google LLC) joined.
-
Ella Ge (Google LLC) joined.
-
Simeon Vincent (Google LLC) joined.
-
Greg Whitworth (Salesforce) joined.
-
Kouhei Ueno (Google LLC) joined.
-
Louise Brett (Google LLC) joined.
-
-
1 organization joined.
-
Salesforce joined.
-
GitHub
w3c/push-api
-
1 issue received 2 new comments.
w3c/manifest
-
3 issues opened.
-
Security Updates Scope | Samsung Mobile Security w3c/manifest#1052, by @fieropheonix6.
-
Nativejet w3c/manifest#1051, by @fieropheonix6.
-
w3cman w3c/manifest#1050, by @fieropheonix6.
-
-
4 issues closed.
-
Security Updates Scope | Samsung Mobile Security w3c/manifest#1052.
-
Nativejet w3c/manifest#1051.
-
w3cman w3c/manifest#1050.
-
Display mode "standalone" inconsistently handled by browsers w3c/manifest#673.
-
-
6 issues received 8 new comments.
-
w3c/manifest#673 (1 comment by @christianliebel)
-
w3c/manifest#539 (1 comment by @javadch)
-
meta: see web almanac for any insights about manifest usage w3c/manifest#987 (1 comment by @christianliebel)
-
1 pull request received 9 new comments.
-
Remove beforeinstallprompt and appinstalled events. w3c/manifest#836 (9 comments by @fabricedesre, @marcoscaceres, @mgiuca, @msimic)
-
w3c/contact-picker
-
2 issues opened.
-
Prepare for W3C FPWD w3c/contact-picker#50, by @marcoscaceres.
-
Call for Consensus: publish Contact Picker API as First Public Working Draft w3c/contact-picker#49, by @marcoscaceres.
-
-
2 issues closed.
-
Move repo to W3C w3c/contact-picker#46.
-
TPAC 2022 status report w3c/contact-picker#48.
-
-
3 issues received 5 new comments.
-
1 pull request opened.
-
Use FPWD template for spec w3c/contact-picker#51, by @rayankans.
-
-
1 pull request received 3 new comments.
w3c/ServiceWorker
-
6 issues received 7 new comments.
-
w3c/ServiceWorker#578 (1 comment by @nin-jin)
-
should FetchEvent.request.signal reflect abort status of outer request? w3c/ServiceWorker#1544 (1 comment by @JakobJingleheimer)
-
w3c/ServiceWorker#980 (1 comment by @gustavopch)
-
allow service workers to created nested dedicated workers w3c/ServiceWorker#1529 (1 comment by @cohenerickson)
w3c/web-share
-
1 issue opened.
-
"current settings object's relevant global object" is not defined w3c/web-share#250, by @Ms2ger.
-
-
1 issue closed.
-
"current settings object's relevant global object" is not defined w3c/web-share#250.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Editorial: use this' relevant global object w3c/web-share#251, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: use this' relevant global object w3c/web-share#251.
-
w3c/IndexedDB
-
1 issue received 1 new comment.
w3c/gamepad
-
1 issue opened.
-
"current settings object's relevant global object" is not defined w3c/gamepad#170, by @Ms2ger.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Replace "current settings object's relevant global object" w3c/gamepad#171, by @nondebug.
-
-
1 pull request received 5 new comments.
w3c/uievents-key
-
1 issue opened.
-
Tasks for wide review w3c/uievents-key#57, by @LJWatson.
-
-
1 issue closed.
-
Get horizontal review for UIEvents KeyboardEvent Key w3c/uievents-key#56.
-
-
1 issue received 1 new comment.
w3c/uievents-code
-
1 issue opened.
-
Tasks for wide review w3c/uievents-code#35, by @LJWatson.
-
w3c/pointerlock
-
1 issue closed.
-
Clarify how requestPointerLock relies on user activation w3c/pointerlock#67.
-
-
3 issues received 5 new comments.
-
Clarify how requestPointerLock relies on user activation w3c/pointerlock#67 (1 comment by @mustaqahmed)
w3c/manifest-app-info
-
1 pull request received 1 new comment.
w3c/FileAPI
-
1 issue received 1 new comment.
w3c/uievents
-
1 issue received 2 new comments.
-
"keyCode" is the only way to work with KeyboardEvents now w3c/uievents#267 (2 comments by @robertknight)
-
TR publications
-
3 documents published.
-
Web Share API published as a Candidate Recommendation Snapshot. History of Web Share API
-
Web Share API published as a Candidate Recommendation Draft. History of Web Share API
-
Web Share API published as a Working Draft. History of Web Share API
-
Participants
-
1 participant joined.
-
Ben Francis (W3C Invited Experts) joined.
-
GitHub
w3c/ServiceWorker
-
2 issues opened.
-
cache.addAll accepts an array of URLs (not just requests) w3c/ServiceWorker#1657, by @noamr.
-
Service Worker local variables disappear for no reason w3c/ServiceWorker#1656, by @ZengTianShengZ.
-
-
2 issues closed.
-
cache.addAll accepts an array of URLs (not just requests) w3c/ServiceWorker#1657.
-
Service Worker local variables disappear for no reason w3c/ServiceWorker#1656.
-
-
4 issues received 6 new comments.
-
cache.addAll accepts an array of URLs (not just requests) w3c/ServiceWorker#1657 (2 comments by @noamr, @wanderview)
-
w3c/ServiceWorker#765 (1 comment by @Kle0s)
-
Service Worker local variables disappear for no reason w3c/ServiceWorker#1656 (1 comment by @jakearchibald)
-
1 pull request opened.
-
Abort with fetch controller's error in Handle Fetch w3c/ServiceWorker#1655, by @nidhijaju.
-
-
1 pull request received 4 new comments.
-
Abort with fetch controller's error in Handle Fetch w3c/ServiceWorker#1655 (4 comments by @jakearchibald, @noamr)
-
w3c/manifest
-
2 issues opened.
-
About update icon in web app manifest w3c/manifest#1049, by @nhuttm.
-
`id` member reuse in MiniApps Manifest (no `document URL`) w3c/manifest#1048, by @espinr.
-
-
1 issue closed.
-
About update icon in web app manifest w3c/manifest#1049.
-
-
6 issues received 17 new comments.
-
Web Manifest Overrides w3c/manifest#1045 (7 comments by @aarongustafson, @bathos, @mgiuca, @tomayac)
-
-
1 pull request closed.
-
Rename .pr-preview.json to -preview.json w3c/manifest#1044.
-
-
2 pull requests received 4 new comments.
-
Add scope conflict section about same-origin and nested scopes w3c/manifest#1034 (2 comments by @marcoscaceres)
w3c/web-share
-
1 issue opened.
-
Explain implementation status w3c/web-share#247, by @marcoscaceres.
-
-
1 issue closed.
-
Explain implementation status w3c/web-share#247.
-
-
9 issues received 11 new comments.
-
Note about choice of USVString imprecise w3c/web-share#152 (3 comments by @aphillips, @marcoscaceres)
-
Mitigating user expectation mismatches with shared URL w3c/web-share#186 (1 comment by @marcoscaceres)
-
Request to move privacy-related requirements to normative text w3c/web-share#187 (1 comment by @marcoscaceres)
-
w3c/web-share#6 (1 comment by @marcoscaceres)
-
-
2 pull requests opened.
-
chore: auto-publish as CRD w3c/web-share#249, by @marcoscaceres.
-
Editorial: describe implementation status situation w3c/web-share#248, by @marcoscaceres.
-
-
2 pull requests merged.
-
chore: auto-publish as CRD w3c/web-share#249.
-
Editorial: describe implementation status situation w3c/web-share#248.
-
w3c/IndexedDB
-
2 issues opened.
-
Is it really true that StructuredDeserialize can't throw in this spec? w3c/IndexedDB#391, by @mkruisselbrink.
-
Future: Support Tuples as compound keys w3c/IndexedDB#390, by @inexorabletash.
-
-
1 issue closed.
-
FPWD of v3? w3c/IndexedDB#268.
-
-
3 issues received 4 new comments.
-
1 pull request opened.
-
Rename 'array key' to 'composite key' w3c/IndexedDB#392, by @inexorabletash.
-
w3c/FileAPI
-
1 issue opened.
-
1 issue received 8 new comments.
-
Consider adding `blob.dataUrl()` method, or some other analogue to `readAsDataURL` w3c/FileAPI#179 (8 comments by @annevk, @josephrocca, @mkruisselbrink)
-
w3c/gamepad
-
2 issues received 2 new comments.
-
GamepadHapticActuator pulse should support frequency parameter w3c/gamepad#148 (1 comment by @cabanier)
-
1 pull request received 7 new comments.
-
Enhance Gamepad interface description for Touch w3c/gamepad#168 (7 comments by @bradleyneedham, @nondebug)
-
w3c/uievents
-
1 issue received 3 new comments.
w3c/manifest-app-info
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Add form_factor field to screenshot member w3c/manifest-app-info#59, by @philloooo.
-
-
1 pull request merged.
-
Fix iPadOS label w3c/manifest-app-info#56.
-
-
2 pull requests received 4 new comments.
-
Add form_factor field to screenshot member w3c/manifest-app-info#59 (3 comments by @aarongustafson, @philloooo)
-
w3c/webappswg
-
1 issue opened.
-
WebApps agenda TPAC 2022 w3c/webappswg#88, by @LJWatson.
-
-
1 issue closed.
-
WebApps agenda TPAC 2022 w3c/webappswg#88.
-
-
2 issues received 5 new comments.
w3c/web-locks
-
1 issue opened.
-
TPAC 2022 status report w3c/web-locks#111, by @inexorabletash.
-
-
1 issue received 7 new comments.
-
TPAC 2022 status report w3c/web-locks#111 (7 comments by @aboodman, @inexorabletash, @marcoscaceres, @saschanaz, @siusin)
-
w3c/uievents-code
-
1 issue opened.
-
Possible error: "Backspace" is listed in the Writing System Keys instead of Functional Keys table w3c/uievents-code#34, by @Keavon.
-
w3c/push-api
-
1 issue opened.
-
Browser MUST always display a permission prompt after a user interaction w3c/push-api#356, by @collimarco.
-
-
1 issue received 2 new comments.
-
Browser MUST always display a permission prompt after a user interaction w3c/push-api#356 (2 comments by @marcoscaceres)
-
TR publications
-
10 documents published.
-
Selection API published 3 times as a Working Draft. History of Selection API
-
Web Share API published 3 times as a Working Draft. History of Web Share API
-
Pointer Lock 2.0 published twice as a Working Draft. History of Pointer Lock 2.0
-
Indexed Database API 3.0 published as a Working Draft. History of Indexed Database API 3.0
-
Intersection Observer published as a Working Draft. History of Intersection Observer
-
Participants
-
4 participants left.
-
Daniel Appelquist (Samsung Electronics Co., Ltd.) left.
-
Mounir Lamouri (Google LLC) left.
-
Raymes Khoury (Google LLC) left.
-
Shwetank Dixit (eyeo GmbH) left.
-
GitHub
w3c/manifest
-
3 issues opened.
-
related_applications needs more settings w3c/manifest#1047, by @jplevene.
-
TPAC 2022 status report w3c/manifest#1046, by @LJWatson.
-
Web Manifest Overrides w3c/manifest#1045, by @marcoscaceres.
-
-
6 issues received 15 new comments.
-
Web Manifest Overrides w3c/manifest#1045 (10 comments by @alancutter, @bathos, @loubrett, @marcoscaceres, @mgiuca, @tomayac)
-
w3c/manifest#676 (1 comment by @aphillips)
-
Add support for defining a theme color for both light & dark modes (prefers color scheme) w3c/manifest#975 (1 comment by @marcoscaceres)
-
w3c/manifest#627 (1 comment by @priyansharma)
-
-
1 pull request opened.
-
Rename .pr-preview.json to -preview.json w3c/manifest#1044, by @Maliek2.
-
-
1 pull request merged.
-
Use ordered map JSON in id processing w3c/manifest#1040.
-
-
1 pull request closed.
-
Adding file_handlers and launch consumer w3c/manifest#1005.
-
w3c/web-share
-
1 issue opened.
-
Call for Consensus: Publish as Candidate Recommendation w3c/web-share#246, by @marcoscaceres.
-
-
7 issues closed.
-
Call for Consensus: Publish as Candidate Recommendation w3c/web-share#246.
-
Add example of permission policy use with iframe w3c/web-share#233.
-
Mitigating user expectation mismatches with shared URL w3c/web-share#186.
-
Request to move privacy-related requirements to normative text w3c/web-share#187.
-
Limiting to http/https is limiting w3c/web-share#178.
-
Move UI note to Sec/Priv section w3c/web-share#64.
-
Extensibility of the API section could be removed w3c/web-share#61.
-
-
1 issue reopened.
-
Permissions policy 'self' is at risk w3c/web-share#169, by @marcoscaceres.
-
-
6 issues received 14 new comments.
-
Permissions policy 'self' is at risk w3c/web-share#169 (9 comments by @ewilligers, @marcoscaceres, @saschanaz)
-
Mitigating user expectation mismatches with shared URL w3c/web-share#186 (1 comment by @marcoscaceres)
-
Request to move privacy-related requirements to normative text w3c/web-share#187 (1 comment by @marcoscaceres)
-
-
2 pull requests opened.
-
Editiorial: Move Priv/Sec into normative parts of spec w3c/web-share#245, by @marcoscaceres.
-
Define sharable scheme + check w3c/web-share#244, by @marcoscaceres.
-
-
5 pull requests merged.
-
Editorial: mark permissions policy at risk w3c/web-share#234.
-
Editiorial: Move Priv/Sec into normative parts of spec w3c/web-share#245.
-
Define sharable scheme + check w3c/web-share#244.
-
Editorial: move UI suggestion to Priv/Sec section w3c/web-share#240.
-
Editorial: remove Extensibility text w3c/web-share#239.
-
-
3 pull requests received 11 new comments.
-
Editorial: mark permissions policy at risk w3c/web-share#234 (6 comments by @marcoscaceres, @saschanaz)
-
w3c/manifest-app-info
-
2 issues opened.
-
Describe current state of manifest-app-info in the explainer w3c/manifest-app-info#57, by @philloooo.
-
consider ranaming "platform" w3c/manifest-app-info#55, by @philloooo.
-
-
1 issue received 6 new comments.
-
consider ranaming "platform" w3c/manifest-app-info#55 (6 comments by @aarongustafson, @dominickng, @philloooo, @tomayac)
-
-
1 pull request opened.
-
Fix iPadOS label w3c/manifest-app-info#56, by @tomayac.
-
w3c/ServiceWorker
-
6 issues opened.
-
Can HTTPS traffic without origin header be intercepted by Service Worker w3c/ServiceWorker#1654, by @JoshiPriyanka92.
-
HTTPS request without origin header are not intercepted by Service Worker w3c/ServiceWorker#1653, by @JoshiPriyanka92.
-
TPAC 2022 w3c/ServiceWorker#1652, by @asutherland.
-
The Service Worker spec should specify how to compute the site for cookies. w3c/ServiceWorker#1651, by @sbingler.
-
cache.add will block the main thread, such as network bandwidth? w3c/ServiceWorker#1650, by @mamumu123.
-
Is there a security issue justifying no `Set-Cookie` setting in SW? w3c/ServiceWorker#1649, by @getify.
-
-
3 issues closed.
-
Can HTTPS traffic without origin header be intercepted by Service Worker w3c/ServiceWorker#1654.
-
HTTPS request without origin header are not intercepted by Service Worker w3c/ServiceWorker#1653.
-
cache.add will block the main thread, such as network bandwidth? w3c/ServiceWorker#1650.
-
-
8 issues received 13 new comments.
-
The Service Worker spec should specify how to compute the site for cookies. w3c/ServiceWorker#1651 (3 comments by @sbingler, @wanderview)
-
cache.add will block the main thread, such as network bandwidth? w3c/ServiceWorker#1650 (2 comments by @jakearchibald, @mamumu123)
-
Is there a security issue justifying no `Set-Cookie` setting in SW? w3c/ServiceWorker#1649 (2 comments by @getify, @mkruisselbrink)
-
Can HTTPS traffic without origin header be intercepted by Service Worker w3c/ServiceWorker#1654 (1 comment by @wanderview)
-
HTTPS request without origin header are not intercepted by Service Worker w3c/ServiceWorker#1653 (1 comment by @wanderview)
-
w3c/ServiceWorker#1188 (1 comment by @JEduardoPeralta)
-
Create Service Worker from Blob/String that does not persist and auto claims for testing w3c/ServiceWorker#1642 (1 comment by @georgir)
-
w3c/push-api
-
3 issues opened.
-
Documentation: It's not clear how to specify the push service w3c/push-api#355, by @DarkTrick.
-
TPAC 2022 status report w3c/push-api#354, by @LJWatson.
-
Question: what about shared device w3c/push-api#353, by @stefanKP50.
-
-
3 issues received 3 new comments.
-
w3c/push-api#303 (1 comment by @FluorescentHallucinogen)
-
Documentation: It's not clear how to specify the push service w3c/push-api#355 (1 comment by @DarkTrick)
-
w3c/push-api#297 (1 comment by @stefanKP50)
-
w3c/gamepad
-
3 issues opened.
-
TPAC 2022 status report w3c/gamepad#169, by @LJWatson.
-
gamepad*connected handlers are only needed on Window w3c/gamepad#166, by @dontcallmedom.
-
-
1 issue closed.
-
gamepad*connected handlers are only needed on Window w3c/gamepad#166.
-
-
3 issues received 12 new comments.
-
gamepad*connected handlers are only needed on Window w3c/gamepad#166 (9 comments by @dontcallmedom, @marcoscaceres)
-
Update subsections "Receiving inputs" and "Constructing a Gamepad" of Gamepad Interface for touch inputs. w3c/gamepad#167 (1 comment by @sagoston)
-
-
1 pull request opened.
-
Enhance Gamepad interface description for Touch w3c/gamepad#168, by @bradleyneedham.
-
-
1 pull request received 17 new comments.
-
Enhance Gamepad interface description for Touch w3c/gamepad#168 (17 comments by @bradleyneedham, @nondebug, @siusin)
-
w3c/uievents
-
1 issue opened.
-
TPAC 2022 status reports w3c/uievents#333, by @LJWatson.
-
-
1 pull request opened.
-
Use <thead> for table headers w3c/uievents#332, by @dontcallmedom.
-
-
1 pull request merged.
-
Use <thead> for table headers w3c/uievents#332.
-
w3c/screen-orientation
-
1 issue opened.
-
TPAC 2022 status report w3c/screen-orientation#208, by @LJWatson.
-
w3c/pointerlock
-
1 issue opened.
-
TPAC 2022 status report w3c/pointerlock#80, by @LJWatson.
-
-
1 pull request opened.
-
Use respec conventions for event definitions w3c/pointerlock#79, by @dontcallmedom.
-
-
1 pull request merged.
-
Use respec conventions for event definitions w3c/pointerlock#79.
-
-
1 pull request received 1 new comment.
w3c/IndexedDB
-
1 issue opened.
-
TPAC 2022 status report w3c/IndexedDB#389, by @LJWatson.
-
-
1 pull request opened.
-
Fix internal links to events w3c/IndexedDB#388, by @dontcallmedom.
-
-
1 pull request merged.
-
Fix internal links to events w3c/IndexedDB#388.
-
-
1 pull request received 1 new comment.
w3c/image-resource
-
1 issue opened.
-
TPAC 2022 status report w3c/image-resource#44, by @LJWatson.
-
w3c/FileAPI
-
1 issue opened.
-
TPAC 2022 status report w3c/FileAPI#178, by @LJWatson.
-
w3c/contact-picker
-
1 issue opened.
-
TPAC 2022 status report w3c/contact-picker#48, by @LJWatson.
-
w3c/badging
-
2 issues opened.
-
TPAC 2022 status report w3c/badging#88, by @LJWatson.
-
Android support, at least w3c/badging#87, by @garygreen.
-
w3c/webappswg
-
2 issues opened.
-
TPAC 2022 - Call for topics and session planning w3c/webappswg#87, by @marcoscaceres.
-
Add meetings to calendar w3c/webappswg#86, by @marcoscaceres.
-
w3c/web-locks
-
1 pull request opened.
-
Fix bad variable usage w3c/web-locks#110, by @inexorabletash.
-
-
1 pull request merged.
-
Fix bad variable usage w3c/web-locks#110.
-
-
1 pull request received 1 new comment.
TR publications
-
15 documents published.
-
Gamepad published 3 times as a Working Draft. History of Gamepad
-
Push API published twice as a Working Draft. History of Push API
-
Indexed Database API 3.0 published twice as a Working Draft. History of Indexed Database API 3.0
-
UI Events published twice as a Working Draft. History of UI Events
-
Intersection Observer published 4 times as a Working Draft. History of Intersection Observer
-
Web Share API published twice as a Working Draft. History of Web Share API
-
Participants
-
2 participants joined.
-
Mike Taylor (Google LLC) joined.
-
Karl Dubost (Apple Inc.) joined.
-
GitHub
w3c/push-api
-
3 issues received 4 new comments.
-
Mention or enforce userVisibleOnly check in PushManager.subscribe? w3c/push-api#339 (2 comments by @aarongustafson, @marcoscaceres)
-
userVisibleOnly should be standardized to match browser behaviour w3c/push-api#313 (1 comment by @jimmywarting)
-
Does PushManager subscribe() need transient activation check? w3c/push-api#346 (1 comment by @marcoscaceres)
-
-
3 pull requests opened.
-
Rewrite .subscribe() to fix various bugs w3c/push-api#350, by @marcoscaceres.
-
Remove redudant secure context check w3c/push-api#349, by @marcoscaceres.
-
check and consume user activation w3c/push-api#348, by @marcoscaceres.
-
-
2 pull requests merged.
-
Rewrite .subscribe() to fix various bugs w3c/push-api#350.
-
Remove redudant secure context check w3c/push-api#349.
-
-
3 pull requests received 17 new comments.
-
Rewrite .subscribe() to fix various bugs w3c/push-api#350 (14 comments by @beverloo, @marcoscaceres, @martinthomson)
-
w3c/push-api#351 (1 comment by @w3cbot)
-
w3c/IndexedDB
-
1 issue closed.
-
Support Storage Partitioning w3c/IndexedDB#382.
-
-
2 issues received 4 new comments.
-
5 pull requests opened.
-
Associate event definitions with the interfaces they fire at w3c/IndexedDB#387, by @dontcallmedom.
-
Normalize negative zero w3c/IndexedDB#386, by @inexorabletash.
-
Bikeshed: Enable 'Assume Explicit For' and make links explicit w3c/IndexedDB#385, by @inexorabletash.
-
Editorial: Add event definition for 'close' w3c/IndexedDB#384, by @inexorabletash.
-
Support Storage Partitioning w3c/IndexedDB#383, by @arichiv.
-
-
4 pull requests merged.
-
Associate event definitions with the interfaces they fire at w3c/IndexedDB#387.
-
Bikeshed: Enable 'Assume Explicit For' and make links explicit w3c/IndexedDB#385.
-
Support Storage Partitioning w3c/IndexedDB#383.
-
Editorial: Add event definition for 'close' w3c/IndexedDB#384.
-
-
3 pull requests received 32 new comments.
-
Editorial: Add event definition for 'close' w3c/IndexedDB#384 (4 comments by @brettz9, @inexorabletash)
w3c/uievents
-
1 issue opened.
-
Remove dblclick text selection default action to match browsers w3c/uievents#328, by @flackr.
-
-
1 issue closed.
-
Document the cancelability of wheel events w3c/uievents#282.
-
-
1 issue received 2 new comments.
-
3 pull requests opened.
-
Specify non-cancelable wheel events when there are no non-passive listeners w3c/uievents#330, by @zcorpan.
-
Remove text selection from the dblclick default action - #328 w3c/uievents#329, by @flackr.
-
Fixed typos w3c/uievents#327, by @chrisn.
-
-
2 pull requests merged.
-
Fixed typos w3c/uievents#327.
-
3 pull requests received 5 new comments.
-
Specify non-cancelable wheel events when there are no non-passive listeners w3c/uievents#330 (2 comments by @garykac, @zcorpan)
-
Remove text selection from the dblclick default action - #328 w3c/uievents#329 (2 comments by @flackr, @mustaqahmed)
-
w3c/manifest
-
1 issue opened.
-
Add option to disable built-in navigation gestures w3c/manifest#1041, by @liamdebeasi.
-
-
2 issues received 8 new comments.
-
Add support for defining a theme color for both light & dark modes (prefers color scheme) w3c/manifest#975 (7 comments by @aarongustafson, @immortalcodes, @marcoscaceres)
-
-
1 pull request opened.
-
Use ordered map JSON in id processing w3c/manifest#1040, by @philloooo.
-
w3c/FileAPI
-
1 issue opened.
-
blob: slice() without valid content type yields unexpected results w3c/FileAPI#177, by @dlrobertson.
-
-
1 issue closed.
-
blob: slice() without valid content type yields unexpected results w3c/FileAPI#177.
-
-
2 issues received 3 new comments.
-
blob: slice() without valid content type yields unexpected results w3c/FileAPI#177 (2 comments by @dlrobertson, @inexorabletash)
-
w3c/image-resource
-
1 issue received 9 new comments.
-
Add a `color_scheme` member w3c/image-resource#26 (9 comments by @aarongustafson, @loubrett, @marcoscaceres, @tomayac)
-
-
1 pull request opened.
-
Accessible name linked w3c/image-resource#43, by @aarongustafson.
-
-
1 pull request merged.
-
Accessible name linked w3c/image-resource#43.
-
w3c/ServiceWorker
-
2 issues opened.
-
Loading service worker behind authentication w3c/ServiceWorker#1648, by @francescoterrell.
-
Service worker catches requests from different ports w3c/ServiceWorker#1646, by @lewispham.
-
-
1 issue closed.
-
Service worker catches requests from different ports w3c/ServiceWorker#1646.
-
-
3 issues received 4 new comments.
-
Service worker catches requests from different ports w3c/ServiceWorker#1646 (1 comment by @lewispham)
-
1 pull request opened.
-
align default metadata used for both ED and CRD w3c/ServiceWorker#1647, by @ylafon.
-
w3c/gamepad
-
2 issues opened.
-
Fold extensions.html into main spec w3c/gamepad#165, by @marcoscaceres.
-
Make note of the fact that the standard gamepad layout is privacy-relevant w3c/gamepad#161, by @IreneKnapp.
-
-
1 issue closed.
-
2 issues received 3 new comments.
-
gamepadconnected/disconnected events & non-"fully active" documents w3c/gamepad#149 (1 comment by @rakina)
-
3 pull requests opened.
-
chore: tidy extensions.html w3c/gamepad#164, by @marcoscaceres.
-
extensions: Add vibrationActuator and dual-rumble effect w3c/gamepad#163, by @nondebug.
-
Suggest Standard Gamepad as a fingerprinting mitigation w3c/gamepad#162, by @nondebug.
-
-
2 pull requests merged.
-
Suggest Standard Gamepad as a fingerprinting mitigation w3c/gamepad#162.
-
chore: tidy extensions.html w3c/gamepad#164.
-
-
1 pull request closed.
-
spec vibrationActuator gamepad extension w3c/gamepad#68.
-
-
2 pull requests received 32 new comments.
-
extensions: Add vibrationActuator and dual-rumble effect w3c/gamepad#163 (29 comments by @marcoscaceres, @nondebug)
-
Suggest Standard Gamepad as a fingerprinting mitigation w3c/gamepad#162 (3 comments by @marcoscaceres, @nondebug)
-
w3c/web-share
-
14 issues closed.
-
Define what "hostile share" is w3c/web-share#217.
-
A security review; some nits w3c/web-share#223.
-
Plan to transition to CR w3c/web-share#207.
-
Better describe intention of `navigator.canShare()` and usage w3c/web-share#211.
-
Redundant notes w3c/web-share#65.
-
Discussion: `navigator.share.qrCode` w3c/web-share#204.
-
Use of File in ShareData w3c/web-share#181.
-
Proposal for a declarative web share button type w3c/web-share#176.
-
Fail when unknown field exists on share() and canShare()? w3c/web-share#214.
-
Additional ShareData types? w3c/web-share#182.
-
Add text language / direction attributes w3c/web-share#6.
-
Should sharing zero size files be allowed? w3c/web-share#229.
-
Split security & privacy considerations w3c/web-share#224.
-
-
11 issues received 21 new comments.
-
A security review; some nits w3c/web-share#223 (5 comments by @ericwilligers, @marcoscaceres, @richsalz)
-
Fail when unknown field exists on share() and canShare()? w3c/web-share#214 (4 comments by @marcoscaceres, @saschanaz)
-
Should sharing zero size files be allowed? w3c/web-share#229 (2 comments by @marcoscaceres, @saschanaz)
-
Better describe intention of `navigator.canShare()` and usage w3c/web-share#211 (1 comment by @marcoscaceres)
-
w3c/web-share#6 (1 comment by @marcoscaceres)
-
-
6 pull requests opened.
-
Editorial: address security review feedback w3c/web-share#243, by @marcoscaceres.
-
Editorial: clarify potentially hostile share w3c/web-share#242, by @marcoscaceres.
-
Editorial: cleanup notes w3c/web-share#241, by @marcoscaceres.
-
Editorial: move UI suggestion to Priv/Sec section w3c/web-share#240, by @marcoscaceres.
-
Editorial: remove Extensibility text w3c/web-share#239, by @marcoscaceres.
-
Editorial: add more examples w3c/web-share#238, by @marcoscaceres.
-
-
4 pull requests merged.
-
Editorial: clarify potentially hostile share w3c/web-share#242.
-
Editorial: address security review feedback w3c/web-share#243.
-
Editorial: cleanup notes w3c/web-share#241.
-
Editorial: add more examples w3c/web-share#238.
-
-
3 pull requests closed.
-
Add <aside class="issue"> for canShare problem w3c/web-share#227.
-
Extract 'Extensibility of the API' w3c/web-share#72.
-
Filter out zero length files w3c/web-share#237.
-
-
4 pull requests received 19 new comments.
-
Editorial: mark permissions policy at risk w3c/web-share#234 (10 comments by @marcoscaceres, @mgiuca, @saschanaz)
-
Editorial: move UI suggestion to Priv/Sec section w3c/web-share#240 (4 comments by @ewilligers, @marcoscaceres)
-
Editorial: clarify potentially hostile share w3c/web-share#242 (4 comments by @ewilligers, @marcoscaceres)
-
TR publications
-
3 documents published.
-
Web Share API published twice as a Working Draft. History of Web Share API
-
Gamepad published as a Working Draft. History of Gamepad
-
Participants
-
2 chairs appointed.
-
Marcos Caceres became a chair.
-
Léonie Watson became a chair.
-
-
3 participants joined.
-
Dominic Farolino (Google LLC) joined.
-
Cornelius Witt (eyeo GmbH) joined.
-
Marcos Caceres (Apple Inc.) joined.
-
-
7 participants left.
-
yi lin (Baidu, Inc.) left.
-
Jun Yang (Baidu, Inc.) left.
-
Yanling Feng (Shenzhen University of Information Technology（深圳信息职业技术大学）) left.
-
Arturo Silva (The Washington Post) left.
-
Michael[tm] Smith (sideshowbarker) (W3C) left.
-
Johannes Wilm (W3C Invited Experts) left.
-
Kris Borchers (OpenJS Foundation) left.
-
-
11 organizations joined.
-
Sony Group Corporation joined.
-
Bocoup joined.
-
Intel Corporation joined.
-
Wikimedia Foundation joined.
-
Rakuten Group, Inc. joined.
-
eyeo GmbH joined.
-
The New York Times joined.
-
Google LLC joined.
-
Apple Inc. joined.
-
Samsung Electronics Co., Ltd. joined.
-
ByteDance joined.
-
GitHub
w3c/IndexedDB
-
1 issue opened.
-
Support Storage Partitioning w3c/IndexedDB#382, by @arichiv.
-
-
2 issues received 13 new comments.
w3c/push-api
-
1 issue received 1 new comment.
-
Does PushManager subscribe() need transient activation check? w3c/push-api#346 (1 comment by @marcoscaceres)
-
w3c/manifest
-
1 issue opened.
-
What's the default value of the `id` member if no `start_url` is provided? w3c/manifest#1038, by @benfrancis.
-
-
4 issues closed.
-
How could I participate and create an alwaysOnTop flag? w3c/manifest#938.
-
i18n support w3c/manifest#848.
-
multiple natural language text fields share language/direction [I18N] w3c/manifest#968.
-
What's the default value of the `id` member if no `start_url` is provided? w3c/manifest#1038.
-
-
8 issues received 13 new comments.
-
Feature request: access to menu bar and context menus w3c/manifest#1025 (3 comments by @aarongustafson, @Shomnipotence, @tomayac)
-
What's the default value of the `id` member if no `start_url` is provided? w3c/manifest#1038 (2 comments by @alancutter, @benfrancis)
-
Add a manifest option for the declaration of the web application running pattern w3c/manifest#1019 (2 comments by @alancutter, @songql)
-
Add a manifest option for the declaration the "version" of the web application w3c/manifest#1036 (2 comments by @dmurph, @songql)
-
How could I participate and create an alwaysOnTop flag? w3c/manifest#938 (1 comment by @marcoscaceres)
-
multiple natural language text fields share language/direction [I18N] w3c/manifest#968 (1 comment by @aarongustafson)
-
w3c/manifest#737 (1 comment by @tomayac)
-
-
1 pull request opened.
-
editorial: Move the definition of display-mode back to APPMANIFEST. w3c/manifest#1039, by @mgiuca.
-
-
1 pull request closed.
-
editorial: Making URL processing DRY w3c/manifest#1018.
-
-
4 pull requests received 24 new comments.
-
editorial: Move the definition of display-mode back to APPMANIFEST. w3c/manifest#1039 (12 comments by @aarongustafson, @aesinnllc, @marcoscaceres, @mgiuca)
-
Add scope conflict section about same-origin and nested scopes w3c/manifest#1034 (10 comments by @aarongustafson, @marcoscaceres)
-
w3c/web-share
-
2 issues opened.
-
Promises cannot be manipulated while "in parallel" w3c/web-share#235, by @annevk.
-
Add example of permission policy use with iframe w3c/web-share#233, by @marcoscaceres.
-
-
3 issues closed.
-
Promises cannot be manipulated while "in parallel" w3c/web-share#235.
-
File size limitations - MP4 w3c/web-share#225.
-
-
7 issues received 39 new comments.
-
Permissions policy 'self' is at risk w3c/web-share#169 (17 comments by @annevk, @marcoscaceres, @saschanaz)
-
Fail when unknown field exists on share() and canShare()? w3c/web-share#214 (9 comments by @marcoscaceres, @saschanaz)
-
Should sharing zero size files be allowed? w3c/web-share#229 (8 comments by @annevk, @marcoscaceres, @saschanaz)
-
What's the reason to remove web intents from web share besides security concerns w3c/web-share#232 (2 comments by @ewilligers, @marcoscaceres)
-
-
3 pull requests opened.
-
Filter out zero length files w3c/web-share#237, by @marcoscaceres.
-
Editorial: use global task to resolve promises w3c/web-share#236, by @marcoscaceres.
-
Editorial: mark permissions policy at risk w3c/web-share#234, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: use global task to resolve promises w3c/web-share#236.
-
-
1 pull request received 4 new comments.
-
Editorial: use global task to resolve promises w3c/web-share#236 (4 comments by @annevk, @marcoscaceres)
-
w3c/ServiceWorker
-
4 issues opened.
-
compile.sh was removed w3c/ServiceWorker#1645, by @wanderview.
-
Clarify CacheStorage behavior in data: URL workers w3c/ServiceWorker#1644, by @recvfrom.
-
The unnecessary limitations of the Cache.put API leads to users inventing work-arounds w3c/ServiceWorker#1643, by @expenses.
-
Create Service Worker from Blob/String that does not persist and auto claims for testing w3c/ServiceWorker#1642, by @frank-dspeed.
-
-
4 issues received 6 new comments.
-
How should import() work in service workers? w3c/ServiceWorker#1585 (2 comments by @jakearchibald, @larry-xu)
-
Create Service Worker from Blob/String that does not persist and auto claims for testing w3c/ServiceWorker#1642 (2 comments by @asutherland, @frank-dspeed)
-
w3c/ServiceWorker#799 (1 comment by @ptoner)
-
w3c/badging
-
2 issues closed.
-
Not working on PWA w3c/badging#76.
-
TPAC planning and specification status report w3c/badging#78.
-
-
1 issue received 1 new comment.
w3c/gamepad
-
1 issue reopened.
-
Make gamepads accessible by web worker w3c/gamepad#37, by @reillyeon.
-
-
1 issue received 6 new comments.
-
1 pull request merged.
-
Editorial: use associated Document in place of responsible document w3c/gamepad#160.
-
-
1 pull request received 6 new comments.
-
Add gamepad input events w3c/gamepad#152 (6 comments by @ewmb7701, @jharris1993, @marcoscaceres, @reillyeon)
-
w3c/FileAPI
-
3 issues received 20 new comments.
w3c/manifest-app-info
-
1 pull request opened.
-
Added some categories for real state w3c/manifest-app-info#52, by @jj-theInvincible.
-
-
1 pull request received 3 new comments.
-
Added some categories for real state w3c/manifest-app-info#52 (3 comments by @aarongustafson, @jj-theInvincible)
-
w3c/web-locks
-
1 issue received 2 new comments.
w3c/screen-orientation
-
1 issue reopened.
-
Should the -secondary orientations be exposed? w3c/screen-orientation#188, by @marcoscaceres.
-
w3c/uievents
-
1 issue opened.
Lifecycle
Participants
-
2 chairs stepped down.
-
Léonie Watson stepped down as a chair.
-
Marcos Caceres stepped down as a chair.
-
-
4 participants joined.
-
Ian Pouncey (TetraLogical Services Ltd) joined.
-
Patrick Lauke (TetraLogical Services Ltd) joined.
-
Léonie Watson (TetraLogical Services Ltd) joined.
-
Wei Li (Dingdao) joined.
-
-
4 participants left.
-
Ian Pouncey (TetraLogical Services Ltd) left.
-
Patrick Lauke (TetraLogical Services Ltd) left.
-
Léonie Watson (TetraLogical Services Ltd) left.
-
Marcos Caceres (Apple Inc.) left.
-
-
6 organizations joined.
-
TPGi joined.
-
TetraLogical Services Ltd joined.
-
Mozilla Foundation joined.
-
Dingdao joined.
-
Microsoft Corporation joined.
-
Thinktecture joined.
-
-
26 organizations left.
-
Dingdao left.
-
Bocoup left.
-
Rakuten Group, Inc. left.
-
ByteDance left.
-
Lenovo left.
-
Sony Group Corporation left.
-
Zhongcheng Blockchain Research Institute (Nanjing) Co. LTD left.
-
Apple Inc. left.
-
Baidu, Inc. left.
-
TPGi left.
-
Intel Corporation left.
-
Coil Technologies, Inc. left.
-
eyeo GmbH left.
-
OpenJS Foundation left.
-
Igalia left.
-
The New York Times left.
-
Wikimedia Foundation left.
-
Shenzhen University of Information Technology（深圳信息职业技术大学） left.
-
The Washington Post left.
-
Samsung Electronics Co., Ltd. left.
-
Microsoft Corporation left.
-
Thinktecture left.
-
Mozilla Foundation left.
-
Google LLC left.
-
IBM Corporation left.
-
TetraLogical Services Ltd left.
-
GitHub
w3c/ServiceWorker
-
1 issue opened.
-
[question]: how do CacheStorage save encoded responses? w3c/ServiceWorker#1641, by @jimmywarting.
-
-
1 issue closed.
-
[question]: how do CacheStorage save encoded responses? w3c/ServiceWorker#1641.
-
-
6 issues received 15 new comments.
-
[question]: how do CacheStorage save encoded responses? w3c/ServiceWorker#1641 (8 comments by @asutherland, @jimmywarting, @wanderview)
-
Service Workers with Self Signed Certificates over SSL w3c/ServiceWorker#1514 (2 comments by @amakhrov)
-
How should import() work in service workers? w3c/ServiceWorker#1585 (2 comments by @Danscap, @jimmywarting)
-
w3c/ServiceWorker#846 (1 comment by @Stvad)
-
[Feature request] Expose parent client ID for iframe navigations w3c/ServiceWorker#1556 (1 comment by @futurist)
-
-
1 pull request opened.
-
Fixing some spec linking issues w3c/ServiceWorker#1640, by @ylafon.
-
-
1 pull request merged.
-
Partition clients API by storage key. (#1606) w3c/ServiceWorker#1632.
-
-
1 pull request closed.
-
add w3cid for editors to help publication w3c/ServiceWorker#1218.
-
-
1 pull request received 1 new comment.
w3c/manifest
-
1 issue opened.
-
Add a manifest option for the declaration the "version" of the web application w3c/manifest#1036, by @songql.
-
-
1 issue closed.
-
Shortcut_items uses manifest_url when it should use start_url w3c/manifest#1003.
-
-
5 issues received 16 new comments.
-
Add a manifest option for the declaration the "version" of the web application w3c/manifest#1036 (7 comments by @aarongustafson, @alancutter, @espinr, @songql, @tomayac)
-
Add support for defining a theme color for both light & dark modes (prefers color scheme) w3c/manifest#975 (4 comments by @aarongustafson, @FluorescentHallucinogen, @MrAntix, @tomayac)
-
i18n: Multiple manifest links with different hreflang? w3c/manifest#892 (1 comment by @FluorescentHallucinogen)
-
Add a manifest option for the declaration of the web application running pattern w3c/manifest#1019 (1 comment by @alancutter)
-
-
1 pull request merged.
-
Clarify shortcut_items should be within scope of scope w3c/manifest#1033.
-
w3c/web-locks
-
1 issue received 1 new comment.
w3c/gamepad
-
3 issues received 4 new comments.
-
gamepadconnected/disconnected events & non-"fully active" documents w3c/gamepad#149 (1 comment by @rakina)
-
1 pull request received 1 new comment.
w3c/uievents
-
1 issue received 2 new comments.
w3c/manifest-app-info
-
1 issue opened.
-
categories w3c/manifest-app-info#51, by @Rockon21.
-
-
1 issue closed.
-
categories w3c/manifest-app-info#51.
-
-
2 issues received 2 new comments.
w3c/pointerlock
-
1 issue received 1 new comment.
-
feature request : Allow to set pointer position upon release w3c/pointerlock#61 (1 comment by @sirisian)
-
w3c/web-share
-
2 issues opened.
-
What's the reason to remove web intents from web share besides security concerns w3c/web-share#232, by @chenmently.
-
Discord on iOS doesn't return 'success' event w3c/web-share#231, by @vital-arekhau.
-
-
1 issue closed.
-
Discord on iOS doesn't return 'success' event w3c/web-share#231.
-
-
1 issue received 2 new comments.
-
Discord on iOS doesn't return 'success' event w3c/web-share#231 (2 comments by @ewilligers, @saschanaz)
-
TR publications
-
2 documents published.
-
Push API published as a Working Draft. History of Push API
-
Web Share API published as a Working Draft. History of Web Share API
-
Participants
-
4 participants left.
-
Jeff Hodges (Google LLC) left.
-
Carolyn MacLeod (IBM Corporation) left.
-
Tomasz Jakut (W3C Invited Experts) left.
-
Ben Francis (W3C Invited Experts) left.
-
GitHub
w3c/ServiceWorker
-
7 issues opened.
-
Edge case in https://w3c.github.io/ServiceWorker/#clients-openwindow w3c/ServiceWorker#1639, by @youennf.
-
A strange behavior about iframe nested service worker clients w3c/ServiceWorker#1637, by @fytriht.
-
Documentation: meaning of "The coast is only clear when all the resources are ready" w3c/ServiceWorker#1635, by @fytriht.
-
can we host `serviceWorker.js` at different domain and register? w3c/ServiceWorker#1634, by @shivasai09.
-
Replace usage of "responsible document" w3c/ServiceWorker#1633, by @miketaylr.
-
register service worker on another domain w3c/ServiceWorker#1631, by @jimmywarting.
-
-
3 issues closed.
-
A strange behavior about iframe nested service worker clients w3c/ServiceWorker#1637.
-
Documentation: meaning of "The coast is only clear when all the resources are ready" w3c/ServiceWorker#1635.
-
can we host `serviceWorker.js` at different domain and register? w3c/ServiceWorker#1634.
-
-
7 issues received 10 new comments.
-
A strange behavior about iframe nested service worker clients w3c/ServiceWorker#1637 (2 comments by @fytriht, @wanderview)
-
Documentation: meaning of "The coast is only clear when all the resources are ready" w3c/ServiceWorker#1635 (2 comments by @fytriht, @tomayac)
-
register service worker on another domain w3c/ServiceWorker#1631 (2 comments by @jakearchibald, @jimmywarting)
-
w3c/ServiceWorker#879 (1 comment by @aerik)
-
can we host `serviceWorker.js` at different domain and register? w3c/ServiceWorker#1634 (1 comment by @wanderview)
-
w3c/ServiceWorker#1356 (1 comment by @jimmywarting)
-
w3c/ServiceWorker#940 (1 comment by @fabiel-leon)
-
-
4 pull requests opened.
-
Clarify code comment w3c/ServiceWorker#1636, by @tomayac.
-
Partition clients API by storage key. (#1606) w3c/ServiceWorker#1632, by @wanderview.
-
Partition cache API by storage key. (#1606) w3c/ServiceWorker#1630, by @wanderview.
-
Partition service workers using Storage Key. (#1606) w3c/ServiceWorker#1629, by @wanderview.
-
-
3 pull requests merged.
-
Clarify code comment w3c/ServiceWorker#1636.
-
Partition cache API by storage key. (#1606) w3c/ServiceWorker#1630.
-
Partition service workers using Storage Key. (#1606) w3c/ServiceWorker#1629.
-
-
1 pull request received 2 new comments.
-
Partition service workers using Storage Key. (#1606) w3c/ServiceWorker#1629 (2 comments by @wanderview)
-
w3c/manifest
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Add scope conflict section about same-origin and nested scopes w3c/manifest#1034, by @dmurph.
-
Clarify shortcut_items should be within scope of scope w3c/manifest#1033, by @philloooo.
-
-
4 pull requests received 35 new comments.
-
Adding file_handlers and launch consumer w3c/manifest#1005 (32 comments by @dmurph, @evanstade, @marcoscaceres)
-
w3c/IndexedDB
-
1 issue received 2 new comments.
w3c/webappswg
-
1 issue opened.
-
Editor for Intersection Observer w3c/webappswg#83, by @LJWatson.
-
-
3 issues closed.
-
Update WG homepage w3c/webappswg#74.
-
Clipboard API not very well maintained w3c/webappswg#50.
-
TPAC 2022 - virtual or physical? w3c/webappswg#82.
-
-
2 issues received 8 new comments.
w3c/push-api
-
2 issues opened.
-
Does PushManager subscribe() need transient activation check? w3c/push-api#346, by @youennf.
-
Should push be a policy-controlled feature? w3c/push-api#345, by @marcoscaceres.
-
-
1 pull request opened.
-
Editorial: define and export 'push' permission w3c/push-api#344, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: define and export 'push' permission w3c/push-api#344.
-
-
1 pull request received 2 new comments.
w3c/uievents
-
1 issue opened.
-
Keyboard Event Types: possible text missing. w3c/uievents#324, by @MelSumner.
-
-
1 pull request received 2 new comments.
w3c/web-share
-
1 pull request opened.
-
Editorial: use associated Document in place of responsible document w3c/web-share#230, by @miketaylr.
-
-
1 pull request merged.
-
Editorial: use associated Document in place of responsible document w3c/web-share#230.
-
w3c/manifest-app-info
-
2 issues closed.
-
Request for additional categories w3c/manifest-app-info#37.
-
Remove windows10x value w3c/manifest-app-info#48.
-
-
1 pull request opened.
-
Chore: Exporting definitions & updating the action w3c/manifest-app-info#50, by @aarongustafson.
-
-
3 pull requests merged.
-
Adding new categories w3c/manifest-app-info#41.
-
Chore: Exporting definitions & updating the action w3c/manifest-app-info#50.
-
Remove `windows10x` platform w3c/manifest-app-info#49.
-
-
2 pull requests received 8 new comments.
-
Chore: Exporting definitions & updating the action w3c/manifest-app-info#50 (7 comments by @aarongustafson, @marcoscaceres)
-
w3c/screen-orientation
-
1 issue opened.
-
Replace usage of "responsible document" w3c/screen-orientation#207, by @miketaylr.
-
w3c/gamepad
-
1 pull request opened.
-
Editorial: use associated Document in place of responsible document w3c/gamepad#160, by @miketaylr.
-
w3c/web-locks
-
1 pull request opened.
-
Editorial: use associated Document in place of responsible document w3c/web-locks#109, by @miketaylr.
-
-
1 pull request merged.
-
Editorial: use associated Document in place of responsible document w3c/web-locks#109.
-
-
1 pull request received 5 new comments.
-
Editorial: use associated Document in place of responsible document w3c/web-locks#109 (5 comments by @miketaylr, @saschanaz)
-
w3c/badging
-
1 pull request opened.
-
Editorial: use associated Document in place of responsible document w3c/badging#86, by @miketaylr.
-
TR publications
-
4 documents published.
-
Web Application Manifest published 3 times as a Working Draft. History of Web Application Manifest
-
Gamepad published as a Working Draft. History of Gamepad
-
GitHub
w3c/ServiceWorker
-
3 issues opened.
-
Unnecessary Origin Restriction w3c/ServiceWorker#1628, by @cinolt.
-
when I deploy my app new version, latest version/changes not updated at the first time reload w3c/ServiceWorker#1627, by @vinodpotru.
-
Service Worker as secure storage and provider for access token and refresh token w3c/ServiceWorker#1626, by @DenyVeyten.
-
-
2 issues closed.
-
Unnecessary Origin Restriction w3c/ServiceWorker#1628.
-
when I deploy my app new version, latest version/changes not updated at the first time reload w3c/ServiceWorker#1627.
-
-
9 issues received 17 new comments.
-
Unnecessary Origin Restriction w3c/ServiceWorker#1628 (3 comments by @cinolt, @jakearchibald, @wanderview)
-
when I deploy my app new version, latest version/changes not updated at the first time reload w3c/ServiceWorker#1627 (1 comment by @jakearchibald)
-
How does ServiceWorker interact with non-"fully active" documents? w3c/ServiceWorker#1594 (1 comment by @rakina)
-
w3c/ServiceWorker#756 (1 comment by @wanderview)
w3c/webappswg
-
1 issue opened.
-
TPAC 2022 - virtual or physical? w3c/webappswg#82, by @marcoscaceres.
-
-
1 issue received 1 new comment.
w3c/web-locks
-
2 issues opened.
-
Queue a global event loop task from parallel queue algorithms when running script w3c/web-locks#108, by @shaseley.
-
Held lock on worker and garbage collection w3c/web-locks#107, by @saschanaz.
-
-
2 issues received 3 new comments.
-
Held lock on worker and garbage collection w3c/web-locks#107 (2 comments by @inexorabletash, @saschanaz)
-
Queue a global event loop task from parallel queue algorithms when running script w3c/web-locks#108 (1 comment by @saschanaz)
-
w3c/manifest
-
3 issues closed.
-
Specify how updates work w3c/manifest#446.
-
Status report and planning for TPAC 2021 w3c/manifest#999.
-
Link to manifest-app-info in the README w3c/manifest#1027.
-
-
3 issues received 5 new comments.
-
Why is purpose a "unordered set of unique space-separated tokens"? w3c/manifest#903 (3 comments by @aarongustafson, @toastal)
-
w3c/manifest#470 (1 comment by @davido242)
-
-
1 pull request opened.
-
Link to manifest-app-info in the README w3c/manifest#1030, by @xfq.
-
-
2 pull requests merged.
-
Describe manifest update behavior w3c/manifest#1011.
-
Link to manifest-app-info in the README w3c/manifest#1030.
-
-
3 pull requests received 21 new comments.
-
Describe manifest update behavior w3c/manifest#1011 (8 comments by @aarongustafson, @marcoscaceres, @philloooo)
-
w3c/manifest#1032 (1 comment by @w3cbot)
w3c/gamepad
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Use * as default allowlist w3c/gamepad#159, by @marcoscaceres.
-
-
1 pull request merged.
-
getGamepad() check if doc is fully active w3c/gamepad#157.
-
-
1 pull request closed.
-
Use * as default allowlist w3c/gamepad#159.
-
-
3 pull requests received 4 new comments.
-
Require secure context for gamepad state and events w3c/gamepad#120 (2 comments by @andrewfstratton, @marcoscaceres)
-
w3c/IndexedDB
-
1 issue opened.
-
Batch get/getAll w3c/IndexedDB#376, by @cyanfish.
-
-
1 issue received 1 new comment.
-
w3c/IndexedDB#35 (1 comment by @fdinburgh)
-
w3c/badging
-
1 issue opened.
-
badging without installing pwa w3c/badging#85, by @jimmywarting.
-
-
1 issue received 1 new comment.
w3c/pointerlock
-
1 pull request received 3 new comments.
-
Add lock options to requestPointerLock w3c/pointerlock#49 (3 comments by @hamishwillee, @marcoscaceres, @reillyeon)
-
w3c/FileAPI
-
2 issues received 2 new comments.
-
w3c/FileAPI#26 (1 comment by @jimmywarting)
-
Participants
-
1 participant left.
-
Jan Miksovsky (W3C Invited Experts) left.
-
GitHub
w3c/web-share
-
1 issue received 8 new comments.
w3c/screen-orientation
-
1 issue opened.
-
Add can-lock-orientation media feature to detect if locking is possible w3c/screen-orientation#206, by @makotokato.
-
-
1 issue received 2 new comments.
-
Add can-lock-orientation media feature to detect if locking is possible w3c/screen-orientation#206 (2 comments by @makotokato, @tomayac)
-
w3c/ServiceWorker
-
3 issues opened.
-
Question: Does ServiceWorker reflects to Web Performance when store cache? w3c/ServiceWorker#1625, by @sudokzt.
-
[FEATURE REQUEST] Persistent ServiceWorker to run setInterval() w3c/ServiceWorker#1624, by @wmbenedetto.
-
[Question] How to get replacesClientId? w3c/ServiceWorker#1623, by @arpitjindal.
-
-
4 issues closed.
-
Question: Does ServiceWorker reflects to Web Performance when store cache? w3c/ServiceWorker#1625.
-
[FEATURE REQUEST] Persistent ServiceWorker to run setInterval() w3c/ServiceWorker#1624.
-
Service Worker Subresource Filter w3c/ServiceWorker#1584.
-
-
9 issues received 11 new comments.
-
[Question] How to get replacesClientId? w3c/ServiceWorker#1623 (2 comments by @arpitjindal, @wanderview)
-
Is it possible to manipulate the initial page request (which seems to be automatically) handled by the service worker? w3c/ServiceWorker#1622 (2 comments by @hawkerboy7, @wanderview)
-
consider adding a note that response body may be re-buffered in browser w3c/ServiceWorker#1573 (1 comment by @banou26)
-
Question: Does ServiceWorker reflects to Web Performance when store cache? w3c/ServiceWorker#1625 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#1372 (1 comment by @mangelozzi)
-
[FEATURE REQUEST] Persistent ServiceWorker to run setInterval() w3c/ServiceWorker#1624 (1 comment by @jakearchibald)
-
consider allowing a non-scope identifier for registrations w3c/ServiceWorker#1512 (1 comment by @wanderview)
-
w3c/ServiceWorker#808 (1 comment by @transformsen)
-
-
2 pull requests merged.
-
Define the time origin for service workers w3c/ServiceWorker#1621.
-
Pass controller from fetch, and abort SW fetch when it's canceled w3c/ServiceWorker#1620.
-
-
2 pull requests received 12 new comments.
-
Define the time origin for service workers w3c/ServiceWorker#1621 (7 comments by @jakearchibald, @noamr, @ylafon)
-
Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) w3c/ServiceWorker#1526 (5 comments by @wanderview)
-
w3c/manifest
-
1 issue closed.
-
Privacy Review: handle start_url tracking w3c/manifest#399.
-
-
2 issues received 4 new comments.
-
w3c/manifest#436 (1 comment by @leopsidom)
-
1 pull request opened.
-
Address privacy issue with start_url w3c/manifest#1029, by @marcoscaceres.
-
-
1 pull request merged.
-
Address privacy issue with start_url w3c/manifest#1029.
-
-
3 pull requests received 16 new comments.
-
Adding file_handlers and launch consumer w3c/manifest#1005 (11 comments by @evanstade, @marcoscaceres)
-
Address privacy issue with start_url w3c/manifest#1029 (4 comments by @aarongustafson, @lknik, @marcoscaceres)
-
w3c/IndexedDB
-
6 issues opened.
-
Clarify the handling of +0 and -0 in keys w3c/IndexedDB#375, by @abacabadabacaba.
-
Thanks for explaining! I missed that first part. w3c/IndexedDB#373, by @Mguiteria.
-
In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? w3c/IndexedDB#372, by @Mguiteria.
-
In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? w3c/IndexedDB#371, by @Mguiteria.
-
Sites i been to w3c/IndexedDB#370, by @Mguiteria.
-
-
5 issues closed.
-
Sites i been to w3c/IndexedDB#370.
-
Thanks for explaining! I missed that first part. w3c/IndexedDB#373.
-
-
6 issues received 9 new comments.
-
Clarify the handling of +0 and -0 in keys w3c/IndexedDB#375 (3 comments by @abacabadabacaba, @asutherland, @inexorabletash)
-
In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? w3c/IndexedDB#371 (1 comment by @inexorabletash)
-
In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? w3c/IndexedDB#372 (1 comment by @inexorabletash)
-
Need to specify what happens if you call `continuePrimaryKey()` on a cursor where the source is an object store. Throw? w3c/IndexedDB#374 (1 comment by @inexorabletash)
-
w3c/push-api
-
1 issue received 1 new comment.
w3c/gamepad
-
2 issues received 6 new comments.
-
2 pull requests received 6 new comments.