Web Applications Working Group - Activity in 2020
No matches.
Lifecycle
-
1 charter started.
-
Chartered until 31 May 2021. Participants had to rejoin under this charter.
-
TR publications
-
2 documents published.
-
Selection API published as a Working Draft. History of Selection API
-
ARIA in HTML published as a Working Draft. History of ARIA in HTML
-
Participants
-
5 participants joined.
-
Yanling Feng (Shenzhen University of Information Technology（深圳信息职业技术大学）) joined.
-
Daniel Clark (Microsoft Corporation) joined.
-
Yoshifumi Inoue (Google LLC) joined.
-
Ian Pouncey (TetraLogical Services Ltd) joined.
-
Kenneth Russell (Google LLC) joined.
-
-
1 participant left.
-
John Foliot (Deque Systems, Inc.) left.
-
-
11 organizations joined.
-
The New York Times joined.
-
Wikimedia Foundation joined.
-
Shenzhen University of Information Technology（深圳信息职业技术大学） joined.
-
The Washington Post joined.
-
Samsung Electronics Co., Ltd. joined.
-
Microsoft Corporation joined.
-
Thinktecture joined.
-
Mozilla Foundation joined.
-
Google LLC joined.
-
IBM Corporation joined.
-
TetraLogical Services Ltd joined.
-
-
23 organizations left.
-
The Washington Post left.
-
The New York Times left.
-
Huawei left.
-
Kodansha, Publishers, Ltd. left.
-
Wikimedia Foundation left.
-
IBM Corporation left.
-
Coil Technologies, Inc. left.
-
Airbnb Inc left.
-
Sony Group Corporation left.
-
Samsung Electronics Co., Ltd. left.
-
Apple Inc. left.
-
BBVA left.
-
Igalia left.
-
Microsoft Corporation left.
-
eyeo GmbH left.
-
Google LLC left.
-
OpenJS Foundation left.
-
Deque Systems, Inc. left.
-
Thinktecture left.
-
TPGi left.
-
Intel Corporation left.
-
TetraLogical Services Ltd left.
-
Mozilla Foundation left.
-
GitHub
w3c/badging
-
1 issue opened.
-
Does this extend to badges in extensions? w3c/badging#81, by @shishirarora3.
-
w3c/manifest
-
1 issue received 9 new comments.
w3c/gamepad
-
1 pull request opened.
-
Add global event handler attributes w3c/gamepad#144, by @saschanaz.
-
w3c/ServiceWorker
-
3 issues opened.
-
[Feature request] Allow keeping service worker alive w3c/ServiceWorker#1558, by @AshleyScirra.
-
[Feature request] Clients should know their own IDs w3c/ServiceWorker#1557, by @AshleyScirra.
-
[Feature request] Expose parent client ID for iframe navigations w3c/ServiceWorker#1556, by @AshleyScirra.
-
-
6 issues received 19 new comments.
-
[Feature request] Allow keeping service worker alive w3c/ServiceWorker#1558 (7 comments by @AshleyScirra, @asutherland, @mkruisselbrink, @wanderview)
-
[Feature request] Expose parent client ID for iframe navigations w3c/ServiceWorker#1556 (5 comments by @AshleyScirra, @asutherland)
-
w3c/ServiceWorker#1372 (2 comments by @asutherland)
-
[Feature request] Clients should know their own IDs w3c/ServiceWorker#1557 (1 comment by @wanderview)
-
-
1 pull request opened.
-
Use undefined union for getRegistration()/match()/get() w3c/ServiceWorker#1559, by @saschanaz.
-
w3c/manifest-app-info
-
1 issue opened.
-
Add F-Droid platform w3c/manifest-app-info#24, by @toby3d.
-
w3c/uievents
-
3 issues opened.
-
Expose IDLs for deprecated methods w3c/uievents#286, by @saschanaz.
-
Browsers do not fire select event with UIEvent w3c/uievents#284, by @saschanaz.
-
-
2 issues closed.
-
1 issue received 5 new comments.
-
Shall we create a dblclick event when the cursor have moved to a different location between two clicks? w3c/uievents#283 (5 comments by @garykac, @sefeng211)
-
-
1 pull request opened.
-
Expose legacy IDL blocks w3c/uievents#287, by @saschanaz.
-
-
1 pull request received 1 new comment.
w3c/web-locks
-
1 issue opened.
-
Allow making locks re-entrant w3c/web-locks#67, by @jasnell.
-
-
1 issue received 1 new comment.
w3c/IndexedDB
-
1 issue opened.
-
Latest Published link is bogus w3c/IndexedDB#347, by @inexorabletash.
-
-
1 issue closed.
-
Latest Published link is bogus w3c/IndexedDB#347.
-
-
1 issue received 2 new comments.
TR publications
-
3 documents published.
-
Intersection Observer published twice as a Working Draft. History of Intersection Observer
-
ARIA in HTML published as a Working Draft. History of ARIA in HTML
-
GitHub
w3c/push-api
-
2 issues received 3 new comments.
-
userVisibleOnly should be standardized to match browser behaviour w3c/push-api#313 (2 comments by @collimarco)
-
w3c/ServiceWorker
-
5 issues opened.
-
get importScripts to work offline w3c/ServiceWorker#1555, by @tomasgil123.
-
clients.claim() with a blob URL worker w3c/ServiceWorker#1554, by @d0iasm.
-
Virtual call on November 20, 2020 w3c/ServiceWorker#1553, by @mfalken.
-
Implementations are missing navigator.serviceWorker in workers w3c/ServiceWorker#1552, by @josephliccini.
-
Service worker & Blocked cookies w3c/ServiceWorker#1551, by @jimmywarting.
-
-
3 issues closed.
-
`Vary` and requests added after the SW w3c/ServiceWorker#1542.
-
Virtual calls around TPAC time w3c/ServiceWorker#1536.
-
unable to open https://wicg.github.io/cookie-store/ w3c/ServiceWorker#1547.
-
-
12 issues received 26 new comments.
-
Virtual call on November 20, 2020 w3c/ServiceWorker#1553 (5 comments by @annevk, @asakusuma, @mfalken, @wanderview)
-
consider allowing a non-scope identifier for registrations w3c/ServiceWorker#1512 (1 comment by @wanderview)
-
w3c/ServiceWorker#745 (1 comment by @James-E-A)
-
w3c/ServiceWorker#1356 (1 comment by @davidmaxwaterman)
-
Implementations are missing navigator.serviceWorker in workers w3c/ServiceWorker#1552 (1 comment by @makotoshimazu)
-
-
1 pull request received 1 new comment.
w3c/manifest
-
3 issues opened.
-
Spec Metadata Lists Incorrect Values for Chrome w3c/manifest#939, by @jpmedley.
-
How could I participate and create an alwaysOnTop flag? w3c/manifest#938, by @MickeyPickles.
-
4 issues received 8 new comments.
-
Spec Metadata Lists Incorrect Values for Chrome w3c/manifest#939 (5 comments by @christianliebel, @jpmedley, @sidvishnoi)
-
Documentation on choosing between "equally appropriate" icons does not match the provided example w3c/manifest#940 (1 comment by @aarongustafson)
-
w3c/manifest#726 (1 comment by @nuxodin)
-
-
3 pull requests received 4 new comments.
-
Processing the manifest is no longer a function of document URL w3c/manifest#834 (1 comment by @dmurph)
-
Editorial: Move some members to App Information Note w3c/manifest#924 (1 comment by @aarongustafson)
w3c/FileAPI
-
1 issue opened.
-
Support using AbortController with FileAPI w3c/FileAPI#159, by @benjamingr.
-
-
1 issue received 6 new comments.
-
Support using AbortController with FileAPI w3c/FileAPI#159 (6 comments by @annevk, @benjamingr, @domenic, @mkruisselbrink)
-
w3c/manifest-app-info
-
1 issue opened.
-
Should we suggest a means of tracking where a PWA was installed from? w3c/manifest-app-info#19, by @aarongustafson.
-
-
1 issue closed.
-
Definition of supplementary manifest members overriding the core manifest w3c/manifest-app-info#18.
-
-
4 issues received 6 new comments.
-
As these are on the web, is market availability an issue? w3c/manifest-app-info#7 (2 comments by @aarongustafson, @diekus)
-
The manifest has a `lang`, but what if multiple languages are supported? w3c/manifest-app-info#10 (2 comments by @aarongustafson, @diekus)
-
Would it be helpful to provide whether the app is ad-supported or supports in-app purchases? w3c/manifest-app-info#8 (1 comment by @TomCJones)
-
Definition of supplementary manifest members overriding the core manifest w3c/manifest-app-info#18 (1 comment by @aarongustafson)
-
w3c/pointerlock
-
1 pull request received 11 new comments.
w3c/uievents
-
4 issues opened.
-
Document the cancelability of wheel events w3c/uievents#282, by @smfr.
-
Composition events lack on* event handler attributes w3c/uievents#280, by @saschanaz.
-
We don't have a definition for "contextmenu" event w3c/uievents#279, by @mustaqahmed.
-
-
1 issue received 1 new comment.
w3c/web-share
-
1 issue opened.
-
Screen Freeze with WebGL Build w3c/web-share#191, by @asyranamin.
-
-
1 issue closed.
-
Screen Freeze with WebGL Build w3c/web-share#191.
-
-
1 issue received 2 new comments.
w3c/badging
-
1 issue opened.
-
Has anything changed with the badge API? w3c/badging#80, by @JohnRSim.
-
-
1 issue closed.
-
Has anything changed with the badge API? w3c/badging#80.
-
-
1 issue received 2 new comments.
-
Has anything changed with the badge API? w3c/badging#80 (2 comments by @fallaciousreasoning, @JohnRSim)
-
w3c/gamepad
-
1 pull request received 1 new comment.
w3c/IndexedDB
-
1 issue received 1 new comment.
TR publications
-
9 documents published.
-
Clipboard API and events published as a Working Draft. History of Clipboard API and events
-
Gamepad published as a Working Draft. History of Gamepad
-
Intersection Observer published as a Working Draft. History of Intersection Observer
-
ARIA in HTML published 3 times as a Working Draft. History of ARIA in HTML
-
The Screen Orientation API published as a Working Draft. History of The Screen Orientation API
-
Web App Manifest published as a Working Draft. History of Web App Manifest
-
Web Share API published as a Working Draft. History of Web Share API
-
Participants
-
7 participants joined.
-
Diego Gonzalez-Zuniga (W3C Invited Experts) joined.
-
Tomasz Jakut (W3C Invited Experts) joined.
-
Glenn Hartmann (Google LLC) joined.
-
Anupam Snigdha (Microsoft Corporation) joined.
-
alex keng (Microsoft Corporation) joined.
-
Caio Gondim (The New York Times) joined.
-
Matthew DeLambo (The New York Times) joined.
-
-
1 participant left.
-
Diego Gonzalez-Zuniga (W3C Invited Experts) left.
-
GitHub
w3c/ServiceWorker
-
4 issues opened.
-
Detecting service worker termination w3c/ServiceWorker#1550, by @Ale763.
-
ServiceWorkerContainer's message event is incorrectly linked to ServiceWorkerGlobalScope event list w3c/ServiceWorker#1549, by @saschanaz.
-
unable to open https://wicg.github.io/cookie-store/ w3c/ServiceWorker#1547, by @danyan.
-
-
2 issues closed.
-
Should we consider Worklets as clients? w3c/ServiceWorker#1502.
-
Virtual Call: pattern matching scopes w3c/ServiceWorker#1535.
-
-
9 issues received 65 new comments.
-
consider allowing a non-scope identifier for registrations w3c/ServiceWorker#1512 (22 comments by @asutherland, @wanderview, @youennf)
-
Virtual calls around TPAC time w3c/ServiceWorker#1536 (18 comments by @annevk, @asutherland, @jakearchibald, @jeffposnick, @jungkees, @makotoshimazu, @mfalken, @wanderview)
-
w3c/ServiceWorker#693 (1 comment by @simondrabble)
-
-
2 pull requests opened.
-
Use `undefined` union type for getRegistration() w3c/ServiceWorker#1548, by @saschanaz.
-
Set correct embedder policy and cross-origin isolation mode w3c/ServiceWorker#1545, by @yutakahirano.
-
-
3 pull requests received 15 new comments.
-
Set correct embedder policy and cross-origin isolation mode w3c/ServiceWorker#1545 (11 comments by @annevk, @domenic, @yutakahirano)
-
Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) w3c/ServiceWorker#1526 (1 comment by @annevk)
-
w3c/manifest
-
1 issue opened.
-
Feature: Open shortcuts on the already open app w3c/manifest#937, by @CheloXL.
-
-
2 issues closed.
-
Related applications parsing is incorrect w3c/manifest#936.
-
Feature: Open shortcuts on the already open app w3c/manifest#937.
-
-
8 issues received 15 new comments.
-
TPAC planning and specification status report w3c/manifest#906 (4 comments by @anssiko, @dmurph, @marcoscaceres)
-
badge purpose "monochrome" is only supported by Firefox w3c/manifest#905 (3 comments by @christianliebel, @mgiuca, @phoglenix)
-
Could you review Chrome/Firefox implementation regarding `fullscreen` display mode on Mac? w3c/manifest#934 (2 comments by @marcoscaceres, @mgiuca)
-
Related applications parsing is incorrect w3c/manifest#936 (2 comments by @aarongustafson, @marcoscaceres)
-
w3c/manifest#586 (1 comment by @marcoscaceres)
-
w3c/manifest#446 (1 comment by @marcoscaceres)
-
-
2 pull requests merged.
-
Editorial: Fix related_applications parsing instructions w3c/manifest#933.
-
chore(ci): use the spec-prod GitHub action w3c/manifest#935.
-
-
2 pull requests received 8 new comments.
-
Adding field `display_override` to the manifest w3c/manifest#932 (7 comments by @aarongustafson, @dmurph, @mgiuca, @NotWoods)
-
Editorial: Fix related_applications parsing instructions w3c/manifest#933 (1 comment by @marcoscaceres)
-
w3c/gamepad
-
1 issue opened.
-
Define ongamepadconnected/ongamepaddisconnected attributes w3c/gamepad#141, by @saschanaz.
-
-
2 issues closed.
-
Restrict getGamepads() to [SecureContext] w3c/gamepad#113.
-
Feature policy integration w3c/gamepad#119.
-
-
2 issues received 5 new comments.
-
Define ongamepadconnected/ongamepaddisconnected attributes w3c/gamepad#141 (3 comments by @marcoscaceres)
-
-
2 pull requests opened.
-
Add gamepad light indicator extension w3c/gamepad#143, by @fernando-80.
-
adding multitouch extension w3c/gamepad#142, by @fernando-80.
-
-
2 pull requests merged.
-
Require secure context for gamepad state and events w3c/gamepad#120.
-
Add permission policy integration w3c/gamepad#112.
-
-
2 pull requests received 17 new comments.
w3c/badging
-
1 issue opened.
-
Hide the badge or setting count to 0 w3c/badging#79, by @antoniodesousa.
-
-
3 issues received 7 new comments.
-
Would the browser icon also show a badge for "badged tabs"? w3c/badging#77 (1 comment by @fallaciousreasoning)
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/badging#75.
-
w3c/web-share
-
3 issues opened.
-
navigator.share in webviews w3c/web-share#190, by @vjbobeldijk.
-
Is immediately resolving share() behavior an acceptable behavior? w3c/web-share#189, by @saschanaz.
-
Should share() be allowed to resolve immediately? w3c/web-share#188, by @saschanaz.
-
-
5 issues closed.
-
navigator.share in webviews w3c/web-share#190.
-
Should the share method be directly on Navigator? w3c/web-share#180.
-
Is immediately resolving share() behavior an acceptable behavior? w3c/web-share#189.
-
Purpose of the sharePromise? w3c/web-share#179.
-
Add internationalization considerations section w3c/web-share#143.
-
-
10 issues received 38 new comments.
-
Should share() be allowed to resolve immediately? w3c/web-share#188 (10 comments by @ewilligers, @marcoscaceres, @mhochk, @saschanaz)
-
Proposal for a declarative web share button type w3c/web-share#176 (8 comments by @adactio, @Krinkle, @marcoscaceres, @simevidas)
-
Should the share method be directly on Navigator? w3c/web-share#180 (4 comments by @marcoscaceres, @mgiuca, @plinss, @saschanaz)
-
Explicitly state that UA can reject file based on its type w3c/web-share#127 (3 comments by @marcoscaceres, @mgiuca)
-
w3c/web-share#61 (1 comment by @saschanaz)
-
-
3 pull requests received 19 new comments.
-
Add "validate share data" algorithm w3c/web-share#185 (8 comments by @marcoscaceres, @martinthomson)
-
chore: inform people that l2 is folded into main spec w3c/web-share#134 (4 comments by @marcoscaceres, @sideshowbarker)
-
w3c/uievents
-
1 issue received 4 new comments.
w3c/pointerlock
-
1 issue opened.
-
Clarify how requestPointerLock relies on user activation w3c/pointerlock#67, by @marcoscaceres.
-
-
2 issues received 5 new comments.
-
Clarify how requestPointerLock relies on user activation w3c/pointerlock#67 (3 comments by @marcoscaceres, @mustaqahmed)
-
TPAC planning and specification status report w3c/pointerlock#64 (2 comments by @marcoscaceres, @mustaqahmed)
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/pointerlock#66.
-
-
1 pull request received 58 new comments.
-
Add lock options to requestPointerLock w3c/pointerlock#49 (58 comments by @domenic, @JamesHollyer, @reillyeon)
-
w3c/screen-orientation
-
1 issue received 1 new comment.
-
TPAC planning and specification status report w3c/screen-orientation#199 (1 comment by @marcoscaceres)
-
-
1 pull request closed.
-
Editorial: Align with Web IDL specification w3c/screen-orientation#200.
-
-
1 pull request received 1 new comment.
w3c/webappswg
-
1 issue opened.
-
TPAC 2020 Agenda w3c/webappswg#40, by @marcoscaceres.
-
-
1 issue received 13 new comments.
-
TPAC 2020 Agenda w3c/webappswg#40 (13 comments by @aarongustafson, @adrianhopebailie, @carmacleod, @fivedots, @hober, @johanneswilm, @LJWatson, @marcoscaceres, @siusin, @zcorpan)
-
w3c/FileAPI
-
1 issue received 2 new comments.
-
TPAC planning and specification status report w3c/FileAPI#156 (2 comments by @marcoscaceres, @mkruisselbrink)
-
w3c/contact-picker
-
1 issue opened.
-
Matching ContactAddress fields to autofill attributes w3c/contact-picker#71, by @jcayzac.
-
-
1 issue received 6 new comments.
-
Matching ContactAddress fields to autofill attributes w3c/contact-picker#71 (6 comments by @ianbjacobs, @jcayzac, @mnoorenberghe, @rsolomakhin)
-
w3c/using-aria
-
1 issue received 1 new comment.
w3c/IndexedDB
-
1 issue opened.
-
Use infra sorting definitions w3c/IndexedDB#346, by @inexorabletash.
-
-
1 issue received 2 new comments.
w3c/push-api
-
1 issue closed.
-
Meta: wide-review tracker w3c/push-api#265.
-
-
2 issues received 3 new comments.
-
TPAC planning and specification status report w3c/push-api#326 (2 comments by @marcoscaceres, @martinthomson)
-
w3c/push-api#265 (1 comment by @marcoscaceres)
-
TR publications
-
2 documents published.
-
Web Share API published as a Working Draft. History of Web Share API
-
Gamepad published as a Working Draft. History of Gamepad
-
Participants
-
1 chair appointed.
-
Marcos Caceres became a chair.
-
-
8 participants joined.
-
Tiger Oakes (Microsoft Corporation) joined.
-
Arturo Silva (The Washington Post) joined.
-
Brandon Wood (The New York Times) joined.
-
Shane Friedman (The New York Times) joined.
-
Randall Leeds (The New York Times) joined.
-
Anna Bialas (The New York Times) joined.
-
Austin Sullivan (Google LLC) joined.
-
Marcos Caceres (Apple Inc.) joined.
-
-
1 participant left.
-
Tiger Oakes (Microsoft Corporation) left.
-
-
2 organizations joined.
-
The Washington Post joined.
-
The New York Times joined.
-
GitHub
w3c/push-api
-
1 issue opened.
-
2 issues closed.
-
Specification status report for TPAC 2019 w3c/push-api#316.
-
-
3 issues received 3 new comments.
-
getting 401 Unauthorized after unsubscribing and resubscribing a new user with a new vapid key w3c/push-api#327 (1 comment by @Amiralizim)
w3c/manifest
-
2 issues opened.
-
Related applications parsing is incorrect w3c/manifest#936, by @aarongustafson.
-
-
7 issues received 14 new comments.
-
TPAC planning and specification status report w3c/manifest#906 (5 comments by @aarongustafson, @christianliebel, @dmurph, @marcoscaceres)
-
w3c/manifest#586 (1 comment by @dmurph)
-
w3c/manifest#399 (1 comment by @Trapfether)
-
-
1 pull request opened.
-
chore(ci): use the spec-prod GitHub action w3c/manifest#935, by @sidvishnoi.
-
-
2 pull requests received 13 new comments.
w3c/gamepad
-
1 issue received 2 new comments.
-
TPAC planning and specification status report w3c/gamepad#137 (2 comments by @marcoscaceres, @mrmcpowned)
-
-
1 pull request opened.
-
chore(ci): use the spec-prod GitHub action w3c/gamepad#140, by @sidvishnoi.
-
-
1 pull request merged.
-
chore(ci): use the spec-prod GitHub action w3c/gamepad#140.
-
-
1 pull request received 1 new comment.
w3c/web-share
-
8 issues opened.
-
Request to move privacy-related requirements to normative text w3c/web-share#187, by @melanierichards.
-
Mitigating user expectation mismatches with shared URL w3c/web-share#186, by @melanierichards.
-
Additional ShareData types? w3c/web-share#182, by @plinss.
-
Use of File in ShareData w3c/web-share#181, by @plinss.
-
Should the share method be directly on Navigator? w3c/web-share#180, by @plinss.
-
Purpose of the sharePromise? w3c/web-share#179, by @plinss.
-
Limiting to http/https is limiting w3c/web-share#178, by @martinthomson.
-
Proposal for a declarative web share button type w3c/web-share#176, by @adactio.
-
-
4 issues closed.
-
Drop the levels/versioning w3c/web-share#107.
-
Improve public documentation for Web Share w3c/web-share#17.
-
Share blobs via a Blob URL? w3c/web-share#7.
-
-
10 issues received 44 new comments.
-
Proposal for a declarative web share button type w3c/web-share#176 (16 comments by @adactio, @ewilligers, @marcoscaceres, @saschanaz)
-
Use of File in ShareData w3c/web-share#181 (7 comments by @ewilligers, @marcoscaceres, @mkruisselbrink, @plinss, @saschanaz)
-
canShare() is not future compatible w3c/web-share#108 (6 comments by @ewilligers, @marcoscaceres, @othermaciej, @tomayac)
-
Additional ShareData types? w3c/web-share#182 (3 comments by @ewilligers, @marcoscaceres, @saschanaz)
-
Explain why canShare exists at definition. w3c/web-share#159 (3 comments by @marcoscaceres, @scheib)
-
Limiting to http/https is limiting w3c/web-share#178 (3 comments by @marcoscaceres, @martinthomson, @tomayac)
-
w3c/web-share#17 (1 comment by @ewilligers)
-
w3c/web-share#7 (1 comment by @ewilligers)
-
-
5 pull requests opened.
-
Add "validate share data" algorithm w3c/web-share#185, by @marcoscaceres.
-
Introduce canShareFiles w3c/web-share#184, by @ewilligers.
-
Check transient activation after sharePromise w3c/web-share#183, by @ewilligers.
-
Add canShare() method w3c/web-share#177, by @marcoscaceres.
-
chore(ci): use the spec-prod GitHub action w3c/web-share#175, by @sidvishnoi.
-
-
4 pull requests merged.
-
Check transient activation after sharePromise w3c/web-share#183.
-
chore: inform people that l2 is folded into main spec w3c/web-share#134.
-
Reject non-http URLs for url member w3c/web-share#174.
-
chore(ci): use the spec-prod GitHub action w3c/web-share#175.
-
-
4 pull requests received 20 new comments.
-
chore: inform people that l2 is folded into main spec w3c/web-share#134 (1 comment by @marcoscaceres)
w3c/ServiceWorker
-
9 issues opened.
-
should FetchEvent.request.signal reflect abort status of outer request? w3c/ServiceWorker#1544, by @wanderview.
-
cache.addAll() is not consistent in aborting outstanding requests on error w3c/ServiceWorker#1543, by @wanderview.
-
`Vary` and requests added after the SW w3c/ServiceWorker#1542, by @yoavweiss.
-
Define openWindow() better w3c/ServiceWorker#1540, by @annevk.
-
Create/uplift tests for openWindow w3c/ServiceWorker#1539, by @annevk.
-
importScripts request does not include Service-Worker header w3c/ServiceWorker#1538, by @tms320c.
-
export 'ServiceWorkerRegistration/service worker registration' w3c/ServiceWorker#1537, by @mkruisselbrink.
-
Virtual calls around TPAC time w3c/ServiceWorker#1536, by @jakearchibald.
-
Virtual Call: pattern matching scopes w3c/ServiceWorker#1535, by @wanderview.
-
-
3 issues closed.
-
importScripts request does not include Service-Worker header w3c/ServiceWorker#1538.
-
export 'ServiceWorkerRegistration/service worker registration' w3c/ServiceWorker#1537.
-
Create F2F agenda - 16 September 2019 w3c/ServiceWorker#1460.
-
-
10 issues received 52 new comments.
-
Virtual Call: pattern matching scopes w3c/ServiceWorker#1535 (16 comments by @annevk, @asakusuma, @asutherland, @jakearchibald, @makotoshimazu, @wanderview, @youennf)
-
Virtual calls around TPAC time w3c/ServiceWorker#1536 (14 comments by @annevk, @asakusuma, @asutherland, @jakearchibald, @jungkees, @makotoshimazu, @mfalken, @tomayac, @wanderview, @yoavweiss, @youennf)
-
should FetchEvent.request.signal reflect abort status of outer request? w3c/ServiceWorker#1544 (7 comments by @annevk, @jakearchibald, @wanderview)
-
`Vary` and requests added after the SW w3c/ServiceWorker#1542 (3 comments by @wanderview, @yoavweiss)
-
importScripts request does not include Service-Worker header w3c/ServiceWorker#1538 (3 comments by @jakearchibald, @tms320c)
-
cache.addAll() is not consistent in aborting outstanding requests on error w3c/ServiceWorker#1543 (2 comments by @wanderview)
-
export 'ServiceWorkerRegistration/service worker registration' w3c/ServiceWorker#1537 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#745 (1 comment by @saburo70)
-
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/ServiceWorker#1541, by @autokagami.
-
-
2 pull requests merged.
-
Editorial: Align with Web IDL specification w3c/ServiceWorker#1541.
-
Use new Streams algorithms w3c/ServiceWorker#1533.
-
-
1 pull request closed.
-
Override the "mode" of Service Worker requests w3c/ServiceWorker#1534.
-
-
4 pull requests received 21 new comments.
-
Handle asynchronous modules (top-level await). w3c/ServiceWorker#1444 (4 comments by @hiroshige-g, @littledan)
-
Editorial: Align with Web IDL specification w3c/ServiceWorker#1530 (4 comments by @j-f1, @jakearchibald, @saschanaz)
-
Override the "mode" of Service Worker requests w3c/ServiceWorker#1534 (3 comments by @jakearchibald, @jugglinmike, @wanderview)
w3c/badging
-
2 issues opened.
-
TPAC planning and specification status report w3c/badging#78, by @marcoscaceres.
-
Would the browser icon also show a badge for "badged tabs"? w3c/badging#77, by @CombeeMike.
-
w3c/pointerlock
-
1 pull request received 17 new comments.
w3c/IndexedDB
-
1 issue received 1 new comment.
w3c/webappswg
-
2 issues closed.
-
Upgrade the WebApps WG GitHub team w3c/webappswg#38.
-
Look at progressing IntersectionObserver w3c/webappswg#29.
-
-
1 issue reopened.
-
Initiate wide review of Web Share API w3c/webappswg#27, by @marcoscaceres.
-
-
4 issues received 6 new comments.
-
Initiate wide review of Web Share API w3c/webappswg#27 (3 comments by @LJWatson, @marcoscaceres, @saschanaz)
-
w3c/manifest-app-info
-
1 issue opened.
-
Definition of supplementary manifest members overriding the core manifest w3c/manifest-app-info#18, by @espinr.
-
TR publications
-
12 documents published.
-
Web Share API published twice as a Working Draft. History of Web Share API
-
Clipboard API and events published as a Working Draft. History of Clipboard API and events
-
Selection API published as a Working Draft. History of Selection API
-
HTML Accessibility API Mappings 1.0 published twice as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
ARIA in HTML published 5 times as a Working Draft. History of ARIA in HTML
-
Participants
-
1 chair stepped down.
-
Marcos Caceres stepped down as a chair.
-
-
2 participants joined.
-
Emilio Cobos Álvarez (Mozilla Foundation) joined.
-
Zitao Wang (Huawei) joined.
-
-
1 participant left.
-
Marcos Caceres (Apple Inc.) left.
-
-
2 organizations joined.
-
Huawei joined.
-
Kodansha, Publishers, Ltd. joined.
-
GitHub
w3c/ServiceWorker
-
2 issues opened.
-
Proposal: clientURL property on FetchEvent w3c/ServiceWorker#1532, by @jeffposnick.
-
allow service workers to created nested dedicated workers w3c/ServiceWorker#1529, by @wanderview.
-
-
1 issue closed.
-
Add 'immediate: true' to the draft spec w3c/ServiceWorker#1489.
-
-
10 issues received 40 new comments.
-
consider allowing a non-scope identifier for registrations w3c/ServiceWorker#1512 (11 comments by @jakearchibald, @wanderview)
-
What to do when an installed service worker's certificate changes/expires w3c/ServiceWorker#1523 (10 comments by @davidben, @jakearchibald, @sleevi, @youennf)
-
allow service workers to created nested dedicated workers w3c/ServiceWorker#1529 (4 comments by @jakearchibald, @mfalken, @wanderview)
-
Proposal: clientURL property on FetchEvent w3c/ServiceWorker#1532 (3 comments by @jeffposnick, @wanderview)
-
should sec-ch-ua headers be visible in FetchEvent.request.headers w3c/ServiceWorker#1525 (3 comments by @annevk, @jakearchibald)
-
w3c/ServiceWorker#913 (1 comment by @wanderview)
-
w3c/ServiceWorker#977 (1 comment by @ciekawy)
-
-
6 pull requests opened.
-
Override the "mode" of Service Worker requests w3c/ServiceWorker#1534, by @jugglinmike.
-
Use new Streams algorithms w3c/ServiceWorker#1533, by @domenic.
-
Give the empty destination to the CORP check w3c/ServiceWorker#1531, by @yutakahirano.
-
Editorial: Align with Web IDL specification w3c/ServiceWorker#1530, by @autokagami.
-
Editorial: update to modern Web IDL conventions w3c/ServiceWorker#1528, by @domenic.
-
Update environment settings object creation w3c/ServiceWorker#1527, by @domenic.
-
-
4 pull requests merged.
-
Give the empty destination to the CORP check w3c/ServiceWorker#1531.
-
Editorial: Align with Web IDL specification w3c/ServiceWorker#1530.
-
Update environment settings object creation w3c/ServiceWorker#1527.
-
Editorial: update to modern Web IDL conventions w3c/ServiceWorker#1528.
-
-
4 pull requests received 40 new comments.
-
Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) w3c/ServiceWorker#1526 (25 comments by @jakearchibald, @wanderview, @ylafon)
-
Editorial: update to modern Web IDL conventions w3c/ServiceWorker#1528 (12 comments by @domenic, @jakearchibald)
-
Define Purge Service Worker Registrations w3c/ServiceWorker#1506 (2 comments by @jungkees, @wanderview)
-
w3c/manifest
-
1 issue reopened.
-
Privacy Review: handle start_url tracking w3c/manifest#399, by @marcoscaceres.
-
-
6 issues received 43 new comments.
-
w3c/manifest#586 (22 comments by @alancutter, @andreban, @benfrancis, @dmurph, @dominickng, @glennhartmann, @mgiuca)
-
w3c/manifest#399 (13 comments by @alancutter, @dominickng, @lknik, @marcoscaceres, @mgiuca, @pizzapanther, @ssb22, @wwwizzarrdry)
-
Shortcuts: Dynamic update or JS access to URLs w3c/manifest#867 (2 comments by @aarongustafson, @bathos)
-
Provide guidance to UAs on appropriate names for "platform" members w3c/manifest#862 (2 comments by @christianliebel, @mgiuca)
-
-
1 pull request opened.
-
Editorial: Fix related_applications parsing instructions w3c/manifest#933, by @benfredwells.
-
-
2 pull requests received 18 new comments.
w3c/webappswg
-
3 issues closed.
-
Pull repository data from "reports" json. w3c/webappswg#4.
-
Move over WICG repositories w3c/webappswg#2.
-
Publish manifest-app-info as FPWD w3c/webappswg#39.
-
-
7 issues received 11 new comments.
-
Look at progressing IntersectionObserver w3c/webappswg#29 (2 comments by @marcoscaceres, @szager-chromium)
-
w3c/webappswg#4 (1 comment by @marcoscaceres)
-
w3c/webappswg#2 (1 comment by @marcoscaceres)
w3c/pointerlock
-
1 issue received 1 new comment.
-
w3c/pointerlock#36 (1 comment by @JamesHollyer)
-
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/pointerlock#66, by @autokagami.
-
-
1 pull request received 24 new comments.
-
Add lock options to requestPointerLock w3c/pointerlock#49 (24 comments by @domenic, @JamesHollyer, @jameshollyergoogle)
-
w3c/web-share
-
1 issue opened.
-
1 issue closed.
-
files members should be a sequence, not a FrozenArray w3c/web-share#165.
-
-
3 issues received 13 new comments.
-
Shared URLs can be auto-fetched by native applications without respecting same-origin policy w3c/web-share#173 (10 comments by @ericlaw1979, @marcoscaceres, @martinthomson, @mgiuca, @snan, @tomayac)
-
-
4 pull requests opened.
-
Reject non-http URLs for url member w3c/web-share#174, by @marcoscaceres.
-
Editorial: Align with Web IDL specification w3c/web-share#172, by @autokagami.
-
Editorial: s/feature-policy/permissions-policy w3c/web-share#171, by @marcoscaceres.
-
User a sequence for files w3c/web-share#170, by @marcoscaceres.
-
-
3 pull requests merged.
-
Editorial: Align with Web IDL specification w3c/web-share#172.
-
User a sequence for files w3c/web-share#170.
-
Editorial: s/feature-policy/permissions-policy w3c/web-share#171.
-
-
2 pull requests received 12 new comments.
-
Reject non-http URLs for url member w3c/web-share#174 (11 comments by @ewilligers, @marcoscaceres, @martinthomson, @whsieh)
-
chore: inform people that l2 is folded into main spec w3c/web-share#134 (1 comment by @marcoscaceres)
-
w3c/web-locks
-
1 pull request opened.
-
Fix linking errors w3c/web-locks#66, by @inexorabletash.
-
-
1 pull request merged.
-
Fix linking errors w3c/web-locks#66.
-
-
1 pull request received 1 new comment.
w3c/uievents
-
6 issues opened.
-
Update focusin/focusout event order to match implementations? w3c/uievents#276, by @devongovett.
-
Upstream InputEvent w3c/uievents#275, by @annevk.
-
Giving JavaScript ability to toggle the state of the modifier keys w3c/uievents#274, by @gked.
-
Insert Key is not part of the spec as a modifier key w3c/uievents#273, by @gked.
-
IDL for legacy dictionary members are not parsed as IDL w3c/uievents#271, by @saschanaz.
-
Define events directly caused by user interaction w3c/uievents#270, by @npm1.
-
-
2 issues closed.
-
IDL for legacy dictionary members are not parsed as IDL w3c/uievents#271.
-
9.4 mutation events are deprecated w3c/uievents#102.
-
-
11 issues received 25 new comments.
-
Insert Key is not part of the spec as a modifier key w3c/uievents#273 (6 comments by @chaals, @garykac, @gked, @LJWatson, @masayuki-nakano)
-
Giving JavaScript ability to toggle the state of the modifier keys w3c/uievents#274 (2 comments by @garykac, @rniwa)
-
Should require Input event to be fired within same event loop as keydown? keypress? neither? w3c/uievents#238 (2 comments by @annevk, @garykac)
-
w3c/uievents#66 (1 comment by @garykac)
-
w3c/uievents#220 (1 comment by @garykac)
-
-
1 pull request opened.
-
Mark the legacy dictionary members as IDL w3c/uievents#272, by @saschanaz.
-
-
1 pull request merged.
-
Mark the legacy dictionary members as IDL w3c/uievents#272.
-
w3c/badging
-
2 issues opened.
-
Not working on PWA w3c/badging#76, by @lagcamgc.
-
Publish FWPD? w3c/badging#74, by @marcoscaceres.
-
-
2 issues received 3 new comments.
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/badging#75, by @autokagami.
-
w3c/IndexedDB
-
2 issues received 2 new comments.
-
w3c/IndexedDB#206 (1 comment by @masterkidan)
-
w3c/IndexedDB#191 (1 comment by @everlose)
-
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/IndexedDB#345, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/IndexedDB#345.
-
w3c/FileAPI
-
1 issue closed.
-
Store HTTPS state on Blob objects w3c/FileAPI#35.
-
-
3 issues received 7 new comments.
-
w3c/FileAPI#35 (1 comment by @annevk)
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/FileAPI#158, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/FileAPI#158.
-
w3c/screen-orientation
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/screen-orientation#200, by @autokagami.
-
w3c/contact-picker
-
2 issues received 5 new comments.
-
Add phonetic name as one of `ContactAddress` properties w3c/contact-picker#70 (4 comments by @agektmr, @eternalharvest, @xfq)
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69 (1 comment by @eternalharvest)
-
w3c/gamepad
-
1 issue opened.
-
Consider how to support devices like Apple Remote w3c/gamepad#139, by @nondebug.
-
-
2 issues received 2 new comments.
-
w3c/gamepad#19 (1 comment by @daoshengmu)
-
w3c/gamepad#56 (1 comment by @nondebug)
-
w3c/manifest-app-info
-
2 issues opened.
-
Typo? at §2 w3c/manifest-app-info#17, by @ntounsi.
-
include accessibility features description w3c/manifest-app-info#16, by @ele-gall-ac-mineducation.
-
-
3 issues closed.
-
Publish the document to TR w3c/manifest-app-info#11.
-
Typo? at §2 w3c/manifest-app-info#17.
-
Ok to drop "main" branch? w3c/manifest-app-info#14.
-
-
3 issues received 4 new comments.
-
1 pull request merged.
-
chore: set up autopublish w3c/manifest-app-info#15.
-
-
1 pull request received 5 new comments.
TR publications
-
14 documents published.
-
Web App Manifest published 9 times as a Working Draft. History of Web App Manifest
-
Clipboard API and events published as a Working Draft. History of Clipboard API and events
-
HTML Accessibility API Mappings 1.0 published as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
Web Share API published as a Working Draft. History of Web Share API
-
ARIA in HTML published as a Working Draft. History of ARIA in HTML
-
Participants
-
4 participants joined.
-
Jack J (Google LLC) joined.
-
Tantek Çelik (Mozilla Foundation) joined.
-
Tiger Oakes (Microsoft Corporation) joined.
-
Kagami Rosylight (Mozilla Foundation) joined.
-
-
1 participant left.
-
Jay Harris (Brave Software Inc.) left.
-
GitHub
w3c/uievents
-
1 issue opened.
-
9 issues closed.
-
Need algorithm for how composition events are fired w3c/uievents#199.
-
Need algorithm for how input events are fired w3c/uievents#198.
-
Time to CR? w3c/uievents#168.
-
Support queryKeyCap w3c/uievents#156.
-
Fire an event on caret position change w3c/uievents#111.
-
Need way to determine what keys are supported on device. w3c/uievents#8.
-
Specification status report for TPAC 2019 w3c/uievents#242.
-
Add support for keyboard lock to test page w3c/uievents#248.
-
Update to constructor operations w3c/uievents#243.
-
-
9 issues received 13 new comments.
-
"keyCode" is the only way to work with KeyboardEvents now w3c/uievents#267 (5 comments by @garykac, @photopea)
-
Should require Input event to be fired within same event loop as keydown? keypress? neither? w3c/uievents#238 (1 comment by @garykac)
-
w3c/uievents#199 (1 comment by @garykac)
-
w3c/uievents#198 (1 comment by @garykac)
-
w3c/uievents#142 (1 comment by @garykac)
-
w3c/uievents#168 (1 comment by @garykac)
-
w3c/uievents#102 (1 comment by @garykac)
-
w3c/uievents#8 (1 comment by @garykac)
-
w3c/uievents#4 (1 comment by @garykac)
-
w3c/ServiceWorker
-
6 issues opened.
-
should sec-ch-ua headers be visible in FetchEvent.request.headers w3c/ServiceWorker#1525, by @wanderview.
-
Open(cacheName) resolvse with null value, though cacheName matches key w3c/ServiceWorker#1524, by @ATerentjev.
-
What to do when an installed service worker's certificate changes/expires w3c/ServiceWorker#1523, by @mfalken.
-
Make WebRTC usable as a backend for Service Workers to fulfill requests from a peer-to-peer network w3c/ServiceWorker#1522, by @interfect.
-
why service-worker.js can not be automatically detected w3c/ServiceWorker#1521, by @UNDERCOVERj.
-
can service worker scope include `username:password@` URL credentials? w3c/ServiceWorker#1520, by @wanderview.
-
-
4 issues closed.
-
Open(cacheName) resolvse with null value, though cacheName matches key w3c/ServiceWorker#1524.
-
cache.match() and COEP w3c/ServiceWorker#1490.
-
provide a way to execute work after browser has consumed a response w3c/ServiceWorker#1397.
-
why service-worker.js can not be automatically detected w3c/ServiceWorker#1521.
-
-
10 issues received 31 new comments.
-
consider allowing a non-scope identifier for registrations w3c/ServiceWorker#1512 (8 comments by @asutherland, @jakearchibald, @wanderview)
-
Open(cacheName) resolvse with null value, though cacheName matches key w3c/ServiceWorker#1524 (6 comments by @ATerentjev, @wanderview)
-
should sec-ch-ua headers be visible in FetchEvent.request.headers w3c/ServiceWorker#1525 (5 comments by @jakearchibald, @wanderview, @yoavweiss)
-
can service worker scope include `username:password@` URL credentials? w3c/ServiceWorker#1520 (4 comments by @annevk, @wanderview)
-
w3c/ServiceWorker#691 (1 comment by @khiav223577)
-
Make WebRTC usable as a backend for Service Workers to fulfill requests from a peer-to-peer network w3c/ServiceWorker#1522 (1 comment by @interfect)
-
why service-worker.js can not be automatically detected w3c/ServiceWorker#1521 (1 comment by @jakearchibald)
-
-
1 pull request opened.
-
Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) w3c/ServiceWorker#1526, by @wanderview.
-
-
1 pull request merged.
-
Introduce Cross-Origin Embedder Policy w3c/ServiceWorker#1516.
-
-
2 pull requests received 3 new comments.
-
Introduce Cross-Origin Embedder Policy w3c/ServiceWorker#1516 (2 comments by @jakearchibald, @yutakahirano)
-
Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) w3c/ServiceWorker#1526 (1 comment by @sideshowbarker)
-
w3c/manifest
-
9 issues opened.
-
Add field: public key (certificate) w3c/manifest#930, by @darkdragon-001.
-
Chore: Update contribution guidelines to include commit prefixes w3c/manifest#929, by @aarongustafson.
-
auto value of the dir member w3c/manifest#923, by @xfq.
-
Feature Request: Shortcuts categories w3c/manifest#922, by @aarongustafson.
-
can multiple PWA scopes exist for virtual paths w3c/manifest#919, by @rmrbytes.
-
Combine all security & privacy sections into one? w3c/manifest#915, by @mgiuca.
-
12 issues closed.
-
Chore: Update contribution guidelines to include commit prefixes w3c/manifest#929.
-
Allow installed PWA to run on OS login w3c/manifest#845.
-
Remove store metadata into own spec or note? w3c/manifest#876.
-
Why does obtaining not check a MIME type? w3c/manifest#821.
-
Add link type "manifest" to HTML w3c/manifest#778.
-
"Delay the load event" should happen in HTML w3c/manifest#891.
-
Bad cross references - remove `data-cite` where possible w3c/manifest#884.
-
can multiple PWA scopes exist for virtual paths w3c/manifest#919.
-
purpose: badge should be defined as default badge for Notifications API w3c/manifest#508.
-
At risk: ManifestImageResource.platform? w3c/manifest#909.
-
scope="../" should be invalid w3c/manifest#551.
-
shortcuts compares wrong scope w3c/manifest#885.
-
-
31 issues received 105 new comments.
-
Feature Request: Shortcuts categories w3c/manifest#922 (13 comments by @aarongustafson, @christianliebel, @marcoscaceres)
-
Example suggests that `icons` `sizes` mean a minimum size, but normative text doesn't support that w3c/manifest#925 (11 comments by @benfrancis, @marcoscaceres, @mgiuca, @phoglenix)
-
Should dynamically calculated property values (like `scope` and `start_url`) be programmatically accessible? w3c/manifest#931 (7 comments by @alancutter, @dominickng, @marcoscaceres, @mgiuca, @tomayac)
-
Clarify behaviour of a page linking to a manifest that is not within scope of that manifest w3c/manifest#784 (6 comments by @b1tr0t, @marcoscaceres, @mgiuca)
-
Add field: public key (certificate) w3c/manifest#930 (5 comments by @alancutter, @darkdragon-001, @dominickng, @mgiuca)
-
Clarify how images are loaded, and that they don't depend on CSP w3c/manifest#910 (5 comments by @aarongustafson, @marcoscaceres)
-
Bring back "serviceworker" member w3c/manifest#864 (4 comments by @aarongustafson, @marcoscaceres, @mgiuca)
-
Related applications members (at risk?) w3c/manifest#877 (3 comments by @aarongustafson, @marcoscaceres, @mgiuca)
-
Provide guidance to UAs on appropriate names for "platform" members w3c/manifest#862 (3 comments by @aarongustafson, @mgiuca)
-
can multiple PWA scopes exist for virtual paths w3c/manifest#919 (2 comments by @christianliebel, @rmrbytes)
-
Bad cross references - remove `data-cite` where possible w3c/manifest#884 (2 comments by @aarongustafson, @marcoscaceres)
-
w3c/manifest#586 (1 comment by @dmurph)
-
w3c/manifest#666 (1 comment by @marcoscaceres)
-
Chore: Update contribution guidelines to include commit prefixes w3c/manifest#929 (1 comment by @marcoscaceres)
-
w3c/manifest#611 (1 comment by @marcoscaceres)
-
w3c/manifest#508 (1 comment by @mgiuca)
-
w3c/manifest#551 (1 comment by @mgiuca)
-
-
12 pull requests opened.
-
Adding field `display_override` to the manifest w3c/manifest#932, by @dmurph.
-
Editorial: include JSON Schema into spec w3c/manifest#928, by @marcoscaceres.
-
Editorial: clarify where to get apps name from w3c/manifest#927, by @marcoscaceres.
-
Editorial: clarify when/how 'auto' is applied w3c/manifest#926, by @marcoscaceres.
-
Editorial: Move some members to App Information Note w3c/manifest#924, by @marcoscaceres.
-
Revert "Editorial: Move some members to App Information Note" w3c/manifest#921, by @aarongustafson.
-
Chore: Moving to data-cite for the accessible name w3c/manifest#920, by @aarongustafson.
-
Pick up export in https://github.com/whatwg/html/pull/5717 w3c/manifest#918, by @aarongustafson.
-
chore: update PULL_REQUEST_TEMPLATE.md w3c/manifest#916, by @marcoscaceres.
-
Editorial: clean up ExternalApplicationResource w3c/manifest#914, by @marcoscaceres.
-
BREAKING CHANGE: remove `platform` from ManifestImageResource w3c/manifest#913, by @christianliebel.
-
chore: run tidy w3c/manifest#911, by @mgiuca.
-
-
9 pull requests merged.
-
Editorial: include JSON Schema into spec w3c/manifest#928.
-
Editorial: Move some members to App Information Note w3c/manifest#900.
-
Use HTML machinery to fetch manifests w3c/manifest#894.
-
Chore: Moving to data-cite for the accessible name w3c/manifest#920.
-
chore: update PULL_REQUEST_TEMPLATE.md w3c/manifest#916.
-
Editorial: clean up ExternalApplicationResource w3c/manifest#914.
-
BREAKING CHANGE: remove `platform` from ManifestImageResource w3c/manifest#913.
-
fix: shortcuts compares wrong scope w3c/manifest#908.
-
chore: run tidy w3c/manifest#911.
-
-
2 pull requests closed.
-
Pick up export in https://github.com/whatwg/html/pull/5717 w3c/manifest#918.
-
Revert "Editorial: Move some members to App Information Note" w3c/manifest#921.
-
-
10 pull requests received 80 new comments.
-
Adding field `display_override` to the manifest w3c/manifest#932 (25 comments by @dmurph, @marcoscaceres, @mgiuca)
-
Processing the manifest is no longer a function of document URL w3c/manifest#834 (25 comments by @alancutter, @dmurph, @dominickng, @marcoscaceres, @mgiuca)
-
Editorial: Move some members to App Information Note w3c/manifest#900 (9 comments by @aarongustafson, @marcoscaceres)
-
Editorial: clarify when/how 'auto' is applied w3c/manifest#926 (7 comments by @marcoscaceres, @r12a, @xfq)
-
Editorial: Move some members to App Information Note w3c/manifest#924 (4 comments by @marcoscaceres)
-
Pick up export in https://github.com/whatwg/html/pull/5717 w3c/manifest#918 (1 comment by @marcoscaceres)
-
BREAKING CHANGE: remove `platform` from ManifestImageResource w3c/manifest#913 (1 comment by @mgiuca)
-
w3c/gamepad
-
1 issue opened.
-
Xbox One impulse trigger effects w3c/gamepad#138, by @nondebug.
-
-
3 issues received 7 new comments.
-
Xbox One impulse trigger effects w3c/gamepad#138 (4 comments by @marcoscaceres, @mrmcpowned, @nondebug)
-
-
2 pull requests received 5 new comments.
w3c/web-share
-
4 issues opened.
-
Permissions policy 'self' is at risk w3c/web-share#169, by @ewilligers.
-
Add intent parameter w3c/web-share#168, by @dshanske.
-
Should we make share title mandatory? w3c/web-share#167, by @AshleyScirra.
-
files members should be a sequence, not a FrozenArray w3c/web-share#165, by @marcoscaceres.
-
-
3 issues closed.
-
Should we make share title mandatory? w3c/web-share#167.
-
Web Share API can be triggered from iframe sandbox w3c/web-share#155.
-
Feature Policy integration w3c/web-share#151.
-
-
5 issues received 18 new comments.
-
Should we make share title mandatory? w3c/web-share#167 (12 comments by @AshleyScirra, @ewilligers, @marcoscaceres, @mgiuca, @saschanaz)
-
Sharing service unavailable should reject with NotSupportedError w3c/web-share#126 (1 comment by @ewilligers)
-
-
1 pull request opened.
-
Introduce "web-share" feature policy w3c/web-share#166, by @ewilligers.
-
-
1 pull request merged.
-
Introduce "web-share" feature policy w3c/web-share#166.
-
-
1 pull request received 14 new comments.
-
Introduce "web-share" feature policy w3c/web-share#166 (14 comments by @ewilligers, @marcoscaceres, @othermaciej)
-
w3c/webappswg
-
3 issues opened.
-
Publish manifest-app-info as FPWD w3c/webappswg#39, by @marcoscaceres.
-
Upgrade the WebApps WG GitHub team w3c/webappswg#38, by @siusin.
-
Create a new repo for "manifest-app-info" w3c/webappswg#37, by @marcoscaceres.
-
-
1 issue closed.
-
Create a new repo for "manifest-app-info" w3c/webappswg#37.
-
-
3 issues received 8 new comments.
w3c/manifest-app-info
-
11 issues opened.
-
Ok to drop "main" branch? w3c/manifest-app-info#14, by @marcoscaceres.
-
Call for Consensus to publish a Working Group Note w3c/manifest-app-info#13, by @aarongustafson.
-
Publish the document to TR w3c/manifest-app-info#11, by @kenchris.
-
The manifest has a `lang`, but what if multiple languages are supported? w3c/manifest-app-info#10, by @aarongustafson.
-
Input requirements? w3c/manifest-app-info#9, by @aarongustafson.
-
Would it be helpful to provide whether the app is ad-supported or supports in-app purchases? w3c/manifest-app-info#8, by @aarongustafson.
-
As these are on the web, is market availability an issue? w3c/manifest-app-info#7, by @aarongustafson.
-
Developer information w3c/manifest-app-info#6, by @aarongustafson.
-
Featured graphic? w3c/manifest-app-info#5, by @aarongustafson.
-
Do we need a short description? w3c/manifest-app-info#4, by @aarongustafson.
-
Can we certify a "Publisher"? w3c/manifest-app-info#3, by @aarongustafson.
-
-
1 issue closed.
-
Call for Consensus to publish a Working Group Note w3c/manifest-app-info#13.
-
-
10 issues received 15 new comments.
-
Call for Consensus to publish a Working Group Note w3c/manifest-app-info#13 (1 comment by @marcoscaceres)
-
As these are on the web, is market availability an issue? w3c/manifest-app-info#7 (1 comment by @jgw96)
-
The manifest has a `lang`, but what if multiple languages are supported? w3c/manifest-app-info#10 (1 comment by @jgw96)
-
Add reference to license/usage permission of assets in manifest w3c/manifest-app-info#2 (1 comment by @aarongustafson)
-
Add change log support to the web app manifest w3c/manifest-app-info#1 (1 comment by @aarongustafson)
-
2 pull requests opened.
-
chore: set up autopublish w3c/manifest-app-info#15, by @marcoscaceres.
-
Prepare for First Public Working Draft w3c/manifest-app-info#12, by @marcoscaceres.
-
-
1 pull request merged.
-
Prepare for First Public Working Draft w3c/manifest-app-info#12.
-
-
1 pull request received 8 new comments.
-
Prepare for First Public Working Draft w3c/manifest-app-info#12 (8 comments by @aarongustafson, @marcoscaceres)
-
w3c/pointerlock
-
1 pull request received 19 new comments.
w3c/FileAPI
-
1 issue opened.
-
Async factory methods for Blob and File w3c/FileAPI#157, by @pwnall.
-
-
2 issues received 3 new comments.
-
w3c/FileAPI#99 (1 comment by @guest271314)
w3c/IndexedDB
-
1 issue opened.
-
Implementation limits on keys w3c/IndexedDB#344, by @pwnall.
-
-
1 issue closed.
-
Algorithm to "store a record" doesn't undo store on index constraint failure w3c/IndexedDB#342.
-
-
3 issues received 7 new comments.
-
Implementation limits on keys w3c/IndexedDB#344 (4 comments by @inexorabletash, @kaizhu256, @pwnall)
-
Cursor property updating precedes success event w3c/IndexedDB#340 (2 comments by @asutherland, @inexorabletash)
-
Algorithm to "store a record" doesn't undo store on index constraint failure w3c/IndexedDB#342 (1 comment by @inexorabletash)
-
-
1 pull request received 2 new comments.
-
[WIP] Initial algorithms / methods for putAll w3c/IndexedDB#343 (2 comments by @inexorabletash, @pwnall)
-
w3c/image-resource
-
1 pull request opened.
-
An image resource might not contain sizes or type w3c/image-resource#33, by @jyasskin.
-
-
1 pull request received 1 new comment.
-
An image resource might not contain sizes or type w3c/image-resource#33 (1 comment by @marcoscaceres)
-
w3c/uievents-code
-
1 issue opened.
-
IPR bot not enabled w3c/uievents-code#29, by @marcoscaceres.
-
-
1 issue closed.
-
IPR bot not enabled w3c/uievents-code#29.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
testing w3c/uievents-code#30, by @marcoscaceres.
-
-
1 pull request closed.
-
testing w3c/uievents-code#30.
-
w3c/uievents-key
-
1 pull request merged.
-
chore: add PULL_REQUEST_TEMPLATE.md w3c/uievents-key#48.
-
w3c/web-locks
-
1 pull request merged.
-
Fix typo w3c/web-locks#65.
-
-
1 pull request received 1 new comment.
TR publications
-
10 documents published.
-
Web App Manifest published 4 times as a Working Draft. History of Web App Manifest
-
HTML Accessibility API Mappings 1.0 published twice as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
Gamepad published as a Working Draft. History of Gamepad
-
Web Share API published twice as a Working Draft. History of Web Share API
-
Clipboard API and events published as a Working Draft. History of Clipboard API and events
-
Participants
-
2 participants joined.
-
Patrick Lauke (TetraLogical Services Ltd) joined.
-
Mustaq Ahmed (Google LLC) joined.
-
-
1 participant left.
-
Patrick Lauke (TetraLogical Services Ltd) left.
-
GitHub
w3c/uievents
-
2 issues opened.
-
TPAC planning and specification status report w3c/uievents#268, by @LJWatson.
-
"keyCode" is the only way to work with KeyboardEvents now w3c/uievents#267, by @photopea.
-
-
2 issues received 2 new comments.
w3c/IndexedDB
-
5 issues opened.
-
Algorithm to "store a record" doesn't undo store on index constraint failure w3c/IndexedDB#342, by @inexorabletash.
-
Cursor property updating precedes success event w3c/IndexedDB#340, by @inexorabletash.
-
[Cursor] got value flag. w3c/IndexedDB#339, by @cheako.
-
Specification status report for TPAC 2020 w3c/IndexedDB#338, by @inexorabletash.
-
TPAC planning and specification status report w3c/IndexedDB#337, by @LJWatson.
-
-
1 issue closed.
-
Add accessibility section w3c/IndexedDB#327.
-
-
5 issues received 8 new comments.
-
Allow version change transactions w/o modifying version number w3c/IndexedDB#304 (1 comment by @sicking)
-
2 pull requests opened.
-
[WIP] Initial algorithms / methods for putAll w3c/IndexedDB#343, by @inexorabletash.
-
Use Bikeshed's special syntax for linking to abstract operations w3c/IndexedDB#341, by @inexorabletash.
-
-
2 pull requests merged.
-
Use Bikeshed's special syntax for linking to abstract operations w3c/IndexedDB#341.
-
Add accessibility section draft. w3c/IndexedDB#328.
-
w3c/web-locks
-
2 pull requests opened.
-
More algorithm wrappers, infra type usage w3c/web-locks#64, by @inexorabletash.
-
Editorial: Markup/down fixes for proper Bikeshed algorithms w3c/web-locks#63, by @inexorabletash.
-
-
2 pull requests merged.
-
More algorithm wrappers, infra type usage w3c/web-locks#64.
-
Editorial: Markup/down fixes for proper Bikeshed algorithms w3c/web-locks#63.
-
-
1 pull request received 1 new comment.
-
Editorial: Markup/down fixes for proper Bikeshed algorithms w3c/web-locks#63 (1 comment by @inexorabletash)
-
w3c/manifest
-
11 issues opened.
-
Clarify how images are loaded, and that they don't depend on CSP w3c/manifest#910, by @marcoscaceres.
-
At risk: ManifestImageResource.platform? w3c/manifest#909, by @mgiuca.
-
Task switcher icon w3c/manifest#907, by @ronanyeah.
-
TPAC planning and specification status report w3c/manifest#906, by @LJWatson.
-
badge purpose "monochrome" is only supported by Firefox w3c/manifest#905, by @marcoscaceres.
-
Why is purpose a "unordered set of unique space-separated tokens"? w3c/manifest#903, by @marcoscaceres.
-
Do we need the "master" branch? w3c/manifest#901, by @aarongustafson.
-
i18n: Multiple manifest links with different hreflang? w3c/manifest#892, by @aarongustafson.
-
"Delay the load event" should happen in HTML w3c/manifest#891, by @marcoscaceres.
-
`shortcuts` missing privacy and security considerations section w3c/manifest#890, by @marcoscaceres.
-
"Authority of manifest" section is wrong w3c/manifest#888, by @mgiuca.
-
-
11 issues closed.
-
Add accessibility section w3c/manifest#860.
-
Task switcher icon w3c/manifest#907.
-
`shortcuts` missing privacy and security considerations section w3c/manifest#890.
-
Rename `purpose: badge` to `purpose: monochrome` and expand on it w3c/manifest#830.
-
Do we need the "master" branch? w3c/manifest#901.
-
Spec what it means to support "manifest" via <link>'s relList w3c/manifest#826.
-
Should dir and lang apply to name/description of app shortcuts? w3c/manifest#872.
-
Use the newly defined ImageResource w3c/manifest#854.
-
Color processing steps are incorrect w3c/manifest#760.
-
Security Risks in Web App Off-scope Navigation w3c/manifest#747.
-
Should manifest be HTTPS only? w3c/manifest#887.
-
-
20 issues received 58 new comments.
-
More precise control over app window features w3c/manifest#856 (8 comments by @amandabaker, @dmurph, @mgiuca, @sunggook)
-
Should manifest be HTTPS only? w3c/manifest#887 (8 comments by @dominickng, @marcoscaceres, @mgiuca)
-
At risk: ManifestImageResource.platform? w3c/manifest#909 (6 comments by @aarongustafson, @christianliebel, @marcoscaceres, @tomayac)
-
Why is purpose a "unordered set of unique space-separated tokens"? w3c/manifest#903 (5 comments by @marcoscaceres, @mgiuca)
-
badge purpose "monochrome" is only supported by Firefox w3c/manifest#905 (3 comments by @kenchris, @marcoscaceres, @mgiuca)
-
Spec what it means to support "manifest" via <link>'s relList w3c/manifest#826 (2 comments by @aarongustafson, @marcoscaceres)
-
i18n: Multiple manifest links with different hreflang? w3c/manifest#892 (2 comments by @kenchris, @xfq)
-
Bad cross references - remove `data-cite` where possible w3c/manifest#884 (1 comment by @marcoscaceres)
-
Should dir and lang apply to name/description of app shortcuts? w3c/manifest#872 (1 comment by @aarongustafson)
-
-
10 pull requests opened.
-
fix: shortcuts compares wrong scope w3c/manifest#908, by @marcoscaceres.
-
Editorial: Move some members to App Information Note w3c/manifest#900, by @aarongustafson.
-
Drop WebIDL enums w3c/manifest#899, by @christianliebel.
-
Adding in some accessibility-related language w3c/manifest#898, by @aarongustafson.
-
Editorial: shortcut strings are localizable w3c/manifest#897, by @aarongustafson.
-
Shortcuts privacy w3c/manifest#896, by @aarongustafson.
-
Editorial: Cite Image Resource w3c/manifest#895, by @christianliebel.
-
Use HTML machinery to fetch manifests w3c/manifest#894, by @marcoscaceres.
-
editorial: rename+export 'application manifest MIME type' w3c/manifest#893, by @marcoscaceres.
-
chore: remove some bad links w3c/manifest#889, by @marcoscaceres.
-
-
11 pull requests merged.
-
Adding in some accessibility-related language w3c/manifest#898.
-
chore: refactor and export scope terms w3c/manifest#882.
-
Shortcuts privacy w3c/manifest#896.
-
BREAKING CHANGE: Replace "badge" with "monochrome" w3c/manifest#833.
-
chore: mark i18n section as informative w3c/manifest#868.
-
Editorial: shortcut strings are localizable w3c/manifest#897.
-
Editorial: Cite Image Resource w3c/manifest#895.
-
Fix color processing steps w3c/manifest#878.
-
editorial: rename+export 'application manifest MIME type' w3c/manifest#893.
-
Added security consideration advice for out-of-scope UI spoofing. w3c/manifest#748.
-
chore: remove some bad links w3c/manifest#889.
-
-
4 pull requests closed.
-
Add navigation_ui property (fixes #765). w3c/manifest#766.
-
Abstracting selecting an icon. w3c/manifest#710.
-
Obtain manifests only using the JSON MIME type w3c/manifest#858.
-
Clarify off-scope theme color w3c/manifest#879.
-
-
18 pull requests received 211 new comments.
-
Editorial: Move some members to App Information Note w3c/manifest#900 (45 comments by @aarongustafson, @christianliebel, @kenchris, @marcoscaceres, @mgiuca)
-
BREAKING CHANGE: Replace "badge" with "monochrome" w3c/manifest#833 (27 comments by @marcoscaceres, @mgiuca, @NotWoods)
-
Adding in some accessibility-related language w3c/manifest#898 (17 comments by @aarongustafson, @marcoscaceres)
-
Use HTML machinery to fetch manifests w3c/manifest#894 (13 comments by @aarongustafson, @benfrancis, @kenchris, @marcoscaceres)
-
Clarify the definition of "navigation scope", "applied", and off-scope theming w3c/manifest#880 (12 comments by @benfrancis, @marcoscaceres, @mgiuca)
-
Editorial: Cite Image Resource w3c/manifest#895 (11 comments by @aarongustafson, @kenchris, @marcoscaceres, @NotWoods, @rayankans)
-
Drop WebIDL enums w3c/manifest#899 (9 comments by @annevk, @christianliebel, @marcoscaceres, @mgiuca)
-
Editorial: shortcut strings are localizable w3c/manifest#897 (7 comments by @aarongustafson, @marcoscaceres)
-
Processing the manifest is no longer a function of document URL w3c/manifest#834 (4 comments by @aarongustafson, @marcoscaceres, @mgiuca)
-
Require document to be in scope to be styled by the manifest w3c/manifest#791 (3 comments by @marcoscaceres, @mgiuca)
-
w3c/manifest#748 (3 comments by @marcoscaceres)
-
Add navigation_ui property (fixes #765). w3c/manifest#766 (2 comments by @marcoscaceres, @mounirlamouri)
-
w3c/manifest#710 (1 comment by @marcoscaceres)
-
editorial: rename+export 'application manifest MIME type' w3c/manifest#893 (1 comment by @marcoscaceres)
-
w3c/ServiceWorker
-
3 issues opened.
-
Error handling inconsistent with other Workers w3c/ServiceWorker#1519, by @scottpledger.
-
register() lacks same origin check w3c/ServiceWorker#1518, by @annevk.
-
Handle Fetch "process response" callback appears to run on wrong event-loop w3c/ServiceWorker#1517, by @gterzian.
-
-
6 issues received 19 new comments.
-
Error handling inconsistent with other Workers w3c/ServiceWorker#1519 (6 comments by @jakearchibald, @wanderview)
-
register() lacks same origin check w3c/ServiceWorker#1518 (3 comments by @annevk, @mkruisselbrink, @mozfreddyb)
-
-
1 pull request opened.
-
Introduce Cross-Origin Embedder Policy w3c/ServiceWorker#1516, by @yutakahirano.
-
-
2 pull requests received 16 new comments.
-
Introduce Cross-Origin Embedder Policy w3c/ServiceWorker#1516 (14 comments by @annevk, @yutakahirano)
-
w3c/gamepad
-
1 issue opened.
-
TPAC planning and specification status report w3c/gamepad#137, by @LJWatson.
-
-
2 issues closed.
-
button[16] not documented in the list of buttons. w3c/gamepad#130.
-
xbox gamepad mapped differently in firefox and chrome on Linux w3c/gamepad#133.
-
-
7 issues received 15 new comments.
-
"STANDARD GAMEPAD" should be defined in a separate attribute w3c/gamepad#129 (2 comments by @Grovkillen, @nondebug)
-
xbox gamepad mapped differently in firefox and chrome on Linux w3c/gamepad#133 (1 comment by @qlambert-pro)
-
3 pull requests opened.
-
Editorial: add a Model section w3c/gamepad#136, by @nondebug.
-
Add buttons[16] to button/axis location table w3c/gamepad#135, by @nondebug.
-
Rewrite gamepad spec using algorithms w3c/gamepad#134, by @nondebug.
-
-
1 pull request merged.
-
Add buttons[16] to button/axis location table w3c/gamepad#135.
-
-
2 pull requests received 13 new comments.
w3c/pointerlock
-
1 issue opened.
-
TPAC planning and specification status report w3c/pointerlock#64, by @LJWatson.
-
-
1 issue closed.
-
No matching definition found for `triggered by user activation` w3c/pointerlock#53.
-
-
2 issues received 4 new comments.
-
w3c/pointerlock#42 (1 comment by @tim-janik)
-
1 pull request opened.
-
Editorial: Fix the broken reference to user activation. w3c/pointerlock#65, by @mustaqahmed.
-
-
2 pull requests merged.
-
Add Mustaq as editor w3c/pointerlock#63.
-
Editorial: Fix the broken reference to user activation. w3c/pointerlock#65.
-
-
2 pull requests received 7 new comments.
-
Editorial: Fix the broken reference to user activation. w3c/pointerlock#65 (3 comments by @marcoscaceres, @NavidZ)
w3c/webappswg
-
1 issue closed.
-
clipboard API failing to auto publish w3c/webappswg#34.
-
-
2 issues received 7 new comments.
-
Planning for a virtual TPAC meeting w3c/webappswg#35 (6 comments by @inexorabletash, @LJWatson, @marcoscaceres)
-
w3c/uievents-key
-
1 issue opened.
-
TPAC planning and specification status report w3c/uievents-key#53, by @LJWatson.
-
w3c/uievents-code
-
1 issue opened.
-
TPAC planning and specification status report w3c/uievents-code#28, by @LJWatson.
-
w3c/image-resource
-
4 issues opened.
-
TPAC planning and specification status report w3c/image-resource#32, by @LJWatson.
-
Rename "master" -> "main" w3c/image-resource#31, by @aarongustafson.
-
"master" -> "main w3c/image-resource#30, by @aarongustafson.
-
Add image-resource to MDN data w3c/image-resource#29, by @aarongustafson.
-
-
3 issues closed.
-
"master" -> "main w3c/image-resource#30.
-
Which CSP policy should apply to ImageResource w3c/image-resource#25.
-
Add alternative text member w3c/image-resource#7.
-
-
5 issues received 12 new comments.
-
Add alternative text member w3c/image-resource#7 (7 comments by @aarongustafson, @joanmarie, @johnfoliot)
-
Which CSP policy should apply to ImageResource w3c/image-resource#25 (2 comments by @danyao, @rayankans)
-
-
1 pull request opened.
-
Accessible description w3c/image-resource#28, by @aarongustafson.
-
-
1 pull request received 15 new comments.
-
Accessible description w3c/image-resource#28 (15 comments by @aarongustafson, @LJWatson, @marcoscaceres)
-
w3c/web-share
-
2 issues opened.
-
TPAC planning and specification status report w3c/web-share#162, by @LJWatson.
-
Explain why canShare exists at definition. w3c/web-share#159, by @scheib.
-
-
1 issue closed.
-
Should calling share() "consume" the activation? w3c/web-share#136.
-
-
2 issues received 6 new comments.
-
2 pull requests opened.
-
chore: run auto-pub when merging on master w3c/web-share#161, by @marcoscaceres.
-
chore: enable autopublish w3c/web-share#160, by @marcoscaceres.
-
-
3 pull requests merged.
-
BREAKING CHANGE: make share() consume user activation w3c/web-share#137.
-
chore: run auto-pub when merging on master w3c/web-share#161.
-
chore: enable autopublish w3c/web-share#160.
-
-
1 pull request received 3 new comments.
-
BREAKING CHANGE: make share() consume user activation w3c/web-share#137 (3 comments by @marcoscaceres)
-
w3c/screen-orientation
-
1 issue opened.
-
TPAC planning and specification status report w3c/screen-orientation#199, by @LJWatson.
-
w3c/push-api
-
1 issue opened.
-
TPAC planning and specification status report w3c/push-api#326, by @LJWatson.
-
w3c/FileAPI
-
1 issue opened.
-
TPAC planning and specification status report w3c/FileAPI#156, by @LJWatson.
-
-
2 issues received 8 new comments.
-
w3c/FileAPI#119 (1 comment by @bakulf)
-
1 pull request opened.
-
Fix typo in read operation algorithm description w3c/FileAPI#155, by @customcommander.
-
-
1 pull request merged.
-
Fix typo in read operation algorithm description w3c/FileAPI#155.
-
-
1 pull request received 1 new comment.
w3c/badging
-
1 issue opened.
-
Feature: Get current badge value w3c/badging#73, by @kristof12345.
-
-
1 issue closed.
-
Remove dependencies section w3c/badging#63.
-
-
2 issues received 2 new comments.
TR publications
-
7 documents published.
-
HTML Accessibility API Mappings 1.0 published as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
Web App Manifest published as a Working Draft. History of Web App Manifest
-
ARIA in HTML published as a Working Draft. History of ARIA in HTML
-
Image Resource published 3 times as a Working Draft. History of Image Resource
-
Image Resource published as a First Public Working Draft. History of Image Resource
-
Participants
-
3 participants joined.
-
Michael Jackson (Microsoft Corporation) joined.
-
John Jansen (Microsoft Corporation) joined.
-
Ben Francis (W3C Invited Experts) joined.
-
-
2 participants left.
-
Greg Whitworth (Salesforce) left.
-
Kagami Rosylight (Mozilla Foundation) left.
-
GitHub
w3c/gamepad
-
1 issue opened.
-
xbox gamepad mapped differently in firefox and chrome on Linux w3c/gamepad#133, by @qlambert-pro.
-
-
9 issues received 12 new comments.
-
xbox gamepad mapped differently in firefox and chrome on Linux w3c/gamepad#133 (1 comment by @mrmcpowned)
-
w3c/gamepad#46 (1 comment by @mrmcpowned)
-
"STANDARD GAMEPAD" should be defined in a separate attribute w3c/gamepad#129 (1 comment by @mrmcpowned)
-
w3c/gamepad#74 (1 comment by @samuelweiler)
-
1 pull request received 1 new comment.
-
w3c/gamepad#15 (1 comment by @mrmcpowned)
-
w3c/manifest
-
13 issues opened.
-
Should manifest be HTTPS only? w3c/manifest#887, by @aarongustafson.
-
shortcuts compares wrong scope w3c/manifest#885, by @marcoscaceres.
-
Bad cross references - remove `data-cite` where possible w3c/manifest#884, by @marcoscaceres.
-
[Chore] Manifest fails to validate due to Specref issues w3c/manifest#881, by @mgiuca.
-
Related applications members (at risk?) w3c/manifest#877, by @marcoscaceres.
-
Remove store metadata into own spec or note? w3c/manifest#876, by @marcoscaceres.
-
Should dir and lang apply to name/description of app shortcuts? w3c/manifest#872, by @xfq.
-
Check wide review requirements and contact appropriate groups w3c/manifest#870, by @marcoscaceres.
-
Shortcuts: Dynamic update or JS access to URLs w3c/manifest#867, by @garykac.
-
Add "payment" dictionary for payment app specific properties w3c/manifest#866, by @sahel-sh.
-
Preparing for Candidate Recommendation w3c/manifest#865, by @marcoscaceres.
-
Bring back "serviceworker" member w3c/manifest#864, by @mgiuca.
-
Provide guidance to UAs on appropriate names for "platform" members w3c/manifest#862, by @mgiuca.
-
-
15 issues closed.
-
[Chore] Manifest fails to validate due to Specref issues w3c/manifest#881.
-
Some mechanism to maybe define a feature policy w3c/manifest#798.
-
Update MDN Browser Compat Data w3c/manifest#859.
-
Parse JSON from bytes w3c/manifest#619.
-
New Boolean members to control interaction with related applications w3c/manifest#658.
-
Allow for multiple scopes w3c/manifest#449.
-
Should the scope terminate by "/"? w3c/manifest#554.
-
unbounded check in navigation should check origin w3c/manifest#549.
-
Support window preferred/initial (minimal?) sizes w3c/manifest#436.
-
Shortcuts: Dynamic update or JS access to URLs w3c/manifest#867.
-
Please add caption property to screenshots w3c/manifest#773.
-
Space-separated sizes in ImageResource? w3c/manifest#807.
-
Representing Spatial Icons for WebApps w3c/manifest#763.
-
Add a `color_scheme` member to `ImageResource` w3c/manifest#758.
-
Which CSP policy should apply to images inside an app manifest? w3c/manifest#851.
-
-
43 issues received 139 new comments.
-
Preparing for Candidate Recommendation w3c/manifest#865 (23 comments by @aarongustafson, @anssiko, @christianliebel, @kenchris, @marcoscaceres, @mgiuca)
-
Bring back "serviceworker" member w3c/manifest#864 (12 comments by @marcoscaceres, @mgiuca, @rsolomakhin, @sahel-sh)
-
Remove store metadata into own spec or note? w3c/manifest#876 (11 comments by @aarongustafson, @jgw96, @kenchris, @marcoscaceres, @mgiuca, @NotWoods)
-
Should dir and lang apply to name/description of app shortcuts? w3c/manifest#872 (9 comments by @marcoscaceres, @mgiuca, @xfq)
-
Add manifest option for PWAs to be registered as scheme/protocol handlers w3c/manifest#846 (4 comments by @emattias, @fabiorocha, @marcoscaceres)
-
Provide guidance to UAs on appropriate names for "platform" members w3c/manifest#862 (4 comments by @aarongustafson, @kenchris, @mgiuca)
-
Spec what it means to support "manifest" via <link>'s relList w3c/manifest#826 (2 comments by @aarongustafson)
-
Some mechanism to maybe define a feature policy w3c/manifest#798 (2 comments by @aarongustafson, @marcoscaceres)
-
Which CSP policy should apply to images inside an app manifest? w3c/manifest#851 (2 comments by @aarongustafson, @danyao)
-
w3c/manifest#666 (1 comment by @aarongustafson)
-
w3c/manifest#597 (1 comment by @mgiuca)
-
w3c/manifest#764 (1 comment by @mgiuca)
-
w3c/manifest#622 (1 comment by @marcoscaceres)
-
w3c/manifest#619 (1 comment by @marcoscaceres)
-
w3c/manifest#658 (1 comment by @mgiuca)
-
w3c/manifest#586 (1 comment by @marcoscaceres)
-
w3c/manifest#449 (1 comment by @mgiuca)
-
w3c/manifest#551 (1 comment by @marcoscaceres)
-
w3c/manifest#549 (1 comment by @marcoscaceres)
-
w3c/manifest#436 (1 comment by @marcoscaceres)
-
w3c/manifest#380 (1 comment by @kenchris)
-
w3c/manifest#763 (1 comment by @aarongustafson)
-
w3c/manifest#758 (1 comment by @aarongustafson)
-
-
13 pull requests opened.
-
editorial: shortcut compares wrong scope w3c/manifest#886, by @marcoscaceres.
-
chore: fix some xrefs w3c/manifest#883, by @marcoscaceres.
-
chore: refactor and export scope terms w3c/manifest#882, by @marcoscaceres.
-
Clarify the definition of "navigation scope", "applied", and off-scope theming w3c/manifest#880, by @mgiuca.
-
Clarify off-scope theme color w3c/manifest#879, by @christianliebel.
-
Fix color processing steps w3c/manifest#878, by @christianliebel.
-
Editorial: ECMA-402 CanonicalizeLanguageTag -> CanonicalizeUnicodeLocaleId w3c/manifest#875, by @marcoscaceres.
-
chore: remove implementation status, use MDN data instead w3c/manifest#874, by @marcoscaceres.
-
chore: switch to respec-autopublish w3c/manifest#873, by @marcoscaceres.
-
Chore: Update links to the WG w3c/manifest#871, by @xfq.
-
chore: fix index section issue w3c/manifest#869, by @marcoscaceres.
-
chore: mark i18n section as informative w3c/manifest#868, by @marcoscaceres.
-
Add protocol handlers to the explainer and spec w3c/manifest#863, by @fabiorocha.
-
-
6 pull requests merged.
-
chore: fix some xrefs w3c/manifest#883.
-
chore: remove implementation status, use MDN data instead w3c/manifest#874.
-
chore: switch to respec-autopublish w3c/manifest#873.
-
chore: fix index section issue w3c/manifest#869.
-
Chore: Update links to the WG w3c/manifest#871.
-
-
1 pull request closed.
-
editorial: shortcut compares wrong scope w3c/manifest#886.
-
-
10 pull requests received 100 new comments.
-
Fix color processing steps w3c/manifest#878 (22 comments by @christianliebel, @kenchris, @marcoscaceres, @sidvishnoi, @tabatkins)
-
BREAKING CHANGE: Replace "badge" with "monochrome" w3c/manifest#833 (13 comments by @kenchris, @leolux, @NotWoods)
-
Clarify the definition of "navigation scope", "applied", and off-scope theming w3c/manifest#880 (11 comments by @kenchris, @marcoscaceres, @mgiuca)
-
Add protocol handlers to the explainer and spec w3c/manifest#863 (4 comments by @dmurph, @fabiorocha, @reillyeon)
-
Processing the manifest is no longer a function of document URL w3c/manifest#834 (3 comments by @hober, @mgiuca)
-
w3c/pointerlock
-
1 pull request opened.
-
Add Mustaq as editor w3c/pointerlock#63, by @NavidZ.
-
-
1 pull request received 2 new comments.
w3c/ServiceWorker
-
3 issues opened.
-
Service worker client URL discrepancy w3c/ServiceWorker#1515, by @JackieNiebling.
-
Service Workers with Self Signed Certificates over SSL w3c/ServiceWorker#1514, by @diipak-bisht.
-
Expose the Fetch Metadata Request Headers w3c/ServiceWorker#1513, by @samdenty.
-
-
3 issues received 9 new comments.
-
Service worker client URL discrepancy w3c/ServiceWorker#1515 (4 comments by @asutherland, @JackieNiebling, @wanderview)
-
w3c/ServiceWorker#1265 (1 comment by @wanderview)
-
w3c/badging
-
3 pull requests opened.
-
editorial: fixup xrefs w3c/badging#72, by @marcoscaceres.
-
chore: WebAppsWG integration w3c/badging#71, by @marcoscaceres.
-
chore: migrate to WebAppsWG w3c/badging#70, by @marcoscaceres.
-
-
3 pull requests merged.
-
chore: WebAppsWG integration w3c/badging#71.
-
editorial: fixup xrefs w3c/badging#72.
-
chore: migrate to WebAppsWG w3c/badging#70.
-
-
2 pull requests received 3 new comments.
w3c/FileAPI
-
1 issue opened.
-
Blob URL store partitioning w3c/FileAPI#153, by @annevk.
-
-
2 issues received 4 new comments.
-
1 pull request opened.
-
Rewrite a lot of the internals of Blobs to make reading more explicit. w3c/FileAPI#154, by @mkruisselbrink.
-
-
1 pull request received 40 new comments.
-
Rewrite a lot of the internals of Blobs to make reading more explicit. w3c/FileAPI#154 (40 comments by @annevk, @inexorabletash, @mkruisselbrink, @pwnall)
-
w3c/web-share
-
3 issues opened.
-
Web Share API can be triggered from iframe sandbox w3c/web-share#155, by @shhnjk.
-
Note about choice of USVString imprecise w3c/web-share#152, by @aphillips.
-
Feature Policy integration w3c/web-share#151, by @ewilligers.
-
-
2 issues closed.
-
Note about choice of USVString imprecise w3c/web-share#152.
-
Complete privacy/security self-review w3c/web-share#149.
-
-
4 issues received 14 new comments.
-
4 pull requests opened.
-
chore: export 'share target' w3c/web-share#158, by @marcoscaceres.
-
chore: tidy w3c/web-share#157, by @marcoscaceres.
-
chore: use ReSpec IDL syntax w3c/web-share#154, by @marcoscaceres.
-
chore: Clarify reason for choosing USVString w3c/web-share#153, by @ewilligers.
-
-
6 pull requests merged.
-
chore: tidy w3c/web-share#157.
-
chore: export 'share target' w3c/web-share#158.
-
chore: Clarify reason for choosing USVString w3c/web-share#153.
-
chore: use ReSpec IDL syntax w3c/web-share#154.
-
Add the ability to share files w3c/web-share#133.
-
Initial take on Security/Privacy self-review w3c/web-share#150.
-
-
4 pull requests received 16 new comments.
-
Initial take on Security/Privacy self-review w3c/web-share#150 (6 comments by @inexorabletash, @marcoscaceres)
-
BREAKING CHANGE: make share() consume user activation w3c/web-share#137 (2 comments by @marcoscaceres)
-
w3c/uievents
-
1 issue opened.
-
Redefine when `keypress` event should be fired w3c/uievents#266, by @masayuki-nakano.
-
-
3 issues received 6 new comments.
-
Redefine when `keypress` event should be fired w3c/uievents#266 (2 comments by @garykac, @masayuki-nakano)
-
w3c/image-resource
-
5 issues opened.
-
Representing Spatial Icons for WebApps w3c/image-resource#27, by @aarongustafson.
-
Add a `color_scheme` member w3c/image-resource#26, by @aarongustafson.
-
Which CSP policy should apply to ImageResource w3c/image-resource#25, by @danyao.
-
Enable auto-publish on TR w3c/image-resource#23, by @marcoscaceres.
-
Add missing privacy and security section w3c/image-resource#21, by @marcoscaceres.
-
-
3 issues closed.
-
Add missing privacy and security section w3c/image-resource#21.
-
Enable auto-publish on TR w3c/image-resource#23.
-
CFC for to publish FPWD w3c/image-resource#17.
-
-
4 issues received 9 new comments.
-
Are we ready to finalize this extraction and start a PR merging into the manifest? w3c/image-resource#10 (3 comments by @aarongustafson, @marcoscaceres)
-
2 pull requests opened.
-
chore(.github/action.yml): enable autopublish w3c/image-resource#24, by @marcoscaceres.
-
Add a Privacy & Security section w3c/image-resource#22, by @rayankans.
-
-
3 pull requests merged.
-
Add a Privacy & Security section w3c/image-resource#22.
-
A few edits per Jake’s feedback w3c/image-resource#20.
-
chore(.github/action.yml): enable autopublish w3c/image-resource#24.
-
-
2 pull requests received 17 new comments.
-
Add a Privacy & Security section w3c/image-resource#22 (10 comments by @aarongustafson, @marcoscaceres, @rayankans)
-
chore(.github/action.yml): enable autopublish w3c/image-resource#24 (7 comments by @marcoscaceres, @sidvishnoi)
-
w3c/IndexedDB
-
1 issue opened.
-
Add a `closed` property on the db w3c/IndexedDB#333, by @Jack-Works.
-
-
2 issues received 3 new comments.
-
3 pull requests opened.
-
Editorial: Use Bikeshed's algorithm and var more better w3c/IndexedDB#336, by @inexorabletash.
-
Editorial: Use WebIDL's new definition conventions for method/etc steps w3c/IndexedDB#335, by @inexorabletash.
-
Define Indexed DB as a storage endpoint, use hooks w3c/IndexedDB#334, by @inexorabletash.
-
-
2 pull requests merged.
-
Editorial: Use Bikeshed's algorithm and var more better w3c/IndexedDB#336.
-
Editorial: Use WebIDL's new definition conventions for method/etc steps w3c/IndexedDB#335.
-
-
3 pull requests received 26 new comments.
-
Editorial: Use WebIDL's new definition conventions for method/etc steps w3c/IndexedDB#335 (12 comments by @domenic, @inexorabletash)
-
Define Indexed DB as a storage endpoint, use hooks w3c/IndexedDB#334 (8 comments by @annevk, @asutherland, @inexorabletash, @mkruisselbrink)
-
Editorial: Use Bikeshed's algorithm and var more better w3c/IndexedDB#336 (6 comments by @domenic, @inexorabletash)
-
w3c/web-locks
-
1 pull request opened.
-
Modernize spec text: w3c/web-locks#62, by @inexorabletash.
-
-
1 pull request merged.
-
Modernize spec text: w3c/web-locks#62.
-
-
1 pull request received 3 new comments.
w3c/contact-picker
-
1 issue opened.
-
[QUESTION] Why is the API not working in Vue.js w3c/contact-picker#32, by @tafelnl.
-
-
1 issue closed.
-
[QUESTION] Why is the API not working in Vue.js w3c/contact-picker#32.
-
-
1 issue received 3 new comments.
-
[QUESTION] Why is the API not working in Vue.js w3c/contact-picker#32 (3 comments by @rayankans, @tafelnl, @tomayac)
-
w3c/webappswg
-
4 issues opened.
-
Add @saschanaz to WebAppWG members w3c/webappswg#36, by @marcoscaceres.
-
Planning for a virtual TPAC meeting w3c/webappswg#35, by @marcoscaceres.
-
clipboard API failing to auto publish w3c/webappswg#34, by @marcoscaceres.
-
execCommand archive link doesn't work w3c/webappswg#33, by @jdm.
-
-
6 issues closed.
-
Add @saschanaz to WebAppWG members w3c/webappswg#36.
-
Superseded Selectors API w3c/webappswg#21.
-
Check specs have an internationalization section w3c/webappswg#25.
-
Check specs have an accessibility section w3c/webappswg#15.
-
Publish ImageResource spec w3c/webappswg#30.
-
execCommand archive link doesn't work w3c/webappswg#33.
-
-
10 issues received 15 new comments.
-
Add @saschanaz to WebAppWG members w3c/webappswg#36 (4 comments by @marcoscaceres, @saschanaz, @siusin)
-
w3c/webappswg#2 (1 comment by @marcoscaceres)
-
w3c/push-api
-
1 issue opened.
-
pushsubscriptionchange event doesn't have oldSubscription in it. w3c/push-api#325, by @novaknole.
-
-
2 issues received 9 new comments.
-
pushsubscriptionchange event doesn't have oldSubscription in it. w3c/push-api#325 (6 comments by @linabutler, @marcoscaceres, @novaknole)
-
TR publications
-
1 document published.
-
The Screen Orientation API published as a Working Draft. History of The Screen Orientation API
-
Participants
-
1 participant joined.
-
Dima Voytenko (Google LLC) joined.
-
GitHub
w3c/push-api
-
1 issue opened.
-
Add accessibility section w3c/push-api#324, by @LJWatson.
-
-
1 issue received 8 new comments.
w3c/webappswg
-
1 issue opened.
-
api3 w3c/webappswg#32, by @ftservice.
-
-
1 issue closed.
-
api3 w3c/webappswg#32.
-
-
5 issues received 14 new comments.
w3c/web-share
-
4 issues opened.
-
Complete privacy/security self-review w3c/web-share#149, by @LJWatson.
-
Complete i18n self-review w3c/web-share#148, by @LJWatson.
-
Add accessibility section w3c/web-share#145, by @LJWatson.
-
Navigator Share w3c/web-share#144, by @yasir-rafiq.
-
-
2 issues closed.
-
Add accessibility section w3c/web-share#145.
-
Navigator Share w3c/web-share#144.
-
-
6 issues received 14 new comments.
-
3 pull requests opened.
-
Initial take on Security/Privacy self-review w3c/web-share#150, by @inexorabletash.
-
chore: 'present' xref does not exist w3c/web-share#147, by @marcoscaceres.
-
Accessibility considerations w3c/web-share#146, by @ewilligers.
-
-
3 pull requests merged.
-
Accessibility considerations w3c/web-share#146.
-
chore: 'present' xref does not exist w3c/web-share#147.
-
editorial: Link `this` to Web IDL w3c/web-share#140.
-
-
2 pull requests received 21 new comments.
-
Initial take on Security/Privacy self-review w3c/web-share#150 (20 comments by @ewilligers, @inexorabletash, @marcoscaceres, @mgiuca)
-
w3c/IndexedDB
-
3 issues opened.
-
Initial DB version (when creating db) is 1 in browsers but 0 in spec w3c/IndexedDB#332, by @gouravkhator.
-
Make "global scope" references more concrete w3c/IndexedDB#329, by @inexorabletash.
-
Add accessibility section w3c/IndexedDB#327, by @LJWatson.
-
-
2 issues closed.
-
Initial DB version (when creating db) is 1 in browsers but 0 in spec w3c/IndexedDB#332.
-
Make "global scope" references more concrete w3c/IndexedDB#329.
-
-
4 issues received 11 new comments.
-
Initial DB version (when creating db) is 1 in browsers but 0 in spec w3c/IndexedDB#332 (1 comment by @inexorabletash)
-
w3c/IndexedDB#34 (1 comment by @Jack-Works)
-
3 pull requests opened.
-
Initial sketch of manual commit flag for transactions w3c/IndexedDB#331, by @inexorabletash.
-
Editorial: Use settings object definition. w3c/IndexedDB#330, by @inexorabletash.
-
Add accessibility section draft. w3c/IndexedDB#328, by @inexorabletash.
-
-
2 pull requests merged.
-
Editorial: Use settings object definition. w3c/IndexedDB#330.
-
Editorial: Use WebIDL terms |this| and |the given value| w3c/IndexedDB#325.
-
-
1 pull request closed.
-
Allow BigInts as IndexedDB keys w3c/IndexedDB#231.
-
-
3 pull requests received 9 new comments.
-
Editorial: Use WebIDL terms |this| and |the given value| w3c/IndexedDB#325 (3 comments by @inexorabletash, @mkruisselbrink)
-
Editorial: Use settings object definition. w3c/IndexedDB#330 (2 comments by @inexorabletash, @mkruisselbrink)
w3c/image-resource
-
2 pull requests opened.
-
A few edits per Jake’s feedback w3c/image-resource#20, by @aarongustafson.
-
Link to the `sizes` parsing steps. w3c/image-resource#19, by @rayankans.
-
-
1 pull request merged.
-
Link to the `sizes` parsing steps. w3c/image-resource#19.
-
-
2 pull requests received 18 new comments.
-
Prepare for FPWD w3c/image-resource#13 (14 comments by @aarongustafson, @jakearchibald, @marcoscaceres, @rayankans)
-
w3c/manifest
-
2 issues opened.
-
Add accessibility section w3c/manifest#860, by @LJWatson.
-
Update MDN Browser Compat Data w3c/manifest#859, by @aarongustafson.
-
-
15 issues closed.
-
Add internal slot for "install is showing". w3c/manifest#761.
-
service worker sections: mixed up inputs and outputs, some suggestions w3c/manifest#706.
-
The new explainer ties the manifest with the concept of install ability w3c/manifest#536.
-
Need to specify client of image objects when fetching w3c/manifest#465.
-
Define how the manifest is fetched w3c/manifest#481.
-
Use case for appuninstall event w3c/manifest#636.
-
Broken fragments in spec w3c/manifest#735.
-
Navigation during installation w3c/manifest#762.
-
make BeforeInstallPrompt optional w3c/manifest#796.
-
how to handle cancel button for pwa prompt w3c/manifest#855.
-
Allowing only site-triggered install prompt w3c/manifest#627.
-
-
29 issues received 73 new comments.
-
Why does obtaining not check a MIME type? w3c/manifest#821 (15 comments by @benfrancis, @dmurph, @dominickng, @marcoscaceres, @mgiuca, @mikewest)
-
Allow installed PWA to run on OS login w3c/manifest#845 (5 comments by @aarongustafson, @marcoscaceres, @reillyeon)
-
More precise control over app window features w3c/manifest#856 (3 comments by @alancutter, @marcoscaceres)
-
Which CSP policy should apply to images inside an app manifest? w3c/manifest#851 (2 comments by @danyao, @hofman-stripe)
-
w3c/manifest#726 (1 comment by @photopea)
-
w3c/manifest#668 (1 comment by @benfrancis)
-
w3c/manifest#761 (1 comment by @marcoscaceres)
-
w3c/manifest#706 (1 comment by @marcoscaceres)
-
w3c/manifest#536 (1 comment by @marcoscaceres)
-
w3c/manifest#465 (1 comment by @marcoscaceres)
-
w3c/manifest#481 (1 comment by @marcoscaceres)
-
w3c/manifest#514 (1 comment by @marcoscaceres)
-
w3c/manifest#735 (1 comment by @marcoscaceres)
-
w3c/manifest#762 (1 comment by @marcoscaceres)
-
Spec what it means to support "manifest" via <link>'s relList w3c/manifest#826 (1 comment by @marcoscaceres)
-
w3c/manifest#627 (1 comment by @mgiuca)
-
-
3 pull requests merged.
-
Remove beforeinstallprompt and appinstalled events. w3c/manifest#836.
-
Remove redundant dependencies section w3c/manifest#857.
-
chore: export some terms needed by Badging w3c/manifest#823.
-
-
2 pull requests closed.
-
Separate BeforeInstallPrompt from automatic prompt w3c/manifest#692.
-
Moves BeforeInstallPrompt and related text to a non-normative annex. w3c/manifest#843.
-
-
2 pull requests received 11 new comments.
-
Obtain manifests only using the JSON MIME type w3c/manifest#858 (6 comments by @dominickng, @marcoscaceres, @mgiuca)
-
Remove beforeinstallprompt and appinstalled events. w3c/manifest#836 (5 comments by @dominickng, @marcoscaceres, @mgiuca, @othermaciej)
-
w3c/ServiceWorker
-
3 issues opened.
-
consider allowing a non-scope identifier for registrations w3c/ServiceWorker#1512, by @wanderview.
-
"uninstall" event in the worker global scope w3c/ServiceWorker#1511, by @ai-zubair.
-
safari fetches from memory cache instead of Service worker w3c/ServiceWorker#1510, by @novaknole.
-
-
2 issues closed.
-
"uninstall" event in the worker global scope w3c/ServiceWorker#1511.
-
safari fetches from memory cache instead of Service worker w3c/ServiceWorker#1510.
-
-
9 issues received 37 new comments.
-
Service workers allow for more responses to be executed as script w3c/ServiceWorker#1509 (21 comments by @anforowicz, @annevk, @arturjanc, @csreis, @jakearchibald, @mikewest)
-
consider allowing a non-scope identifier for registrations w3c/ServiceWorker#1512 (6 comments by @asutherland, @jakearchibald, @wanderview)
-
safari fetches from memory cache instead of Service worker w3c/ServiceWorker#1510 (4 comments by @jakearchibald, @novaknole, @wanderview)
-
w3c/ServiceWorker#1282 (1 comment by @anthumchris)
-
w3c/ServiceWorker#1230 (1 comment by @annevk)
-
w3c/ServiceWorker#1224 (1 comment by @gterzian)
-
w3c/ServiceWorker#745 (1 comment by @hubyhuby)
-
w3c/ServiceWorker#1247 (1 comment by @daffinm)
-
w3c/ServiceWorker#1222 (1 comment by @daffinm)
-
-
1 pull request merged.
-
Update agent and realm allocation w3c/ServiceWorker#1508.
-
-
1 pull request received 3 new comments.
w3c/contact-picker
-
1 issue closed.
-
We REALLY need this! w3c/contact-picker#20.
-
-
1 issue received 1 new comment.
w3c/screen-orientation
-
2 issues opened.
-
Apply an orientation lock rejects its own newly created promise w3c/screen-orientation#198, by @smacleod.
-
Add accessibility section w3c/screen-orientation#196, by @LJWatson.
-
-
2 pull requests opened.
-
chore: use GitHub action to validate and auto-publish w3c/screen-orientation#197, by @sidvishnoi.
-
chore: use GitHub action to validate and auto-publish w3c/screen-orientation#195, by @sidvishnoi.
-
-
1 pull request merged.
-
chore: use GitHub action to validate and auto-publish w3c/screen-orientation#197.
-
-
1 pull request closed.
-
chore: use GitHub action to validate and auto-publish w3c/screen-orientation#195.
-
-
2 pull requests received 12 new comments.
-
chore: use GitHub action to validate and auto-publish w3c/screen-orientation#195 (11 comments by @marcoscaceres, @sidvishnoi, @siusin)
-
chore: use GitHub action to validate and auto-publish w3c/screen-orientation#197 (1 comment by @sidvishnoi)
-
w3c/uievents
-
2 issues opened.
-
no way to distinguish printable key values from non-printable w3c/uievents#264, by @Yaffle.
-
Add an accessibility section w3c/uievents#263, by @LJWatson.
-
-
1 issue received 1 new comment.
-
Should Key event be fired for [Previous] and [Next] key on Virtual Keyboard? w3c/uievents#253 (1 comment by @dtapuska)
-
-
1 pull request closed.
-
set default for optional dictionary w3c/uievents#239.
-
-
1 pull request received 1 new comment.
w3c/FileAPI
-
3 issues opened.
-
Add accessibility section w3c/FileAPI#152, by @LJWatson.
-
Blob URL store entries are not removed w3c/FileAPI#149, by @annevk.
-
-
1 issue closed.
-
1 issue reopened.
-
Why are Blob() and File() constructors at Chromium 81 throwing RangeError? w3c/FileAPI#147, by @guest271314.
-
-
3 issues received 8 new comments.
-
Consider substituting optional BlobPart or sequence<BlobPart> for optional sequence<BlobPart> blobParts at constructor w3c/FileAPI#150 (5 comments by @domenic, @guest271314)
-
Why are Blob() and File() constructors at Chromium 81 throwing RangeError? w3c/FileAPI#147 (1 comment by @guest271314)
-
-
1 pull request opened.
-
Use valid UUID in blob: URL example w3c/FileAPI#151, by @ctavan.
-
-
1 pull request merged.
-
Use valid UUID in blob: URL example w3c/FileAPI#151.
-
-
2 pull requests received 5 new comments.
w3c/uievents-code
-
1 issue opened.
-
Add accessibility section w3c/uievents-code#27, by @LJWatson.
-
w3c/uievents-key
-
1 issue opened.
-
Add accessibility section w3c/uievents-key#52, by @LJWatson.
-
w3c/pointerlock
-
1 issue opened.
-
Add accessibility section w3c/pointerlock#62, by @LJWatson.
-
w3c/gamepad
-
1 issue opened.
-
Add accessibility section w3c/gamepad#132, by @LJWatson.
-
w3c/badging
-
1 pull request opened.
-
Update explainer.md w3c/badging#69, by @DavidMulder0.
-
-
1 pull request merged.
-
Update explainer.md w3c/badging#69.
-
-
1 pull request received 1 new comment.
w3c/manifest-app-info
-
1 issue received 1 new comment.
-
Add change log support to the web app manifest w3c/manifest-app-info#1 (1 comment by @marcoscaceres)
-
TR publications
-
5 documents published.
-
The Screen Orientation API published as a Working Draft. History of The Screen Orientation API
-
Web App Manifest published 4 times as a Working Draft. History of Web App Manifest
-
Participants
-
3 participants joined.
-
Wenson Hsieh (Apple Inc.) joined.
-
Bo Cupp (Microsoft Corporation) joined.
-
Alessandro Curzi (Microsoft Corporation) joined.
-
-
2 participants left.
-
Gerard Cohen (Wells Fargo Bank N.A.) left.
-
Janice Shiu (Mozilla Foundation) left.
-
-
1 organization left.
-
Wells Fargo Bank N.A. left.
-
GitHub
w3c/ServiceWorker
-
2 issues opened.
-
Service workers allow for more responses to be executed as script w3c/ServiceWorker#1509, by @annevk.
-
Check if <script>'s fetch request has an integrity attribute w3c/ServiceWorker#1507, by @guanzo.
-
-
1 issue closed.
-
Check if <script>'s fetch request has an integrity attribute w3c/ServiceWorker#1507.
-
-
5 issues received 8 new comments.
-
Service workers allow for more responses to be executed as script w3c/ServiceWorker#1509 (3 comments by @annevk, @jakearchibald)
-
w3c/ServiceWorker#1246 (1 comment by @huangjihua)
-
Check if <script>'s fetch request has an integrity attribute w3c/ServiceWorker#1507 (1 comment by @wanderview)
-
-
1 pull request opened.
-
Update agent and realm allocation w3c/ServiceWorker#1508, by @domenic.
-
-
2 pull requests received 15 new comments.
-
Define Purge Service Worker Registrations w3c/ServiceWorker#1506 (9 comments by @annevk, @jakearchibald, @jungkees)
-
Update agent and realm allocation w3c/ServiceWorker#1508 (6 comments by @annevk, @domenic, @jakearchibald)
-
w3c/manifest
-
4 issues opened.
-
More precise control over app window features w3c/manifest#856, by @mgiuca.
-
how to handle cancel button for pwa prompt w3c/manifest#855, by @novaknole.
-
Use the newly defined ImageResource w3c/manifest#854, by @rayankans.
-
Which CSP policy should apply to images inside an app manifest? w3c/manifest#851, by @danyao.
-
-
3 issues received 11 new comments.
-
More precise control over app window features w3c/manifest#856 (8 comments by @aarongustafson, @alancutter, @benfrancis, @dmurph, @marcoscaceres, @mgiuca, @NotWoods)
-
Add manifest option for PWAs to be registered as scheme/protocol handlers w3c/manifest#846 (1 comment by @samtan-msft)
-
-
3 pull requests opened.
-
Obtain manifests only using the JSON MIME type w3c/manifest#858, by @marcoscaceres.
-
Remove redundant dependencies section w3c/manifest#857, by @marcoscaceres.
-
Chore: Use figures for the mask examples w3c/manifest#852, by @NotWoods.
-
-
2 pull requests merged.
-
Editorial: structure loop body with sub-steps w3c/manifest#827.
-
Chore: Use figures for the mask examples w3c/manifest#852.
-
-
1 pull request closed.
-
Set the manifest request's `destination`. w3c/manifest#829.
-
-
5 pull requests received 37 new comments.
-
Remove beforeinstallprompt and appinstalled events. w3c/manifest#836 (28 comments by @aarongustafson, @briantbutton, @david0178418, @dominickng, @madmoizo, @marcoscaceres, @mgiuca, @othermaciej, @rniwa)
-
Moves BeforeInstallPrompt and related text to a non-normative annex. w3c/manifest#843 (1 comment by @aarongustafson)
-
w3c/gamepad
-
5 issues opened.
-
Terminology of inputs. w3c/gamepad#131, by @Grovkillen.
-
button[16] not documented in the list of buttons. w3c/gamepad#130, by @Grovkillen.
-
"STANDARD GAMEPAD" should be defined in a separate attribute w3c/gamepad#129, by @Grovkillen.
-
Direction and thrust of the joystick w3c/gamepad#128, by @Grovkillen.
-
Add Internationalization Considerations section w3c/gamepad#127, by @marcoscaceres.
-
-
2 issues received 3 new comments.
-
"STANDARD GAMEPAD" should be defined in a separate attribute w3c/gamepad#129 (2 comments by @Grovkillen)
-
w3c/web-locks
-
1 pull request opened.
-
Editorial: add domintro note and simplify markup w3c/web-locks#61, by @inexorabletash.
-
-
1 pull request merged.
-
Editorial: add domintro note and simplify markup w3c/web-locks#61.
-
w3c/IndexedDB
-
1 issue opened.
-
Add type databases(name: string): IDBDatabase[] to IDBFactory w3c/IndexedDB#322, by @fritzschoff.
-
-
3 issues closed.
-
Add type databases(name: string): IDBDatabase[] to IDBFactory w3c/IndexedDB#322.
-
Where unique key goes w3c/IndexedDB#181.
-
-
5 issues received 11 new comments.
-
Combining cursors / query execution engine w3c/IndexedDB#298 (6 comments by @asutherland, @inexorabletash, @kaizhu256)
-
Add type databases(name: string): IDBDatabase[] to IDBFactory w3c/IndexedDB#322 (1 comment by @inexorabletash)
-
w3c/IndexedDB#36 (1 comment by @theSherwood)
-
w3c/IndexedDB#181 (1 comment by @r12a)
-
-
3 pull requests opened.
-
Add domintro note and simplify markup w3c/IndexedDB#326, by @inexorabletash.
-
Editorial: Use WebIDL terms |this| and |the given value| w3c/IndexedDB#325, by @inexorabletash.
-
Update CI config to use Python 3.7 w3c/IndexedDB#323, by @xfq.
-
-
5 pull requests merged.
-
Add domintro note and simplify markup w3c/IndexedDB#326.
-
Update CI config to use Python 3.7 w3c/IndexedDB#323.
-
Simplify transaction starting constraints to match reality w3c/IndexedDB#319.
-
Editorial: Improve example's text around uniqueness. w3c/IndexedDB#318.
-
Editorial: Call out browser versions for new features w3c/IndexedDB#321.
-
-
3 pull requests received 4 new comments.
-
Editorial: Call out browser versions for new features w3c/IndexedDB#321 (2 comments by @asutherland, @inexorabletash)
-
Editorial: Use WebIDL terms |this| and |the given value| w3c/IndexedDB#325 (1 comment by @inexorabletash)
-
Simplify transaction starting constraints to match reality w3c/IndexedDB#319 (1 comment by @inexorabletash)
-
w3c/FileAPI
-
2 issues opened.
-
Why are Blob() and File() constructors at Chromium 81 throwing RangeError? w3c/FileAPI#147, by @guest271314.
-
Add Internationalization Considerations section w3c/FileAPI#146, by @marcoscaceres.
-
-
6 issues received 17 new comments.
-
Why are Blob() and File() constructors at Chromium 81 throwing RangeError? w3c/FileAPI#147 (7 comments by @guest271314, @inexorabletash)
-
Define chunk size for `ReadableStream` created by `blob::stream()` w3c/FileAPI#144 (3 comments by @guest271314)
-
w3c/FileAPI#119 (1 comment by @angeloko23)
-
w3c/FileAPI#74 (1 comment by @koto)
-
-
1 pull request opened.
-
Update to Python 3 w3c/FileAPI#148, by @siusin.
-
-
1 pull request merged.
-
Update to Python 3 w3c/FileAPI#148.
-
w3c/webappswg
-
3 issues opened.
-
Clipboard spec is failing to publish w3c/webappswg#31, by @marcoscaceres.
-
Publish ImageResource spec w3c/webappswg#30, by @marcoscaceres.
-
Look at progressing IntersectionObserver w3c/webappswg#29, by @marcoscaceres.
-
-
3 issues closed.
-
Clipboard spec is failing to publish w3c/webappswg#31.
-
W3C WebApps page shows our group as closed w3c/webappswg#26.
-
Create a template for CR criteria w3c/webappswg#23.
-
-
8 issues received 15 new comments.
-
w3c/webappswg#4 (1 comment by @marcoscaceres)
w3c/image-resource
-
3 issues opened.
-
CFC for to publish FPWD w3c/image-resource#17, by @marcoscaceres.
-
Add link on from page w3c/image-resource#16, by @marcoscaceres.
-
Add me as admin :) w3c/image-resource#15, by @marcoscaceres.
-
-
2 issues closed.
-
Add link on from page w3c/image-resource#16.
-
Add me as admin :) w3c/image-resource#15.
-
-
4 issues received 8 new comments.
-
Are we ready to finalize this extraction and start a PR merging into the manifest? w3c/image-resource#10 (5 comments by @marcoscaceres, @rayankans)
-
-
3 pull requests opened.
-
Web Platform WG -> Web Apps WG w3c/image-resource#18, by @travisleithead.
-
Update README.md w3c/image-resource#14, by @marcoscaceres.
-
Prepare for FPWD w3c/image-resource#13, by @marcoscaceres.
-
-
4 pull requests merged.
-
Web Platform WG -> Web Apps WG w3c/image-resource#18.
-
Update README.md w3c/image-resource#14.
-
Prepare for FPWD w3c/image-resource#13.
-
Add a dfn in the fetching algorithm w3c/image-resource#12.
-
-
2 pull requests received 32 new comments.
-
Add a dfn in the fetching algorithm w3c/image-resource#12 (2 comments by @aarongustafson, @rayankans)
w3c/uievents
-
1 issue opened.
-
Make sure all UIEvents are data-exported (for xref from other specs) w3c/uievents#262, by @garykac.
-
-
1 issue closed.
-
Change click/auxclick/contextment/dblclick event types to PointerEvent? w3c/uievents#235.
-
-
2 issues received 2 new comments.
-
w3c/uievents#169 (1 comment by @marijnh)
-
Should Key event be fired for [Previous] and [Next] key on Virtual Keyboard? w3c/uievents#253 (1 comment by @makotokato)
-
-
1 pull request merged.
-
Change the type of click and auxclick to PointerEvent w3c/uievents#259.
-
-
1 pull request received 4 new comments.
-
Change the type of click and auxclick to PointerEvent w3c/uievents#259 (4 comments by @garykac, @marcoscaceres, @NavidZ)
-
w3c/pointerlock
-
3 issues opened.
-
feature request : Allow to set pointer position upon release w3c/pointerlock#61, by @nadavsinai.
-
Add Internationalization Considerations section w3c/pointerlock#60, by @marcoscaceres.
-
User gesture requirement allows for abuse. w3c/pointerlock#59, by @JamesHollyer.
-
-
1 issue closed.
-
User gesture requirement allows for abuse. w3c/pointerlock#59.
-
-
1 issue received 5 new comments.
-
User gesture requirement allows for abuse. w3c/pointerlock#59 (5 comments by @JamesHollyer, @marcoscaceres, @NavidZ, @scheib)
-
-
1 pull request received 1 new comment.
-
Editorial: Update redirected links to point to final location w3c/pointerlock#55 (1 comment by @garykac)
-
w3c/manifest-app-info
-
1 issue opened.
-
Add change log support to the web app manifest w3c/manifest-app-info#1, by @stanleyhon.
-
-
1 issue received 1 new comment.
-
Add reference to license/usage permission of assets in manifest w3c/manifest-app-info#2 (1 comment by @marcoscaceres)
-
w3c/push-api
-
1 issue opened.
-
Add Internationalization Considerations section w3c/push-api#323, by @marcoscaceres.
-
w3c/screen-orientation
-
1 issue opened.
-
Add internationalization considerations section w3c/screen-orientation#194, by @marcoscaceres.
-
w3c/web-share
-
1 issue opened.
-
Add internationalization considerations section w3c/web-share#143, by @marcoscaceres.
-
TR publications
-
6 documents published.
-
Selection API published as a Working Draft. History of Selection API
-
Gamepad published as a Working Draft. History of Gamepad
-
ARIA in HTML published 3 times as a Working Draft. History of ARIA in HTML
-
Push API published as a Working Draft. History of Push API
-
Participants
-
3 participants joined.
-
Jungkee Song (Microsoft Corporation) joined.
-
Vincent Scheib (Google LLC) joined.
-
Timo Tijhof (Wikimedia Foundation) joined.
-
-
2 participants left.
-
Tiger Oakes (Microsoft Corporation) left.
-
Michael Champion (Microsoft Corporation) left.
-
-
1 organization joined.
-
Wikimedia Foundation joined.
-
GitHub
w3c/ServiceWorker
-
3 issues opened.
-
Chrome: serviceWorker.ready() resolves before service worker is active after unregistering w3c/ServiceWorker#1505, by @HassHz.
-
Avoid double refresh on service worker update w3c/ServiceWorker#1504, by @novaknole.
-
Recovering from start failures w3c/ServiceWorker#1503, by @ytausky.
-
-
1 issue closed.
-
Service worker spec meetup w3c/ServiceWorker#1501.
-
-
5 issues received 18 new comments.
-
Service worker spec meetup w3c/ServiceWorker#1501 (5 comments by @asutherland, @jakearchibald, @n8schloss, @wanderview)
-
Recovering from start failures w3c/ServiceWorker#1503 (5 comments by @bzbarsky, @mfalken, @wanderview, @ytausky)
-
w3c/ServiceWorker#977 (1 comment by @valgussev)
-
1 pull request opened.
-
Define Purge Service Worker Registrations w3c/ServiceWorker#1506, by @jungkees.
-
-
1 pull request merged.
-
Add FetchEvent.handled (#1397) w3c/ServiceWorker#1496.
-
-
2 pull requests received 10 new comments.
-
Define Purge Service Worker Registrations w3c/ServiceWorker#1506 (7 comments by @asakusuma, @jungkees)
-
w3c/IndexedDB
-
1 issue reopened.
-
Where unique key goes w3c/IndexedDB#181, by @inexorabletash.
-
-
2 issues received 4 new comments.
-
w3c/IndexedDB#42 (1 comment by @Kuzcoo)
-
4 pull requests opened.
-
Editorial: Call out browser versions for new features w3c/IndexedDB#321, by @inexorabletash.
-
Editorial: Fix some incorrect capitalization, and make sections less shouty w3c/IndexedDB#320, by @inexorabletash.
-
Simplify transaction starting constraints to match reality w3c/IndexedDB#319, by @inexorabletash.
-
Editorial: Improve example's text around uniqueness. w3c/IndexedDB#318, by @inexorabletash.
-
-
1 pull request merged.
-
Editorial: Fix some incorrect capitalization, and make sections less shouty w3c/IndexedDB#320.
-
-
4 pull requests received 6 new comments.
-
Simplify transaction starting constraints to match reality w3c/IndexedDB#319 (3 comments by @asutherland, @inexorabletash)
-
Editorial: Fix some incorrect capitalization, and make sections less shouty w3c/IndexedDB#320 (1 comment by @inexorabletash)
-
Editorial: Improve example's text around uniqueness. w3c/IndexedDB#318 (1 comment by @inexorabletash)
-
w3c/webappswg
-
1 issue received 4 new comments.
w3c/web-share
-
1 issue opened.
-
File sharing not works on iOS w3c/web-share#142, by @bogdyak.
-
-
2 issues closed.
-
Share Images (high-level abstraction over Blob) w3c/web-share#12.
-
File sharing not works on iOS w3c/web-share#142.
-
-
1 issue reopened.
-
Share blobs via a Blob URL? w3c/web-share#7, by @mgiuca.
-
-
3 issues received 6 new comments.
-
w3c/web-share#7 (1 comment by @mgiuca)
w3c/gamepad
-
1 pull request opened.
-
[gamepad-extensions] Align with Web IDL specification w3c/gamepad#126, by @autokagami.
-
-
1 pull request merged.
-
[gamepad-extensions] Align with Web IDL specification w3c/gamepad#126.
-
w3c/uievents
-
1 issue opened.
-
2 pull requests opened.
-
Update index.html with the latest bikeshed w3c/uievents#260, by @NavidZ.
-
Change the type of click and auxclick to PointerEvent w3c/uievents#259, by @NavidZ.
-
-
1 pull request closed.
-
Update index.html with the latest bikeshed w3c/uievents#260.
-
-
2 pull requests received 5 new comments.
-
Change the type of click and auxclick to PointerEvent w3c/uievents#259 (3 comments by @garykac, @NavidZ)
-
w3c/badging
-
1 issue opened.
-
Rate limiting the ability to set a badge w3c/badging#68, by @mgiuca.
-
-
1 issue closed.
-
Do we really want to add Badge API to Navigator? w3c/badging#56.
-
-
3 issues received 22 new comments.
-
Rate limiting the ability to set a badge w3c/badging#68 (19 comments by @bzbarsky, @cwilso, @marcoscaceres, @mgiuca, @othermaciej, @yoavweiss)
-
w3c/pointerlock
-
1 issue opened.
-
The frequency of the security popup w3c/pointerlock#58, by @mr21.
-
-
1 issue closed.
-
The frequency of the security popup w3c/pointerlock#58.
-
-
1 issue received 3 new comments.
w3c/manifest
-
2 issues opened.
-
Procedure for moving manifests and Apps w3c/manifest#850, by @kevincox.
-
i18n support w3c/manifest#848, by @calidion.
-
-
7 issues received 18 new comments.
-
Add option to replace title bar with a display a smaller caption control overlay w3c/manifest#847 (1 comment by @marcoscaceres)
-
Icon purpose "splashscreen" and splashscreen text w3c/manifest#844 (1 comment by @FluorescentHallucinogen)
-
1 pull request received 1 new comment.
w3c/contact-picker
-
1 issue opened.
-
Acknowledge the history of contact API proposals w3c/contact-picker#30, by @jyasskin.
-
-
1 issue closed.
-
Acknowledge the history of contact API proposals w3c/contact-picker#30.
-
-
1 pull request opened.
-
Add a section on previous attempts and the differences w3c/contact-picker#31, by @rayankans.
-
-
1 pull request merged.
-
Add a section on previous attempts and the differences w3c/contact-picker#31.
-
-
1 pull request received 3 new comments.
-
Add a section on previous attempts and the differences w3c/contact-picker#31 (3 comments by @beverloo, @rayankans)
-
w3c/manifest-app-info
-
1 issue opened.
-
Add reference to license/usage permission of assets in manifest w3c/manifest-app-info#2, by @diekus-zz.
-
w3c/push-api
-
1 issue opened.
-
Make automatic failing normative w3c/push-api#322, by @annevk.
-
TR publications
-
2 documents published.
-
The Screen Orientation API published as a Working Draft. History of The Screen Orientation API
-
Gamepad published as a Working Draft. History of Gamepad
-
Participants
-
2 participants joined.
-
Carolyn MacLeod (IBM Corporation) joined.
-
Adrian Hope-Bailie (Coil Technologies, Inc.) joined.
-
-
1 participant left.
-
Raymes Khoury (Google LLC) left.
-
-
2 organizations joined.
-
IBM Corporation joined.
-
Coil Technologies, Inc. joined.
-
GitHub
w3c/ServiceWorker
-
8 issues opened.
-
Should we consider Worklets as clients? w3c/ServiceWorker#1502, by @bakulf.
-
Service worker spec meetup w3c/ServiceWorker#1501, by @jakearchibald.
-
navigate() behavior in browsers for file:/// and mixed content does not match spec w3c/ServiceWorker#1500, by @bzbarsky.
-
Size limits with synchronous WebAssembly functions w3c/ServiceWorker#1499, by @Pauan.
-
OPTIONS request reported as GET w3c/ServiceWorker#1498, by @anthumchris.
-
Credentials on scripts imported by importScripts() w3c/ServiceWorker#1497, by @makotoshimazu.
-
Update algorithm may want to abort in absence of a newest worker w3c/ServiceWorker#1495, by @perryjiang.
-
Inaccurate Abstract w3c/ServiceWorker#1493, by @annevk.
-
-
2 issues closed.
-
Should the order of registrations returned by getRegistrations() be sorted by scope? w3c/ServiceWorker#1465.
-
Inaccurate Abstract w3c/ServiceWorker#1493.
-
-
15 issues received 47 new comments.
-
Service worker spec meetup w3c/ServiceWorker#1501 (9 comments by @jungkees, @mfalken, @mkruisselbrink, @n8schloss, @wanderview, @xtuc)
-
Size limits with synchronous WebAssembly functions w3c/ServiceWorker#1499 (9 comments by @annevk, @jakearchibald, @moshevds, @Pauan)
-
Should the order of registrations returned by getRegistrations() be sorted by scope? w3c/ServiceWorker#1465 (8 comments by @asutherland, @jungkees, @makotoshimazu, @mfalken, @wanderview, @wangw-1991)
-
Top-level await integration for ServiceWorkers running modules w3c/ServiceWorker#1407 (5 comments by @jakearchibald, @Pauan)
-
Credentials on scripts imported by importScripts() w3c/ServiceWorker#1497 (4 comments by @annevk, @domenic, @mfalken)
-
Should we consider Worklets as clients? w3c/ServiceWorker#1502 (2 comments by @nhiroki, @wanderview)
-
navigate() behavior in browsers for file:/// and mixed content does not match spec w3c/ServiceWorker#1500 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#977 (1 comment by @jtsmedley)
-
w3c/ServiceWorker#822 (1 comment by @jespertheend)
-
w3c/ServiceWorker#1299 (1 comment by @annevk)
-
w3c/ServiceWorker#1159 (1 comment by @pinobatch)
-
w3c/ServiceWorker#863 (1 comment by @tomayac)
-
-
2 pull requests opened.
-
Add FetchEvent.handled (#1397) w3c/ServiceWorker#1496, by @tingshao.
-
Rewriting abstract w3c/ServiceWorker#1494, by @jakearchibald.
-
-
1 pull request merged.
-
Rewriting abstract w3c/ServiceWorker#1494.
-
-
3 pull requests received 33 new comments.
-
Rewriting abstract w3c/ServiceWorker#1494 (5 comments by @annevk, @jakearchibald, @jungkees, @mfalken)
-
Handle asynchronous modules (top-level await). w3c/ServiceWorker#1444 (3 comments by @jakearchibald, @littledan)
w3c/manifest
-
9 issues opened.
-
Add option to replace title bar with a display a smaller caption control overlay w3c/manifest#847, by @amandabaker.
-
Add manifest option for PWAs to be registered as scheme/protocol handlers w3c/manifest#846, by @fabiorocha.
-
Allow installed PWA to run on OS login w3c/manifest#845, by @laukstein.
-
Icon purpose "splashscreen" and splashscreen text w3c/manifest#844, by @NekR.
-
[Proposal] Add options to control app window w3c/manifest#842, by @FluorescentHallucinogen.
-
Add more than one icon at PWA install w3c/manifest#841, by @FluorescentHallucinogen.
-
[Proposal] Home screen widgets w3c/manifest#840, by @FluorescentHallucinogen.
-
[Proposal] 'maximized' and 'minimized' display modes values w3c/manifest#839, by @FluorescentHallucinogen.
-
Microsoft's company url redirects to another Microsoft url w3c/manifest#837, by @janiceshiu.
-
-
3 issues closed.
-
Microsoft's company url redirects to another Microsoft url w3c/manifest#837.
-
[Proposal] Add options to control app window w3c/manifest#842.
-
[Proposal] Home screen widgets w3c/manifest#840.
-
-
8 issues received 23 new comments.
-
Icon purpose "splashscreen" and splashscreen text w3c/manifest#844 (4 comments by @dominickng, @FluorescentHallucinogen, @NekR)
-
Add more than one icon at PWA install w3c/manifest#841 (4 comments by @FluorescentHallucinogen, @NotWoods)
-
Add manifest option for PWAs to be registered as scheme/protocol handlers w3c/manifest#846 (3 comments by @fabiorocha, @FluorescentHallucinogen)
-
Microsoft's company url redirects to another Microsoft url w3c/manifest#837 (3 comments by @aarongustafson, @alancutter, @janiceshiu)
-
[Proposal] Home screen widgets w3c/manifest#840 (2 comments by @aarongustafson, @FluorescentHallucinogen)
-
[Proposal] 'maximized' and 'minimized' display modes values w3c/manifest#839 (1 comment by @aarongustafson)
-
2 pull requests opened.
-
Moves BeforeInstallPrompt and related text to a non-normative annex. w3c/manifest#843, by @mgiuca.
-
Chore: Update link for Microsoft's company URL. Fixes #837 w3c/manifest#838, by @janiceshiu.
-
-
1 pull request closed.
-
Chore: Update link for Microsoft's company URL. Fixes #837 w3c/manifest#838.
-
-
5 pull requests received 32 new comments.
-
Moves BeforeInstallPrompt and related text to a non-normative annex. w3c/manifest#843 (10 comments by @dominickng, @erikmchut, @marcoscaceres, @mgiuca, @rniwa, @slightlyoff)
-
Processing the manifest is no longer a function of document URL w3c/manifest#834 (7 comments by @alancutter, @mgiuca)
-
BREAKING CHANGE: Replace "badge" with "monochrome" w3c/manifest#833 (6 comments by @mgiuca, @NotWoods)
-
Chore: Update link for Microsoft's company URL. Fixes #837 w3c/manifest#838 (5 comments by @aarongustafson, @janiceshiu, @kenchris)
-
Remove beforeinstallprompt and appinstalled events. w3c/manifest#836 (4 comments by @briantbutton, @erikmchut, @mgiuca)
-
w3c/IndexedDB
-
1 issue opened.
-
Missing durability attribute in the IDBTransaction interface w3c/IndexedDB#316, by @triple-underscore.
-
-
2 issues closed.
-
Missing durability attribute in the IDBTransaction interface w3c/IndexedDB#316.
-
Define flush-to-disk guarantees and control w3c/IndexedDB#50.
-
-
1 issue received 2 new comments.
-
Missing durability attribute in the IDBTransaction interface w3c/IndexedDB#316 (2 comments by @inexorabletash, @triple-underscore)
-
-
2 pull requests opened.
-
Address missing durability attribute/docs. Fixes #316 w3c/IndexedDB#317, by @inexorabletash.
-
Fix typo in link syntax w3c/IndexedDB#315, by @Simran-B.
-
-
3 pull requests merged.
-
Address missing durability attribute/docs. Fixes #316 w3c/IndexedDB#317.
-
Fix typo in link syntax w3c/IndexedDB#315.
-
Sketch out spec text for transaction durability option w3c/IndexedDB#301.
-
-
3 pull requests received 6 new comments.
-
Address missing durability attribute/docs. Fixes #316 w3c/IndexedDB#317 (2 comments by @inexorabletash, @triple-underscore)
-
Sketch out spec text for transaction durability option w3c/IndexedDB#301 (2 comments by @asutherland, @inexorabletash)
-
w3c/badging
-
4 issues opened.
-
"service worker context" w3c/badging#67, by @mfalken.
-
Clarity around "is a service worker client" w3c/badging#66, by @mfalken.
-
Feature request: Allow additional symbols as the badge value w3c/badging#65, by @mgiuca.
-
Change color of the badge w3c/badging#64, by @slootmaekersdirk.
-
-
3 issues received 5 new comments.
-
Feature request: Allow additional symbols as the badge value w3c/badging#65 (2 comments by @g-ortuno, @mgiuca)
w3c/pointerlock
-
3 issues opened.
-
where possible, use xref to link terms from other specs w3c/pointerlock#56, by @janiceshiu.
-
update links to point to their final location w3c/pointerlock#54, by @janiceshiu.
-
No matching definition found for `triggered by user activation` w3c/pointerlock#53, by @janiceshiu.
-
-
2 issues closed.
-
where possible, use xref to link terms from other specs w3c/pointerlock#56.
-
update links to point to their final location w3c/pointerlock#54.
-
-
1 issue received 2 new comments.
-
No matching definition found for `triggered by user activation` w3c/pointerlock#53 (2 comments by @marcoscaceres)
-
-
2 pull requests opened.
-
Editorial: Use xref to link document active sandboxing flag set w3c/pointerlock#57, by @janiceshiu.
-
Editorial: Update redirected links to point to final location w3c/pointerlock#55, by @janiceshiu.
-
-
2 pull requests merged.
-
Editorial: Use xref to link document active sandboxing flag set w3c/pointerlock#57.
-
Editorial: Update redirected links to point to final location w3c/pointerlock#55.
-
-
3 pull requests received 23 new comments.
-
Editorial: Update redirected links to point to final location w3c/pointerlock#55 (2 comments by @marcoscaceres)
-
Editorial: Use xref to link document active sandboxing flag set w3c/pointerlock#57 (1 comment by @marcoscaceres)
w3c/screen-orientation
-
2 issues opened.
-
Nested browsing contexts cannot be accessed `in parallel` w3c/screen-orientation#193, by @janiceshiu.
-
Browsing contexts do not have a document w3c/screen-orientation#192, by @janiceshiu.
-
-
1 pull request opened.
-
editorial: remove unused fullscreen element dependency w3c/screen-orientation#191, by @janiceshiu.
-
-
1 pull request merged.
-
editorial: remove unused fullscreen element dependency w3c/screen-orientation#191.
-
-
1 pull request received 1 new comment.
-
editorial: remove unused fullscreen element dependency w3c/screen-orientation#191 (1 comment by @marcoscaceres)
-
w3c/gamepad
-
1 pull request opened.
-
Add conformance section w3c/gamepad#125, by @foolip.
-
-
1 pull request merged.
-
Add conformance section w3c/gamepad#125.
-
w3c/uievents
-
1 issue opened.
-
Move impl info from glossary to proper algorithmic description of event handlers w3c/uievents#258, by @garykac.
-
-
1 issue received 1 new comment.
-
Move impl info from glossary to proper algorithmic description of event handlers w3c/uievents#258 (1 comment by @garykac)
-
w3c/web-share
-
1 issue opened.
-
PDF share support w3c/web-share#141, by @ashishgehlot.
-
-
1 issue closed.
-
PDF share support w3c/web-share#141.
-
-
1 issue received 1 new comment.
w3c/image-resource
-
1 issue opened.
-
Are we ready to finalize this extraction and start a PR merging into the manifest? w3c/image-resource#10, by @aarongustafson.
-
-
1 issue closed.
-
Should this include "purpose" and "platform" from Manifest (and also Bikeshed vs Respec) w3c/image-resource#4.
-
-
2 issues received 2 new comments.
-
Are we ready to finalize this extraction and start a PR merging into the manifest? w3c/image-resource#10 (1 comment by @rayankans)
-
Should this include "purpose" and "platform" from Manifest (and also Bikeshed vs Respec) w3c/image-resource#4 (1 comment by @aarongustafson)
-
-
2 pull requests opened.
-
Add a dfn in the fetching algorithm w3c/image-resource#12, by @rayankans.
-
Addin a note about space-separated values w3c/image-resource#11, by @aarongustafson.
-
-
1 pull request merged.
-
Addin a note about space-separated values w3c/image-resource#11.
-
-
1 pull request received 2 new comments.
-
Addin a note about space-separated values w3c/image-resource#11 (2 comments by @aarongustafson, @rayankans)
-
w3c/webappswg
-
1 issue opened.
-
Move input-events to CR w3c/webappswg#28, by @johanneswilm.
-
w3c/FileAPI
-
2 issues opened.
-
Navigation to blob URLs w3c/FileAPI#145, by @annevk.
-
Define chunk size for `ReadableStream` created by `blob::stream()` w3c/FileAPI#144, by @kevinmarschke.
-
-
12 issues closed.
-
Reslove Blob to an existing ArrayBuffer w3c/FileAPI#143.
-
Consider dropping lowercasing requirement for the type attribute w3c/FileAPI#122.
-
Consider reserializing type attributes, not just parsing them. w3c/FileAPI#123.
-
add dataURL method w3c/FileAPI#136.
-
Navigation to blob URLs w3c/FileAPI#145.
-
Add readAsSharedArrayBuffer to FileReader w3c/FileAPI#73.
-
file selection dialog callable by file api w3c/FileAPI#56.
-
Remove parsable mime type requirement? w3c/FileAPI#13.
-
Include file creation time and last access time. w3c/FileAPI#26.
-
Add a FileList.drop(index) method w3c/FileAPI#25.
-
[FileAPI] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/FileAPI#137.
-
-
16 issues received 25 new comments.
-
Define chunk size for `ReadableStream` created by `blob::stream()` w3c/FileAPI#144 (8 comments by @annevk, @domenic, @kevinmarschke, @ricea)
-
w3c/FileAPI#122 (1 comment by @annevk)
-
w3c/FileAPI#123 (1 comment by @annevk)
-
w3c/FileAPI#73 (1 comment by @annevk)
-
w3c/FileAPI#56 (1 comment by @annevk)
-
w3c/FileAPI#13 (1 comment by @annevk)
-
w3c/FileAPI#26 (1 comment by @annevk)
-
w3c/FileAPI#25 (1 comment by @annevk)
-
w3c/FileAPI#23 (1 comment by @annevk)
-
w3c/FileAPI#35 (1 comment by @annevk)
-
w3c/FileAPI#93 (1 comment by @annevk)
-
w3c/push-api
-
1 issue received 1 new comment.
-
w3c/push-api#303 (1 comment by @evan-brass)
-