Web Applications Working Group - Activity in 2019
No matches.
TR publications
-
9 documents published.
-
HTML Accessibility API Mappings 1.0 published 4 times as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
Web App Manifest published twice as a Working Draft. History of Web App Manifest
-
ARIA in HTML published twice as a Working Draft. History of ARIA in HTML
-
Web Share API published as a First Public Working Draft. History of Web Share API
-
Participants
-
1 participant joined.
-
Janice Shiu (Mozilla Foundation) joined.
-
GitHub
w3c/ServiceWorker
-
5 issues opened.
-
React service worker is not working with Keycloak w3c/ServiceWorker#1492, by @kumaraswamyDR.
-
Using registrations that failed to install a ServiceWorker w3c/ServiceWorker#1491, by @perryjiang.
-
cache.match() and COEP w3c/ServiceWorker#1490, by @wanderview.
-
Add 'immediate: true' to the draft spec w3c/ServiceWorker#1489, by @summercms.
-
cors image request retry not work w3c/ServiceWorker#1488, by @QingLeiLi.
-
-
3 issues closed.
-
Make serviceWorker.ready spec match implementations w3c/ServiceWorker#1477.
-
React service worker is not working with Keycloak w3c/ServiceWorker#1492.
-
cors image request retry not work w3c/ServiceWorker#1488.
-
-
6 issues received 18 new comments.
-
cache.match() and COEP w3c/ServiceWorker#1490 (11 comments by @annevk, @ArthurSonzogni, @asutherland, @wanderview)
-
w3c/ServiceWorker#1390 (1 comment by @kevodwyer)
-
-
1 pull request opened.
-
Fixing ready promise definition w3c/ServiceWorker#1487, by @jakearchibald.
-
-
3 pull requests merged.
-
Fixing ready promise definition w3c/ServiceWorker#1487.
-
Drop 'potential-navigation-or-subresource request'. w3c/ServiceWorker#1486.
-
Use ExtendableMessageEvent for messageerror in service workers. w3c/ServiceWorker#1485.
-
-
1 pull request closed.
-
Make serviceWorker.ready spec match implementations w3c/ServiceWorker#1478.
-
-
4 pull requests received 7 new comments.
-
Drop 'potential-navigation-or-subresource request'. w3c/ServiceWorker#1486 (2 comments by @jakearchibald)
-
Make serviceWorker.ready spec match implementations w3c/ServiceWorker#1478 (2 comments by @jakearchibald, @Yannic)
-
Use ExtendableMessageEvent for messageerror in service workers. w3c/ServiceWorker#1485 (1 comment by @mfalken)
w3c/uievents
-
1 issue opened.
-
Should Key event be fired for [Previous] and [Next] key on Virtual Keyboard? w3c/uievents#253, by @makotokato.
-
-
2 issues received 2 new comments.
-
w3c/uievents#5 (1 comment by @Dalzhim)
-
Should Key event be fired for [Previous] and [Next] key on Virtual Keyboard? w3c/uievents#253 (1 comment by @masayuki-nakano)
-
-
3 pull requests opened.
-
index.html: rebuild w3c/uievents#256, by @vapier.
-
fix link markdown typo w3c/uievents#255, by @vapier.
-
build.py: get it working under Python 3 w3c/uievents#254, by @vapier.
-
-
3 pull requests merged.
-
index.html: rebuild w3c/uievents#256.
-
fix link markdown typo w3c/uievents#255.
-
build.py: get it working under Python 3 w3c/uievents#254.
-
-
3 pull requests received 4 new comments.
w3c/gamepad
-
1 issue opened.
-
Maybe use "sticky activation" model? w3c/gamepad#124, by @marcoscaceres.
-
-
1 issue closed.
-
What's a good place to start contributing to the Gamepad spec? w3c/gamepad#121.
-
-
1 issue received 1 new comment.
-
What's a good place to start contributing to the Gamepad spec? w3c/gamepad#121 (1 comment by @marcoscaceres)
-
w3c/web-share
-
2 issues opened.
-
Add Eric Willigers as editor w3c/web-share#138, by @mgiuca.
-
Should calling share() "consume" the activation? w3c/web-share#136, by @marcoscaceres.
-
-
2 issues closed.
-
Preparations for First Public Working Draft w3c/web-share#129.
-
Add Eric Willigers as editor w3c/web-share#138.
-
-
2 issues received 6 new comments.
-
Should calling share() "consume" the activation? w3c/web-share#136 (3 comments by @marcoscaceres, @othermaciej)
-
4 pull requests opened.
-
editorial: Link `this` to Web IDL w3c/web-share#140, by @saschanaz.
-
Added Eric Willigers as co-editor. w3c/web-share#139, by @mgiuca.
-
BREAKING CHANGE: make share() consume user activation w3c/web-share#137, by @marcoscaceres.
-
Editorial: Use new HTML activation model w3c/web-share#135, by @marcoscaceres.
-
-
2 pull requests merged.
-
Added Eric Willigers as co-editor. w3c/web-share#139.
-
Editorial: Use new HTML activation model w3c/web-share#135.
-
-
3 pull requests received 6 new comments.
-
BREAKING CHANGE: make share() consume user activation w3c/web-share#137 (1 comment by @marcoscaceres)
w3c/manifest
-
3 issues opened.
-
Steps for processing shortcut member are very vague w3c/manifest#831, by @dominickng.
-
Rename `purpose: badge` to `purpose: monochrome` and expand on it w3c/manifest#830, by @NotWoods.
-
1 issue closed.
-
Steps for processing shortcut member are very vague w3c/manifest#831.
-
-
5 issues received 75 new comments.
-
beforeinstallprompt : Prompting user makes it to hard to discern whether the user truly wanted to "install" a web app w3c/manifest#835 (68 comments by @aeallord, @alancutter, @dominickng, @ecjs, @electrify12, @elylucas, @jyasskin, @kenchris, @madmoizo, @marcoscaceres, @mgiuca, @NekR, @NotWoods, @othermaciej, @rniwa, @Splaktar, @tomayac, @vincentmorneau)
-
Rename `purpose: badge` to `purpose: monochrome` and expand on it w3c/manifest#830 (4 comments by @mgiuca, @NotWoods)
-
w3c/manifest#555 (1 comment by @JacobDB)
-
w3c/manifest#758 (1 comment by @laukstein)
-
-
7 pull requests opened.
-
Remove beforeinstallprompt and appinstalled events. w3c/manifest#836, by @marcoscaceres.
-
Processing the manifest is no longer a function of document URL w3c/manifest#834, by @mgiuca.
-
BREAKING CHANGE: Replace "badge" with "monochrome" w3c/manifest#833, by @NotWoods.
-
Rewrite processing shortcuts algorithm to be more precise w3c/manifest#832, by @mgiuca.
-
Set the manifest request's `destination`. w3c/manifest#829, by @mikewest.
-
Editorial: fix typo w3c/manifest#828, by @jugglinmike.
-
Editorial: structure loop body with sub-steps w3c/manifest#827, by @jugglinmike.
-
-
2 pull requests merged.
-
Rewrite processing shortcuts algorithm to be more precise w3c/manifest#832.
-
Editorial: fix typo w3c/manifest#828.
-
-
7 pull requests received 69 new comments.
-
BREAKING CHANGE: Replace "badge" with "monochrome" w3c/manifest#833 (28 comments by @aarongustafson, @marcoscaceres, @NotWoods)
-
Remove beforeinstallprompt and appinstalled events. w3c/manifest#836 (18 comments by @aarongustafson, @dominickng, @marcoscaceres, @mgiuca, @othermaciej, @rniwa)
-
Processing the manifest is no longer a function of document URL w3c/manifest#834 (10 comments by @alancutter, @fallaciousreasoning, @marcoscaceres, @mgiuca, @NotWoods)
-
Rewrite processing shortcuts algorithm to be more precise w3c/manifest#832 (8 comments by @aarongustafson, @dominickng, @marcoscaceres, @mgiuca)
-
Set the manifest request's `destination`. w3c/manifest#829 (3 comments by @marcoscaceres, @mikewest)
-
w3c/webappswg
-
2 issues opened.
-
Initiate wide review of Web Share API w3c/webappswg#27, by @marcoscaceres.
-
W3C WebApps page shows our group as closed w3c/webappswg#26, by @marcoscaceres.
-
-
1 issue received 4 new comments.
-
W3C WebApps page shows our group as closed w3c/webappswg#26 (4 comments by @marcoscaceres, @plehegar, @siusin)
-
w3c/IndexedDB
-
2 issues opened.
-
Add a new event `onbeforecommit` on the interface IDBTransaction w3c/IndexedDB#314, by @Jack-Works.
-
IDBTransaction's error attribute can return null but isn't nullable w3c/IndexedDB#312, by @jdm.
-
-
1 issue closed.
-
IDBTransaction's error attribute can return null but isn't nullable w3c/IndexedDB#312.
-
-
3 issues received 7 new comments.
-
Add a new event `onbeforecommit` on the interface IDBTransaction w3c/IndexedDB#314 (5 comments by @inexorabletash, @Jack-Works)
-
w3c/IndexedDB#206 (1 comment by @inexorabletash)
-
IDBTransaction's error attribute can return null but isn't nullable w3c/IndexedDB#312 (1 comment by @inexorabletash)
-
-
1 pull request opened.
-
IDBTransaction's error attribute should be nullable w3c/IndexedDB#313, by @inexorabletash.
-
-
1 pull request merged.
-
IDBTransaction's error attribute should be nullable w3c/IndexedDB#313.
-
-
3 pull requests received 5 new comments.
-
Sketch out spec text for transaction durability option w3c/IndexedDB#301 (2 comments by @inexorabletash, @pwnall)
-
IDBTransaction's error attribute should be nullable w3c/IndexedDB#313 (2 comments by @inexorabletash)
-
w3c/badging
-
2 issues received 6 new comments.
-
Make setXXXBadge(undefined) set flag instead of clearing w3c/badging#60 (1 comment by @fallaciousreasoning)
w3c/FileAPI
-
1 issue opened.
-
Reslove Blob to an existing ArrayBuffer w3c/FileAPI#143, by @Zhang-Junzhi.
-
-
1 issue received 12 new comments.
-
Reslove Blob to an existing ArrayBuffer w3c/FileAPI#143 (12 comments by @annevk, @mkruisselbrink, @Zhang-Junzhi)
-
w3c/using-aria
-
2 issues received 2 new comments.
-
2 pull requests opened.
-
Correct MSIE casing, remove erroneous invisible space w3c/using-aria#53, by @tomayac.
-
Consistent anchors w3c/using-aria#52, by @yatil.
-
-
1 pull request merged.
-
Correct MSIE casing, remove erroneous invisible space w3c/using-aria#53.
-
-
1 pull request received 2 new comments.
w3c/contact-picker
-
1 issue opened.
-
maybe split up name to to components? w3c/contact-picker#29, by @jimmywarting.
-
-
1 issue received 1 new comment.
TR publications
-
9 documents published.
-
ARIA in HTML published twice as a Working Draft. History of ARIA in HTML
-
Web App Manifest published 3 times as a Working Draft. History of Web App Manifest
-
Gamepad published as a Working Draft. History of Gamepad
-
HTML Accessibility API Mappings 1.0 published twice as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
The Screen Orientation API published as a Working Draft. History of The Screen Orientation API
-
GitHub
w3c/ServiceWorker
-
1 issue opened.
-
Behavior for accessing cache storage in opaque origins w3c/ServiceWorker#1484, by @mkruisselbrink.
-
-
1 issue closed.
-
Behavior of the onfetch setter regarding no-fetch service workers w3c/ServiceWorker#1004.
-
-
1 issue reopened.
-
is the browser required to start the ServiceWorker for postMessage() if there is no message event handler? w3c/ServiceWorker#1200, by @mfalken.
-
-
6 issues received 8 new comments.
-
Top-level await integration for ServiceWorkers running modules w3c/ServiceWorker#1407 (3 comments by @hiroshige-g, @Ms2ger)
-
w3c/ServiceWorker#1357 (1 comment by @nachoab)
-
Need to explain name matching rules for cache names w3c/ServiceWorker#1483 (1 comment by @aphillips)
-
w3c/ServiceWorker#1200 (1 comment by @mfalken)
-
w3c/ServiceWorker#1004 (1 comment by @jungkees)
-
w3c/ServiceWorker#339 (1 comment by @sheerun)
-
-
2 pull requests opened.
-
Drop 'potential-navigation-or-subresource request'. w3c/ServiceWorker#1486, by @mikewest.
-
Use ExtendableMessageEvent for messageerror in service workers. w3c/ServiceWorker#1485, by @mkruisselbrink.
-
-
1 pull request received 3 new comments.
-
Use ExtendableMessageEvent for messageerror in service workers. w3c/ServiceWorker#1485 (3 comments by @asutherland, @mfalken, @mkruisselbrink)
-
w3c/manifest
-
4 issues opened.
-
Spec what it means to support "manifest" via <link>'s relList w3c/manifest#826, by @marcoscaceres.
-
Media type -> MIME type w3c/manifest#822, by @annevk.
-
Why does obtaining not check a MIME type? w3c/manifest#821, by @annevk.
-
Open PWA application from Android application w3c/manifest#820, by @jayarajm.
-
-
5 issues closed.
-
Clarify ServiceWorkerRegistrationObject’s purpose w3c/manifest#800.
-
Media type -> MIME type w3c/manifest#822.
-
Open PWA application from Android application w3c/manifest#820.
-
App shortcuts / actions w3c/manifest#582.
-
-
8 issues received 16 new comments.
-
Why does obtaining not check a MIME type? w3c/manifest#821 (9 comments by @annevk, @foolip, @marcoscaceres)
-
Spec what it means to support "manifest" via <link>'s relList w3c/manifest#826 (1 comment by @marcoscaceres)
-
w3c/manifest#689 (1 comment by @Hoodlum-Z)
-
w3c/manifest#436 (1 comment by @tomayac)
-
w3c/manifest#582 (1 comment by @aarongustafson)
-
-
4 pull requests opened.
-
BREAKING CHANGE: remove serviceworker member w3c/manifest#825, by @marcoscaceres.
-
Chore: Replace "media type" with "MIME type". w3c/manifest#824, by @mgiuca.
-
chore: export some terms needed by Badging w3c/manifest#823, by @marcoscaceres.
-
Fixing a typo w3c/manifest#819, by @aarongustafson.
-
-
5 pull requests merged.
-
BREAKING CHANGE: remove serviceworker member w3c/manifest#825.
-
Chore: Replace "media type" with "MIME type". w3c/manifest#824.
-
Fixing a typo w3c/manifest#819.
-
Add shortcuts feature to the explainer and spec w3c/manifest#768.
-
-
4 pull requests received 25 new comments.
-
Add shortcuts feature to the explainer and spec w3c/manifest#768 (21 comments by @aarongustafson, @mgiuca)
-
Chore: Replace "media type" with "MIME type". w3c/manifest#824 (2 comments by @marcoscaceres, @mgiuca)
-
Make Service Worker registration work properly (don't use outdated steps) w3c/manifest#792 (1 comment by @mgiuca)
-
w3c/IndexedDB
-
3 issues opened.
-
Array proxies as keys? w3c/IndexedDB#309, by @inexorabletash.
-
Issues with key and keyPath usage w3c/IndexedDB#308, by @annevk.
-
Bidirection Replication w3c/IndexedDB#307, by @guettli.
-
-
1 issue closed.
-
Array proxies as keys? w3c/IndexedDB#309.
-
-
5 issues received 9 new comments.
-
w3c/IndexedDB#10 (2 comments by @inexorabletash)
-
w3c/IndexedDB#254 (1 comment by @asutherland)
-
2 pull requests opened.
-
Disallow proxies during key conversion w3c/IndexedDB#311, by @inexorabletash.
-
Make transactions inactive during clone w3c/IndexedDB#310, by @inexorabletash.
-
-
2 pull requests merged.
-
Make transactions inactive during clone w3c/IndexedDB#310.
-
Disallow proxies during key conversion w3c/IndexedDB#311.
-
-
2 pull requests received 4 new comments.
w3c/uievents
-
3 issues opened.
-
Pixel values should all be in CSS pixels w3c/uievents#250, by @instylevii.
-
4 issues received 8 new comments.
-
Declare whether line breaks in `CompositionEvent.data` and `InputEvent.data` should be as-is or converted to `\n` w3c/uievents#251 (1 comment by @masayuki-nakano)
w3c/gamepad
-
1 issue closed.
-
Specification status report for TPAC 2019 w3c/gamepad#99.
-
-
1 pull request merged.
-
Editorial: Fix a few inconsistencies in "GamepadButton Interface" w3c/gamepad#122.
-
-
3 pull requests received 25 new comments.
-
Spec liveness of Gamepad and GamepadButton objects (#8) w3c/gamepad#123 (19 comments by @domenic, @marcoscaceres, @nondebug)
-
Editorial: Fix a few inconsistencies in "GamepadButton Interface" w3c/gamepad#122 (4 comments by @kri, @marcoscaceres)
-
w3c/screen-orientation
-
1 issue received 11 new comments.
-
Should the -secondary orientations be exposed? w3c/screen-orientation#188 (11 comments by @marcoscaceres, @mounirlamouri, @smfr)
-
-
1 pull request opened.
-
Editorial: fix typo w3c/screen-orientation#190, by @kri.
-
-
1 pull request merged.
-
Editorial: fix typo w3c/screen-orientation#190.
-
-
1 pull request received 1 new comment.
w3c/badging
-
1 issue opened.
-
Remove dependencies section w3c/badging#63, by @marcoscaceres.
-
-
4 issues closed.
-
Make setXXXBadge(undefined) set flag instead of clearing w3c/badging#60.
-
Update Spec to Match Explainer w3c/badging#45.
-
Add examples of client/document badging w3c/badging#58.
-
-
5 issues received 33 new comments.
-
Should OS failures setting the badge reject the promise? w3c/badging#61 (15 comments by @fallaciousreasoning, @marcoscaceres, @mgiuca)
-
Make setXXXBadge(undefined) set flag instead of clearing w3c/badging#60 (11 comments by @fallaciousreasoning, @marcoscaceres, @mgiuca)
-
Do we really want to add Badge API to Navigator? w3c/badging#56 (5 comments by @annevk, @marcoscaceres, @mgiuca)
-
Should the badge be associated with a browsing context instead of a document? w3c/badging#59 (1 comment by @mgiuca)
-
-
1 pull request opened.
-
testing PR preview w3c/badging#62, by @marcoscaceres.
-
-
1 pull request merged.
-
Spec rewrite: Update to new separate document/app API w3c/badging#57.
-
-
1 pull request closed.
-
testing PR preview w3c/badging#62.
-
-
1 pull request received 32 new comments.
-
Spec rewrite: Update to new separate document/app API w3c/badging#57 (32 comments by @annevk, @marcoscaceres, @mgiuca)
-
w3c/image-resource
-
1 issue received 1 new comment.
-
Should this include "purpose" and "platform" from Manifest (and also Bikeshed vs Respec) w3c/image-resource#4 (1 comment by @marcoscaceres)
-
w3c/web-share
-
1 issue closed.
-
Specification status report for TPAC 2019 w3c/web-share#121.
-
-
3 issues received 3 new comments.
-
3 pull requests opened.
-
chore: inform people that l2 is folded into main spec w3c/web-share#134, by @marcoscaceres.
-
Add the ability to share files w3c/web-share#133, by @marcoscaceres.
-
Editorial: drop levels + small fixes w3c/web-share#132, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: drop levels + small fixes w3c/web-share#132.
-
-
2 pull requests received 4 new comments.
-
chore: inform people that l2 is folded into main spec w3c/web-share#134 (2 comments by @marcoscaceres, @mgiuca)
-
w3c/using-aria
-
1 issue opened.
-
Error in section 2.10 regarding use of aria-label/labelledby for <section> elements w3c/using-aria#51, by @gmjellin.
-
-
1 issue closed.
-
1 issue received 4 new comments.
-
Error in section 2.10 regarding use of aria-label/labelledby for <section> elements w3c/using-aria#51 (4 comments by @gmjellin, @JAWS-test, @scottaohara)
-
w3c/webappswg
-
1 issue opened.
-
Check specs have an internationalization section w3c/webappswg#25, by @marcoscaceres.
-
-
1 issue closed.
-
TPAC 2019: Specification status reports w3c/webappswg#19.
-
w3c/web-locks
-
1 issue received 4 new comments.
w3c/contact-picker
-
3 issues closed.
-
Detect which contact properties are supported by the browser w3c/contact-picker#19.
-
Provide access to address properties w3c/contact-picker#12.
-
Provide access to contact's icon w3c/contact-picker#13.
-
-
1 pull request merged.
-
Add support for selecting icons, resolves #13 w3c/contact-picker#28.
-
-
1 pull request received 10 new comments.
-
Add support for selecting icons, resolves #13 w3c/contact-picker#28 (10 comments by @beverloo, @rayankans)
-
TR publications
-
19 documents published.
-
The Screen Orientation API published as a Working Draft. History of The Screen Orientation API
-
Web App Manifest published 6 times as a Working Draft. History of Web App Manifest
-
ARIA in HTML published 5 times as a Working Draft. History of ARIA in HTML
-
HTML Accessibility API Mappings 1.0 published 3 times as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
Gamepad published 3 times as a Working Draft. History of Gamepad
-
Push API published as a Working Draft. History of Push API
-
GitHub
w3c/badging
-
5 issues opened.
-
Should OS failures setting the badge reject the promise? w3c/badging#61, by @mgiuca.
-
Make setXXXBadge(undefined) set flag instead of clearing w3c/badging#60, by @mgiuca.
-
Should the badge be associated with a browsing context instead of a document? w3c/badging#59, by @mgiuca.
-
Add examples of client/document badging w3c/badging#58, by @mgiuca.
-
Do we really want to add Badge API to Navigator? w3c/badging#56, by @mgiuca.
-
-
8 issues closed.
-
Invalid scope URL needs to raise an error w3c/badging#53.
-
Determine how set() will work for "flag" mode + scope w3c/badging#52.
-
Scoping Badges is Complicated w3c/badging#43.
-
TPAC Discussion Result w3c/badging#55.
-
Separate API for tab badging vs app badging w3c/badging#49.
-
Consider separate 'Cleared' and 'Unset' values for badges. w3c/badging#42.
-
Resetting Badges w3c/badging#41.
-
Disassociate from install w3c/badging#12.
-
-
12 issues received 26 new comments.
-
Do we really want to add Badge API to Navigator? w3c/badging#56 (4 comments by @marcoscaceres, @mgiuca)
-
Should the badge be associated with a browsing context instead of a document? w3c/badging#59 (2 comments by @marcoscaceres, @mgiuca)
-
Invalid scope URL needs to raise an error w3c/badging#53 (2 comments by @fallaciousreasoning, @mgiuca)
-
Determine how set() will work for "flag" mode + scope w3c/badging#52 (2 comments by @fallaciousreasoning, @mgiuca)
-
Separate API for tab badging vs app badging w3c/badging#49 (2 comments by @fallaciousreasoning, @mgiuca)
-
Consider separate 'Cleared' and 'Unset' values for badges. w3c/badging#42 (1 comment by @fallaciousreasoning)
-
w3c/badging#12 (1 comment by @fallaciousreasoning)
-
1 pull request opened.
-
Spec rewrite: Update to new separate document/app API w3c/badging#57, by @mgiuca.
-
-
1 pull request merged.
-
Explainer: Separate APIs for URL-scoped badge vs document badge w3c/badging#51.
-
-
1 pull request closed.
-
Update explainer.md w3c/badging#48.
-
-
3 pull requests received 108 new comments.
-
Spec rewrite: Update to new separate document/app API w3c/badging#57 (85 comments by @fallaciousreasoning, @marcoscaceres, @mgiuca)
-
Explainer: Separate APIs for URL-scoped badge vs document badge w3c/badging#51 (22 comments by @marcoscaceres, @mgiuca)
-
w3c/uievents
-
4 issues opened.
-
Add support for keyboard lock to test page w3c/uievents#248, by @jamiewalch.
-
Need property which gives the (base) unmodified key w3c/uievents#247, by @tszynalski.
-
Propose the new navbeforefocus UIEvent w3c/uievents#246, by @anawhj.
-
Propose the new navbeforefocus UIEvent w3c/uievents#245, by @lgewst.
-
-
1 issue closed.
-
Propose the new navbeforefocus UIEvent w3c/uievents#245.
-
-
3 issues received 7 new comments.
w3c/using-aria
-
1 issue opened.
-
Possible addition to the 4th rule w3c/using-aria#50, by @JAWS-test.
-
w3c/ServiceWorker
-
7 issues opened.
-
Need to explain name matching rules for cache names w3c/ServiceWorker#1483, by @r12a.
-
Allow better composability of fetch handlers w3c/ServiceWorker#1482, by @devongovett.
-
VueJS dynamic imports / lazy loading supported by SW? w3c/ServiceWorker#1481, by @doorkey.
-
Service worker expiration w3c/ServiceWorker#1480, by @TomPradat.
-
Make serviceWorker.ready spec match implementations w3c/ServiceWorker#1477, by @jakearchibald.
-
Provide a way to attach data to clients w3c/ServiceWorker#1475, by @jakearchibald.
-
-
3 issues closed.
-
Why does spec set redirect's mode to error ? w3c/ServiceWorker#1366.
-
Service worker expiration w3c/ServiceWorker#1480.
-
-
10 issues received 42 new comments.
-
Top-level await integration for ServiceWorkers running modules w3c/ServiceWorker#1407 (24 comments by @annevk, @devsnek, @domenic, @jakearchibald, @littledan, @ljharb, @syg)
-
Provide a way to attach data to clients w3c/ServiceWorker#1475 (4 comments by @asutherland, @jakearchibald, @surma, @voxpelli)
-
The requested service worker becomes redundant and a new and random service worker gets requested and registered w3c/ServiceWorker#1479 (3 comments by @jakearchibald, @rishabhnigamoyo)
-
Allow better composability of fetch handlers w3c/ServiceWorker#1482 (2 comments by @devongovett, @jakearchibald)
-
w3c/ServiceWorker#204 (1 comment by @TomPradat)
-
w3c/ServiceWorker#1366 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#765 (1 comment by @kevodwyer)
-
-
2 pull requests opened.
-
Make serviceWorker.ready spec match implementations w3c/ServiceWorker#1478, by @Yannic.
-
Export ServiceWorkerGlobalScope's service worker for DOM Standards w3c/ServiceWorker#1476, by @jungkees.
-
-
1 pull request merged.
-
Export ServiceWorkerGlobalScope's service worker for DOM Standards w3c/ServiceWorker#1476.
-
-
2 pull requests received 4 new comments.
-
Make serviceWorker.ready spec match implementations w3c/ServiceWorker#1478 (3 comments by @jakearchibald, @Yannic, @ylafon)
-
Export ServiceWorkerGlobalScope's service worker for DOM Standards w3c/ServiceWorker#1476 (1 comment by @jungkees)
-
w3c/image-resource
-
6 issues opened.
-
Processing an array of image resources does not return an Array of ImageResources w3c/image-resource#8, by @rayankans.
-
Add alternative text member w3c/image-resource#7, by @aarongustafson.
-
Should this include the Fetching algorithm? w3c/image-resource#5, by @rayankans.
-
Should this include "purpose" and "platform" from Manifest (and also Bikeshed vs Respec) w3c/image-resource#4, by @mgiuca.
-
Should this include the selection algorithm? w3c/image-resource#3, by @aarongustafson.
-
Merge with WICG/imageresource? w3c/image-resource#2, by @aarongustafson.
-
-
5 issues closed.
-
Processing an array of image resources does not return an Array of ImageResources w3c/image-resource#8.
-
Should this include the Fetching algorithm? w3c/image-resource#5.
-
Should this include the selection algorithm? w3c/image-resource#3.
-
Merge with WICG/imageresource? w3c/image-resource#2.
-
Multiple size values in `sizes`? w3c/image-resource#1.
-
-
7 issues received 37 new comments.
-
Should this include the selection algorithm? w3c/image-resource#3 (14 comments by @aarongustafson, @jakearchibald, @marcoscaceres, @mgiuca, @rayankans)
-
Should this include "purpose" and "platform" from Manifest (and also Bikeshed vs Respec) w3c/image-resource#4 (11 comments by @aarongustafson, @kenchris, @marcoscaceres, @mgiuca, @NotWoods, @rayankans)
-
Multiple size values in `sizes`? w3c/image-resource#1 (4 comments by @aarongustafson, @dominickng, @NotWoods, @rayankans)
-
Should this include the Fetching algorithm? w3c/image-resource#5 (3 comments by @aarongustafson, @rayankans)
-
Processing an array of image resources does not return an Array of ImageResources w3c/image-resource#8 (1 comment by @aarongustafson)
-
-
2 pull requests opened.
-
Create a processed image resource struct. w3c/image-resource#9, by @rayankans.
-
Added in Processing an Array of Image Resources - Resolves #3 w3c/image-resource#6, by @aarongustafson.
-
-
2 pull requests merged.
-
Create a processed image resource struct. w3c/image-resource#9.
-
Added in Processing an Array of Image Resources - Resolves #3 w3c/image-resource#6.
-
-
2 pull requests received 29 new comments.
-
Added in Processing an Array of Image Resources - Resolves #3 w3c/image-resource#6 (17 comments by @aarongustafson, @marcoscaceres, @mgiuca, @rayankans)
-
Create a processed image resource struct. w3c/image-resource#9 (12 comments by @aarongustafson, @mgiuca, @NotWoods, @rayankans)
-
w3c/contact-picker
-
1 issue opened.
-
Unable to register for Origin Trial w3c/contact-picker#27, by @Exoplanet3000.
-
-
1 issue closed.
-
Unable to register for Origin Trial w3c/contact-picker#27.
-
-
3 issues received 5 new comments.
-
1 pull request opened.
-
Add support for selecting icons, resolves #13 w3c/contact-picker#28, by @rayankans.
-
-
1 pull request merged.
-
Add feature detection & create the concept of a Contacts Source. w3c/contact-picker#26.
-
w3c/gamepad
-
3 issues opened.
-
What's a good place to start contributing to the Gamepad spec? w3c/gamepad#121, by @mrmcpowned.
-
Feature policy integration w3c/gamepad#119, by @marcoscaceres.
-
Add James and Matt as spec editors w3c/gamepad#116, by @nondebug.
-
-
2 issues closed.
-
Gamepad event timing w3c/gamepad#83.
-
Add James and Matt as spec editors w3c/gamepad#116.
-
-
2 issues received 18 new comments.
-
w3c/gamepad#73 (1 comment by @mrmcpowned)
-
6 pull requests opened.
-
Spec liveness of Gamepad and GamepadButton objects (#8) w3c/gamepad#123, by @nondebug.
-
Editorial: Fix a few inconsistencies in "GamepadButton Interface" w3c/gamepad#122, by @kri.
-
Require secure context for gamepad state and events w3c/gamepad#120, by @nondebug.
-
chore(ci): use ReSpec auto-publish action w3c/gamepad#118, by @sidvishnoi.
-
Add James Hollyer and Matt Reynolds as editors w3c/gamepad#117, by @nondebug.
-
Remove Travis, use GitHub Action w3c/gamepad#115, by @sidvishnoi.
-
-
4 pull requests merged.
-
chore(ci): use ReSpec auto-publish action w3c/gamepad#118.
-
Add James Hollyer and Matt Reynolds as editors w3c/gamepad#117.
-
Remove Travis, use GitHub Action w3c/gamepad#115.
-
1 pull request closed.
-
Remove Travis, use GitHub Action w3c/gamepad#109.
-
-
1 pull request reopened.
-
Add James Hollyer and Matt Reynolds as editors w3c/gamepad#117, by @nondebug.
-
-
8 pull requests received 26 new comments.
-
Spec liveness of Gamepad and GamepadButton objects (#8) w3c/gamepad#123 (8 comments by @marcoscaceres)
-
Clarification of gamepad state from getGamepads() and connect/disconnect events w3c/gamepad#106 (1 comment by @JamesHollyer)
-
w3c/manifest
-
5 issues opened.
-
Obtaining the manifest from any context w3c/manifest#818, by @rayankans.
-
Processing steps change the types of things (type errors) w3c/manifest#817, by @mgiuca.
-
Broken reference: Valid MIME type w3c/manifest#813, by @benfrancis.
-
Inconsistent use of "terminate" vs "abort" w3c/manifest#809, by @jyasskin.
-
Clarify the purpose of `purpose: badge` w3c/manifest#808, by @NotWoods.
-
-
6 issues closed.
-
Broken reference: Valid MIME type w3c/manifest#813.
-
Inconsistent use of "terminate" vs "abort" w3c/manifest#809.
-
Richer splash screen backgrounds w3c/manifest#589.
-
Add splashscreen as a `purpose` w3c/manifest#510.
-
Clarify the purpose of `purpose: badge` w3c/manifest#808.
-
-
13 issues received 38 new comments.
-
custom padding for maskable icons w3c/manifest#805 (7 comments by @glennhartmann, @mgiuca, @NotWoods)
-
Transparent Bottom Navigation Bar w3c/manifest#804 (5 comments by @alancutter, @denaszune, @Malvoz, @NotWoods)
-
Space-separated sizes in ImageResource? w3c/manifest#807 (5 comments by @aarongustafson, @dominickng, @marcoscaceres)
-
support "Continue where you left off" and "Open a specific page or set of pages" w3c/manifest#794 (1 comment by @mfulton26)
-
w3c/manifest#589 (1 comment by @marcoscaceres)
-
w3c/manifest#465 (1 comment by @marcoscaceres)
-
Support different shortcut icon requirements/guidelines on different platforms w3c/manifest#795 (1 comment by @mgiuca)
-
6 pull requests opened.
-
chore: remove some cross referenced terms w3c/manifest#816, by @janiceshiu.
-
Fix broken specs w3c/manifest#815, by @janiceshiu.
-
Fixes #813 w3c/manifest#814, by @aarongustafson.
-
Fix typo: is -> to w3c/manifest#812, by @benfrancis.
-
Various fixes to ImageResource processing algorithms w3c/manifest#811, by @mgiuca.
-
Editorial: Consistently use abort not terminate w3c/manifest#810, by @janiceshiu.
-
-
9 pull requests merged.
-
Make BeforeInstallPrompt optional w3c/manifest#797.
-
chore: remove some cross referenced terms w3c/manifest#816.
-
Fix broken specs w3c/manifest#815.
-
Various fixes to ImageResource processing algorithms w3c/manifest#811.
-
Fixes #813 w3c/manifest#814.
-
Fix typo: is -> to w3c/manifest#812.
-
WebAppManifest itself should be top-level (for="") w3c/manifest#785.
-
Editorial: Consistently use abort not terminate w3c/manifest#810.
-
Adding myself as an editor :-) w3c/manifest#806.
-
-
11 pull requests received 39 new comments.
-
Add shortcuts feature to the explainer and spec w3c/manifest#768 (15 comments by @aarongustafson, @mgiuca)
-
Make Service Worker registration work properly (don't use outdated steps) w3c/manifest#792 (2 comments by @jyasskin, @marcoscaceres)
-
w3c/screen-orientation
-
2 issues opened.
-
Should the -secondary orientations be exposed? w3c/screen-orientation#188, by @smfr.
-
"locking" to the default orienation w3c/screen-orientation#187, by @smfr.
-
-
2 issues closed.
-
"locking" to the default orienation w3c/screen-orientation#187.
-
Specification status report for TPAC 2019 w3c/screen-orientation#185.
-
-
3 issues received 3 new comments.
-
1 pull request opened.
-
Editorial: Add an IDL Index appendix to the spec. w3c/screen-orientation#189, by @rakuco.
-
-
1 pull request merged.
-
Editorial: Add an IDL Index appendix to the spec. w3c/screen-orientation#189.
-
-
1 pull request received 1 new comment.
-
Editorial: Add an IDL Index appendix to the spec. w3c/screen-orientation#189 (1 comment by @marcoscaceres)
-
w3c/web-share
-
2 issues opened.
-
Clarify how URL should be used on platforms without dedicated URL field w3c/web-share#130, by @NotWoods.
-
Preparations for First Public Working Draft w3c/web-share#129, by @marcoscaceres.
-
-
1 issue closed.
-
Clarify how URL should be used on platforms without dedicated URL field w3c/web-share#130.
-
-
2 issues received 8 new comments.
-
Preparations for First Public Working Draft w3c/web-share#129 (6 comments by @marcoscaceres, @mgiuca)
-
Clarify how URL should be used on platforms without dedicated URL field w3c/web-share#130 (2 comments by @mgiuca)
-
-
1 pull request opened.
-
Clarify that UAs can concatenate fields like on Android. w3c/web-share#131, by @mgiuca.
-
-
1 pull request merged.
-
Clarify that UAs can concatenate fields like on Android. w3c/web-share#131.
-
-
1 pull request received 11 new comments.
-
Clarify that UAs can concatenate fields like on Android. w3c/web-share#131 (11 comments by @ewilligers, @marcoscaceres, @mgiuca, @saschanaz)
-
w3c/web-locks
-
1 issue received 1 new comment.
-
w3c/web-locks#55 (1 comment by @inexorabletash)
-
-
1 pull request opened.
-
Use IDL/Infra terms, simplify text. w3c/web-locks#60, by @inexorabletash.
-
-
1 pull request merged.
-
Use IDL/Infra terms, simplify text. w3c/web-locks#60.
-
-
1 pull request received 3 new comments.
w3c/FileAPI
-
1 issue closed.
-
Specification status report for TPAC 2019 w3c/FileAPI#138.
-
-
1 issue received 1 new comment.
w3c/webappswg
-
2 issues opened.
-
Send a CFC for Screen Orientation spec to go to CR w3c/webappswg#24, by @marcoscaceres.
-
Create a template for CR criteria w3c/webappswg#23, by @marcoscaceres.
-
-
3 issues closed.
-
Make sure all WD specs are on auto publish w3c/webappswg#6.
-
Archive File System API w3c/webappswg#20.
-
RFC: TPAC meeting structure w3c/webappswg#10.
-
-
4 issues received 6 new comments.
w3c/push-api
-
1 issue closed.
-
"handle functional event" no longer a thing w3c/push-api#315.
-
-
1 issue received 1 new comment.
-
w3c/push-api#302 (1 comment by @borisavz)
-
-
1 pull request opened.
-
Replaced handle functional event with Fire functional event w3c/push-api#321, by @sonakshisaxena1.
-
-
1 pull request merged.
-
Replaced handle functional event with Fire functional event w3c/push-api#321.
-
-
1 pull request received 5 new comments.
-
Replaced handle functional event with Fire functional event w3c/push-api#321 (5 comments by @marcoscaceres)
-
w3c/IndexedDB
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Add "Repository" metadata w3c/IndexedDB#306, by @tabatkins.
-
-
1 pull request merged.
-
Add "Repository" metadata w3c/IndexedDB#306.
-
-
1 pull request received 1 new comment.
TR publications
-
21 documents published.
-
ARIA in HTML published 3 times as a Working Draft. History of ARIA in HTML
-
Web App Manifest published 5 times as a Working Draft. History of Web App Manifest
-
Gamepad published 4 times as a Working Draft. History of Gamepad
-
HTML Accessibility API Mappings 1.0 published 7 times as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
File API published as a Working Draft. History of File API
-
The Screen Orientation API published as a Working Draft. History of The Screen Orientation API
-
Participants
-
3 organizations joined.
-
Airbnb Inc joined.
-
Sony Group Corporation joined.
-
Samsung Electronics Co., Ltd. joined.
-
GitHub
w3c/manifest
-
15 issues opened.
-
Space-separated sizes in ImageResource? w3c/manifest#807, by @aarongustafson.
-
custom padding for maskable icons w3c/manifest#805, by @glennhartmann.
-
Transparent Bottom Navigation Bar w3c/manifest#804, by @denaszune.
-
Clarify ServiceWorkerRegistrationObject’s purpose w3c/manifest#800, by @aarongustafson.
-
Required WebAppManifest Member clarification w3c/manifest#799, by @moonmeister.
-
Some mechanism to maybe define a feature policy w3c/manifest#798, by @marcoscaceres.
-
make BeforeInstallPrompt optional w3c/manifest#796, by @marcoscaceres.
-
Support different shortcut icon requirements/guidelines on different platforms w3c/manifest#795, by @mgiuca.
-
support "Continue where you left off" and "Open a specific page or set of pages" w3c/manifest#794, by @mfulton26.
-
Scope should remove the query and fragment at parse time w3c/manifest#793, by @mgiuca.
-
Refactor the manifest install flow w3c/manifest#788, by @mgiuca.
-
BeforeInstallPromptEvent.prompt() does not actually perform installation w3c/manifest#786, by @mgiuca.
-
-
21 issues closed.
-
Refactor the manifest install flow w3c/manifest#788.
-
BeforeInstallPromptEvent.prompt() does not actually perform installation w3c/manifest#786.
-
manifest.webmanifest or manifest.json w3c/manifest#689.
-
Clarify service worker member, and when it installs w3c/manifest#640.
-
Combine Origin Policy mechanism with the Web App Manifest? w3c/manifest#500.
-
Required WebAppManifest Member clarification w3c/manifest#799.
-
Dynamic Theme Color w3c/manifest#779.
-
Specification status report for TPAC 2019 w3c/manifest#782.
-
we refer to ASCII lowercase from WHATWG infra spec but Trim from ES spec w3c/manifest#600.
-
Include Minimal Store/Catalog MetaData in Manifest w3c/manifest#448.
-
Should appinstalled and beforeinstallprompt events be optional? w3c/manifest#699.
-
shortcuts to content vs shortcut to app w3c/manifest#167.
-
Validate ReSpec in CI w3c/manifest#733.
-
Expose API for managing Web App aspects w3c/manifest#472.
-
Introduce window.Application global object aside manifest.webmanifest w3c/manifest#769.
-
Adaptive icons on Android 9 w3c/manifest#783.
-
beforeinstallprompt not fire with "prefer_related_applications": true w3c/manifest#780.
-
-
2 issues reopened.
-
IDL: Make name required w3c/manifest#622, by @mgiuca.
-
shortcuts to content vs shortcut to app w3c/manifest#167, by @marcoscaceres.
-
-
42 issues received 131 new comments.
-
w3c/manifest#399 (16 comments by @aarongustafson, @alancutter, @dominickng, @lknik, @mgiuca, @npdoty, @othermaciej)
-
Specification status report for TPAC 2019 w3c/manifest#782 (11 comments by @aarongustafson, @christianliebel, @dominickng, @kenchris, @marcoscaceres, @mgiuca, @tomayac)
-
Clarify ServiceWorkerRegistrationObject’s purpose w3c/manifest#800 (9 comments by @aarongustafson, @boyofgreen, @christianliebel, @kenchris, @mgiuca)
-
Clarify behaviour of a page linking to a manifest that is not within scope of that manifest w3c/manifest#784 (9 comments by @aarongustafson, @christianliebel, @dominickng, @mgiuca)
-
Support different shortcut icon requirements/guidelines on different platforms w3c/manifest#795 (5 comments by @beverloo, @mgiuca)
-
w3c/manifest#763 (5 comments by @aarongustafson, @christianliebel, @fallaciousreasoning, @kenzkiran, @marcoscaceres)
-
Adaptive icons on Android 9 w3c/manifest#783 (5 comments by @dominickng, @kenchris, @marcoscaceres, @mgiuca, @TorstenDittmann)
-
Some mechanism to maybe define a feature policy w3c/manifest#798 (4 comments by @aarongustafson, @dominickng, @fallaciousreasoning, @mgiuca)
-
support "Continue where you left off" and "Open a specific page or set of pages" w3c/manifest#794 (3 comments by @alancutter, @dominickng)
-
Scope should remove the query and fragment at parse time w3c/manifest#793 (3 comments by @aarongustafson, @fallaciousreasoning, @mgiuca)
-
beforeinstallprompt not fire with "prefer_related_applications": true w3c/manifest#780 (2 comments by @dominickng, @marcoscaceres)
-
Introduce window.Application global object aside manifest.webmanifest w3c/manifest#769 (2 comments by @marcoscaceres)
-
w3c/manifest#669 (1 comment by @mgiuca)
-
Steps to install the web application does not take into account whether the installation process was canceled w3c/manifest#787 (1 comment by @mgiuca)
-
w3c/manifest#600 (1 comment by @aarongustafson)
-
w3c/manifest#479 (1 comment by @aarongustafson)
-
w3c/manifest#465 (1 comment by @aarongustafson)
-
w3c/manifest#582 (1 comment by @aarongustafson)
-
w3c/manifest#758 (1 comment by @aarongustafson)
-
w3c/manifest#733 (1 comment by @marcoscaceres)
-
w3c/manifest#603 (1 comment by @marcoscaceres)
-
w3c/manifest#472 (1 comment by @marcoscaceres)
-
w3c/manifest#611 (1 comment by @marcoscaceres)
-
-
9 pull requests opened.
-
Adding myself as an editor :-) w3c/manifest#806, by @aarongustafson.
-
Editorial: Use vectors for maskable icon w3c/manifest#803, by @NotWoods.
-
Editorial: add note on file extension w3c/manifest#802, by @christianliebel.
-
Link fixes 2019-09-20 w3c/manifest#801, by @aarongustafson.
-
Make BeforeInstallPrompt optional w3c/manifest#797, by @marcoscaceres.
-
Make Service Worker registration work properly (don't use outdated steps) w3c/manifest#792, by @mgiuca.
-
Require document to be in scope to be styled by the manifest w3c/manifest#791, by @mgiuca.
-
Rewrite installation process and install prompting logic w3c/manifest#790, by @mgiuca.
-
WebAppManifest itself should be top-level (for="") w3c/manifest#785, by @jyasskin.
-
-
3 pull requests merged.
-
Rewrite installation process and install prompting logic w3c/manifest#790.
-
Editorial: Use vectors for maskable icon w3c/manifest#803.
-
Editorial: add note on file extension w3c/manifest#802.
-
-
1 pull request closed.
-
Link fixes 2019-09-20 w3c/manifest#801.
-
-
1 pull request reopened.
-
WebAppManifest itself should be top-level (for="") w3c/manifest#785, by @jyasskin.
-
-
11 pull requests received 86 new comments.
-
Add shortcuts feature to the explainer and spec w3c/manifest#768 (27 comments by @aarongustafson, @beverloo, @christianliebel, @hjrchung, @marcoscaceres, @mgiuca, @NotWoods)
-
Rewrite installation process and install prompting logic w3c/manifest#790 (25 comments by @dominickng, @marcoscaceres, @mgiuca)
-
Make Service Worker registration work properly (don't use outdated steps) w3c/manifest#792 (7 comments by @kenchris, @marcoscaceres, @mgiuca)
-
Require document to be in scope to be styled by the manifest w3c/manifest#791 (5 comments by @dominickng, @mgiuca)
-
w3c/manifest#710 (1 comment by @aarongustafson)
-
w3c/image-resource
-
1 issue opened.
-
Multiple size values in `sizes`? w3c/image-resource#1, by @aarongustafson.
-
w3c/IndexedDB
-
5 issues opened.
-
Allow indexing on Request/Response properties w3c/IndexedDB#305, by @inexorabletash.
-
Allow version change transactions w/o modifying version number w3c/IndexedDB#304, by @inexorabletash.
-
Combining cursors / query execution engine w3c/IndexedDB#298, by @pwnall.
-
use browser data max storage? w3c/IndexedDB#295, by @yushengling.
-
No longer need to escape _includes w3c/IndexedDB#294, by @inexorabletash.
-
-
28 issues closed.
-
[IndexedDB] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/IndexedDB#288.
-
No longer need to escape _includes w3c/IndexedDB#294.
-
lastModifiedDate on File is not a thing w3c/IndexedDB#215.
-
use browser data max storage? w3c/IndexedDB#295.
-
Promise-based API w3c/IndexedDB#42.
-
Support transaction timeouts w3c/IndexedDB#43.
-
RegExp search w3c/IndexedDB#46.
-
Allow cancelling a versionchange event w3c/IndexedDB#52.
-
Support Files stored by reference w3c/IndexedDB#56.
-
Support URLs into records w3c/IndexedDB#57.
-
JSON schema specification w3c/IndexedDB#64.
-
Allow delete() on index w3c/IndexedDB#68.
-
"Join" queries on multiple object stores w3c/IndexedDB#92.
-
Introduce a more general query mechanism beyond keys/ranges w3c/IndexedDB#45.
-
Allow sorting within indexes w3c/IndexedDB#138.
-
Add caniuse panels w3c/IndexedDB#159.
-
index sorting w3c/IndexedDB#173.
-
Report data loss to script w3c/IndexedDB#30.
-
Grant access to other origins w3c/IndexedDB#60.
-
Encrypted storage w3c/IndexedDB#191.
-
Expiry of databases w3c/IndexedDB#205.
-
Site-agnostic databases based on `registerProtocolHandler` w3c/IndexedDB#264.
-
Specification status report for TPAC 2019 w3c/IndexedDB#290.
-
Update to constructor operations w3c/IndexedDB#293.
-
-
49 issues received 75 new comments.
-
[IndexedDB] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/IndexedDB#288 (3 comments by @inexorabletash)
-
w3c/IndexedDB#253 (2 comments by @inexorabletash)
-
w3c/IndexedDB#264 (2 comments by @inexorabletash)
-
w3c/IndexedDB#206 (2 comments by @inexorabletash)
-
w3c/IndexedDB#42 (1 comment by @inexorabletash)
-
w3c/IndexedDB#43 (1 comment by @inexorabletash)
-
w3c/IndexedDB#44 (1 comment by @inexorabletash)
-
w3c/IndexedDB#46 (1 comment by @inexorabletash)
-
w3c/IndexedDB#47 (1 comment by @inexorabletash)
-
w3c/IndexedDB#52 (1 comment by @inexorabletash)
-
w3c/IndexedDB#53 (1 comment by @inexorabletash)
-
w3c/IndexedDB#56 (1 comment by @inexorabletash)
-
w3c/IndexedDB#57 (1 comment by @inexorabletash)
-
w3c/IndexedDB#62 (1 comment by @inexorabletash)
-
w3c/IndexedDB#64 (1 comment by @inexorabletash)
-
w3c/IndexedDB#68 (1 comment by @inexorabletash)
-
w3c/IndexedDB#72 (1 comment by @inexorabletash)
-
w3c/IndexedDB#92 (1 comment by @inexorabletash)
-
w3c/IndexedDB#45 (1 comment by @inexorabletash)
-
w3c/IndexedDB#76 (1 comment by @inexorabletash)
-
w3c/IndexedDB#138 (1 comment by @inexorabletash)
-
w3c/IndexedDB#159 (1 comment by @inexorabletash)
-
w3c/IndexedDB#173 (1 comment by @inexorabletash)
-
w3c/IndexedDB#204 (1 comment by @inexorabletash)
-
w3c/IndexedDB#211 (1 comment by @inexorabletash)
-
w3c/IndexedDB#223 (1 comment by @dmurph)
-
w3c/IndexedDB#224 (1 comment by @dmurph)
-
w3c/IndexedDB#230 (1 comment by @inexorabletash)
-
w3c/IndexedDB#237 (1 comment by @inexorabletash)
-
w3c/IndexedDB#30 (1 comment by @inexorabletash)
-
w3c/IndexedDB#60 (1 comment by @inexorabletash)
-
w3c/IndexedDB#191 (1 comment by @inexorabletash)
-
w3c/IndexedDB#205 (1 comment by @inexorabletash)
-
w3c/IndexedDB#71 (1 comment by @inexorabletash)
-
w3c/IndexedDB#69 (1 comment by @inexorabletash)
-
w3c/IndexedDB#34 (1 comment by @inexorabletash)
-
w3c/IndexedDB#19 (1 comment by @inexorabletash)
-
7 pull requests opened.
-
Use IDL this w3c/IndexedDB#303, by @inexorabletash.
-
Sketch out IDBCursor.close() w3c/IndexedDB#302, by @inexorabletash.
-
Sketch out spec text for transaction durability option w3c/IndexedDB#301, by @inexorabletash.
-
Remove lastModifiedDate handling w3c/IndexedDB#300, by @inexorabletash.
-
Remove WebIDL escaping of includes() method w3c/IndexedDB#299, by @inexorabletash.
-
Replace var with let/const in examples. w3c/IndexedDB#297, by @inexorabletash.
-
Editorial: use new constructor syntax from WebIDL w3c/IndexedDB#296, by @marcoscaceres.
-
-
5 pull requests merged.
-
Use IDL this w3c/IndexedDB#303.
-
Replace var with let/const in examples. w3c/IndexedDB#297.
-
Remove WebIDL escaping of includes() method w3c/IndexedDB#299.
-
Remove lastModifiedDate handling w3c/IndexedDB#300.
-
Editorial: use new constructor syntax from WebIDL w3c/IndexedDB#296.
-
-
6 pull requests received 14 new comments.
-
Remove WebIDL escaping of includes() method w3c/IndexedDB#299 (6 comments by @aliams, @inexorabletash)
-
Sketch out spec text for transaction durability option w3c/IndexedDB#301 (3 comments by @asutherland, @inexorabletash, @pwnall)
-
w3c/gamepad
-
3 issues opened.
-
Rewrite things as algorithms... w3c/gamepad#114, by @marcoscaceres.
-
Restrict getGamepads() to [SecureContext] w3c/gamepad#113, by @marcoscaceres.
-
-
3 issues closed.
-
Clarify what "up" and "down" mean for input axes w3c/gamepad#94.
-
Update to constructor operations w3c/gamepad#102.
-
Update spec to new IDL syntax for optional dictionaries w3c/gamepad#101.
-
-
6 issues received 10 new comments.
-
w3c/gamepad#70 (1 comment by @marcoscaceres)
-
w3c/gamepad#82 (1 comment by @knyg)
-
Update spec to new IDL syntax for optional dictionaries w3c/gamepad#101 (1 comment by @marcoscaceres)
-
9 pull requests opened.
-
Add permission policy integration w3c/gamepad#112, by @marcoscaceres.
-
Editorial: add whitespace in Web IDL w3c/gamepad#111, by @foolip.
-
Remove Travis, use GitHub Action w3c/gamepad#109, by @sidvishnoi.
-
Editorial: reduce dependencies using newer syntax w3c/gamepad#108, by @sidvishnoi.
-
Define user activation and added references in getGamepads and gamepa… w3c/gamepad#107, by @knyg.
-
Clarification of gamepad state from getGamepads() and connect/disconnect events w3c/gamepad#106, by @sagoston.
-
Clarify -1.0 and 1.0 values based on controller orientation w3c/gamepad#105, by @knyg.
-
Specify length of array when controllers are connected/disconnected. w3c/gamepad#104, by @knyg.
-
refactor: use new IDL constructor + fix link w3c/gamepad#103, by @marcoscaceres.
-
-
4 pull requests merged.
-
Editorial: reduce dependencies using newer syntax w3c/gamepad#108.
-
Editorial: add whitespace in Web IDL w3c/gamepad#111.
-
Clarify -1.0 and 1.0 values based on controller orientation w3c/gamepad#105.
-
refactor: use new IDL constructor + fix link w3c/gamepad#103.
-
-
1 pull request closed.
-
Do not permit unique info in ID w3c/gamepad#96.
-
-
4 pull requests reopened.
-
Editorial: reduce dependencies using newer syntax w3c/gamepad#108, by @marcoscaceres.
-
Clarification of gamepad state from getGamepads() and connect/disconnect events w3c/gamepad#106, by @sagoston.
-
Define user activation and added references in getGamepads and gamepa… w3c/gamepad#107, by @marcoscaceres.
-
Clarify -1.0 and 1.0 values based on controller orientation w3c/gamepad#105, by @marcoscaceres.
-
-
7 pull requests received 23 new comments.
-
Specify length of array when controllers are connected/disconnected. w3c/gamepad#104 (5 comments by @sagoston, @ylafon)
-
Editorial: reduce dependencies using newer syntax w3c/gamepad#108 (2 comments by @marcoscaceres, @sagoston)
-
Clarify -1.0 and 1.0 values based on controller orientation w3c/gamepad#105 (2 comments by @sagoston)
-
Define user activation and added references in getGamepads and gamepa… w3c/gamepad#107 (1 comment by @marcoscaceres)
w3c/web-share
-
3 issues opened.
-
Explicitly state that UA can reject file based on its type w3c/web-share#127, by @mgiuca.
-
Sharing service unavailable should reject with NotSupportedError w3c/web-share#126, by @marcoscaceres.
-
Sharing data: URLs w3c/web-share#123, by @marcoscaceres.
-
-
4 issues closed.
-
canShare(data) without filepicker w3c/web-share#114.
-
Sharing data: URLs w3c/web-share#123.
-
Clarifying behavior of multiple simultaneous shares w3c/web-share#110.
-
Distinguishing between data errors and user abort w3c/web-share#112.
-
-
3 issues received 7 new comments.
-
4 pull requests opened.
-
Editorial: don't early abort w3c/web-share#128, by @marcoscaceres.
-
editorial: ReSpec fixes + enhancements w3c/web-share#125, by @marcoscaceres.
-
editorial: URLs resolved against base, not location w3c/web-share#124, by @marcoscaceres.
-
s/wicg/w3c/ w3c/web-share#122, by @tomayac.
-
-
5 pull requests merged.
-
Editorial: don't early abort w3c/web-share#128.
-
s/wicg/w3c/ w3c/web-share#122.
-
Introduce [[sharePromise]] internal slot w3c/web-share#113.
-
editorial: URLs resolved against base, not location w3c/web-share#124.
-
editorial: ReSpec fixes + enhancements w3c/web-share#125.
-
-
1 pull request closed.
-
Do 'triggered by user activation' check earlier w3c/web-share#118.
-
-
1 pull request reopened.
-
Do 'triggered by user activation' check earlier w3c/web-share#118, by @marcoscaceres.
-
-
4 pull requests received 17 new comments.
-
Do 'triggered by user activation' check earlier w3c/web-share#118 (9 comments by @ewilligers, @marcoscaceres, @mgiuca)
-
editorial: ReSpec fixes + enhancements w3c/web-share#125 (2 comments by @ewilligers, @marcoscaceres)
-
w3c/badging
-
4 issues opened.
-
TPAC Discussion Result w3c/badging#55, by @fallaciousreasoning.
-
[Badging] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/badging#54, by @fallaciousreasoning.
-
Invalid scope URL needs to raise an error w3c/badging#53, by @mgiuca.
-
Determine how set() will work for "flag" mode + scope w3c/badging#52, by @mgiuca.
-
-
4 issues closed.
-
handling failure w3c/badging#2.
-
IPC calls for promise w3c/badging#35.
-
[Badging] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/badging#54.
-
Scope of badging w3c/badging#5.
-
-
8 issues received 21 new comments.
-
Determine how set() will work for "flag" mode + scope w3c/badging#52 (7 comments by @fallaciousreasoning, @g-ortuno, @mgiuca)
-
[Badging] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/badging#54 (2 comments by @fallaciousreasoning)
-
Invalid scope URL needs to raise an error w3c/badging#53 (2 comments by @fallaciousreasoning, @mgiuca)
-
w3c/badging#2 (1 comment by @mgiuca)
-
-
1 pull request received 31 new comments.
-
Explainer: Separate APIs for URL-scoped badge vs document badge w3c/badging#51 (31 comments by @fallaciousreasoning, @marcoscaceres, @mgiuca)
-
w3c/ServiceWorker
-
6 issues opened.
-
NavigationPreloadManager.setHeader spec should verify valid HTTP header values w3c/ServiceWorker#1474, by @perryjiang.
-
"display-mode" information on navigation requests w3c/ServiceWorker#1473, by @NekR.
-
The return value for update() is wrong in WebIDL w3c/ServiceWorker#1472, by @philipwalton.
-
Relaying service worker state when serving Clear-Site-Data w3c/ServiceWorker#1471, by @asakusuma.
-
Consider deprecating the ability for scope to match query parameters w3c/ServiceWorker#1469, by @mgiuca.
-
scope pattern matching w3c/ServiceWorker#1468, by @wanderview.
-
-
9 issues closed.
-
content-type in csp report on fetch is missed w3c/ServiceWorker#1449.
-
Hiding add to homescreen minibar for certain urls. w3c/ServiceWorker#1375.
-
Measuring performance with and without Service Worker w3c/ServiceWorker#1462.
-
skipWaiting issue on different registrations w3c/ServiceWorker#561.
-
Consistency of ServiceWorkerClient fields w3c/ServiceWorker#500.
-
Update to constructor operations w3c/ServiceWorker#1464.
-
Export "clear registration" w3c/ServiceWorker#1410.
-
"waiting for all" definition changed w3c/ServiceWorker#1363.
-
Clarify "waiting for all" in Install w3c/ServiceWorker#1461.
-
-
1 issue reopened.
-
Clarification on what happens during a terminated activation w3c/ServiceWorker#1372, by @jakearchibald.
-
-
31 issues received 86 new comments.
-
CFC: Transition V1 spec to CR w3c/ServiceWorker#1458 (8 comments by @jakearchibald, @ylafon, @youennf)
-
Top-level await integration for ServiceWorkers running modules w3c/ServiceWorker#1407 (7 comments by @asutherland, @jakearchibald, @Jamesernator, @littledan, @ljharb)
-
support efficient offline redirects w3c/ServiceWorker#1457 (6 comments by @jakearchibald, @ralphch0, @wanderview)
-
Create F2F agenda - 16 September 2019 w3c/ServiceWorker#1460 (6 comments by @jakearchibald, @mfalken, @wanderview, @yutakahirano)
-
Should the order of registrations returned by getRegistrations() be sorted by scope? w3c/ServiceWorker#1465 (5 comments by @asutherland, @mfalken, @youennf)
-
NavigationPreloadManager.setHeader spec should verify valid HTTP header values w3c/ServiceWorker#1474 (3 comments by @annevk)
-
Consider deprecating the ability for scope to match query parameters w3c/ServiceWorker#1469 (3 comments by @jakearchibald, @mgiuca, @wanderview)
-
spec says cache should return responses with immutable headers, but no browser does that w3c/ServiceWorker#1456 (3 comments by @annevk, @jakearchibald)
-
A way to specify a pattern of destination URLs to hit/skip SW w3c/ServiceWorker#1454 (2 comments by @jakearchibald)
-
w3c/ServiceWorker#1038 (2 comments by @jakearchibald)
-
Relaying service worker state when serving Clear-Site-Data w3c/ServiceWorker#1471 (2 comments by @asakusuma, @asutherland)
-
w3c/ServiceWorker#1366 (1 comment by @TomPradat)
-
w3c/ServiceWorker#765 (1 comment by @zkrige)
-
w3c/ServiceWorker#1373 (1 comment by @fallaciousreasoning)
-
w3c/ServiceWorker#1375 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#693 (1 comment by @jakearchibald)
-
Measuring performance with and without Service Worker w3c/ServiceWorker#1462 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#1370 (1 comment by @jakearchibald)
-
Registering service workers for unique origins? w3c/ServiceWorker#1437 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#561 (1 comment by @mfalken)
-
w3c/ServiceWorker#500 (1 comment by @mfalken)
-
w3c/ServiceWorker#626 (1 comment by @jakearchibald)
-
3 pull requests opened.
-
Updating constructor definitions w3c/ServiceWorker#1470, by @jakearchibald.
-
Updating use of promises w3c/ServiceWorker#1467, by @jakearchibald.
-
Fixing refs w3c/ServiceWorker#1466, by @jakearchibald.
-
-
5 pull requests merged.
-
Add a note about termination during activation. w3c/ServiceWorker#1451.
-
Updating constructor definitions w3c/ServiceWorker#1470.
-
Updating use of promises w3c/ServiceWorker#1467.
-
Fixing refs w3c/ServiceWorker#1466.
-
Editorial: Update 'wait for all' usage. w3c/ServiceWorker#1463.
-
-
1 pull request closed.
-
Experimenting with abortable algorithms w3c/ServiceWorker#1443.
-
-
7 pull requests received 22 new comments.
-
Add an option to include frozen documents. w3c/ServiceWorker#1442 (8 comments by @dtapuska, @jakearchibald, @wanderview, @youennf)
-
Editorial: Update 'wait for all' usage. w3c/ServiceWorker#1463 (5 comments by @jakearchibald, @mfalken)
-
Handle asynchronous modules (top-level await). w3c/ServiceWorker#1444 (3 comments by @annevk, @littledan, @Ms2ger)
-
w3c/pointerlock
-
1 issue opened.
-
Allow hardware cursor while in pointer lock w3c/pointerlock#52, by @vans163.
-
-
2 issues received 3 new comments.
-
Specification status report for TPAC 2019 w3c/pointerlock#50 (2 comments by @marcoscaceres, @NavidZ)
-
w3c/pointerlock#36 (1 comment by @NavidZ)
-
w3c/contact-picker
-
1 issue opened.
-
Iterator getter is not callable w3c/contact-picker#25, by @ashinzekene.
-
-
1 issue closed.
-
Iterator getter is not callable w3c/contact-picker#25.
-
-
2 issues received 7 new comments.
-
2 pull requests opened.
-
Add feature detection & create the concept of a Contacts Source. w3c/contact-picker#26, by @rayankans.
-
Support sharing addresses w3c/contact-picker#24, by @rayankans.
-
-
1 pull request merged.
-
Support sharing addresses w3c/contact-picker#24.
-
-
2 pull requests received 4 new comments.
-
Add feature detection & create the concept of a Contacts Source. w3c/contact-picker#26 (1 comment by @rayankans)
w3c/FileAPI
-
1 issue opened.
-
Put policies in the blob URL store w3c/FileAPI#142, by @annevk.
-
-
1 issue closed.
-
Update to constructor operations w3c/FileAPI#139.
-
-
3 issues received 5 new comments.
-
Consider Blob.fromStream (returns a Promise<Blob>) w3c/FileAPI#140 (2 comments by @annevk, @mkruisselbrink)
-
1 pull request opened.
-
Change Constructor extAttr to constructor() op w3c/FileAPI#141, by @marcoscaceres.
-
-
1 pull request merged.
-
Change Constructor extAttr to constructor() op w3c/FileAPI#141.
-
w3c/push-api
-
1 issue closed.
-
Update to constructor operations w3c/push-api#318.
-
-
2 issues received 3 new comments.
-
Specification status report for TPAC 2019 w3c/push-api#316 (2 comments by @beverloo, @marcoscaceres)
-
-
1 pull request opened.
-
Editorial: subscription unregistration happens magically w3c/push-api#320, by @marcoscaceres.
-
-
2 pull requests merged.
-
Editorial: subscription unregistration happens magically w3c/push-api#320.
-
Editorial: use new constructor IDL syntax w3c/push-api#319.
-
-
1 pull request received 2 new comments.
w3c/webappswg
-
3 issues opened.
-
Indexed DB in list of specs? w3c/webappswg#22, by @inexorabletash.
-
Superseded Selectors API w3c/webappswg#21, by @dontcallmedom.
-
Archive File System API w3c/webappswg#20, by @marcoscaceres.
-
-
1 issue closed.
-
Indexed DB in list of specs? w3c/webappswg#22.
-
-
2 issues received 8 new comments.
w3c/screen-orientation
-
3 issues closed.
-
Clarification regarding locking the screen orientation w3c/screen-orientation#143.
-
Steps for updating orientation information are misleading w3c/screen-orientation#100.
-
The responsible document w3c/screen-orientation#146.
-
-
7 issues received 7 new comments.
-
w3c/screen-orientation#151 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#143 (1 comment by @marcoscaceres)
-
lock() should not fail if another lock() is called in the change event w3c/screen-orientation#184 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#77 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#100 (1 comment by @marcoscaceres)
-
w3c/screen-orientation#146 (1 comment by @marcoscaceres)
w3c/uievents
-
1 issue received 3 new comments.
-
Specification status report for TPAC 2019 w3c/uievents#242 (3 comments by @garykac, @marcoscaceres, @travisleithead)
-
TR publications
-
10 documents published.
-
Pointer Lock 2.0 published as a Working Draft. History of Pointer Lock 2.0
-
Gamepad published 4 times as a Working Draft. History of Gamepad
-
Web App Manifest published 4 times as a Working Draft. History of Web App Manifest
-
Selection API published as a Working Draft. History of Selection API
-
Participants
-
1 participant joined.
-
Jan Miksovsky (W3C Invited Experts) joined.
-
GitHub
w3c/pointerlock
-
1 issue opened.
-
Specification status report for TPAC 2019 w3c/pointerlock#50, by @LJWatson.
-
-
1 issue received 1 new comment.
-
w3c/pointerlock#36 (1 comment by @smaug----)
-
-
1 pull request opened.
-
Editorial: Update the list of acknowledgments from commit history w3c/pointerlock#51, by @NavidZ.
-
-
1 pull request merged.
-
Editorial: Update the list of acknowledgments from commit history w3c/pointerlock#51.
-
-
1 pull request received 8 new comments.
-
Add lock options to requestPointerLock w3c/pointerlock#49 (8 comments by @marcoscaceres, @NavidZ, @scheib, @smaug----)
-
w3c/FileAPI
-
4 issues opened.
-
Consider Blob.fromStream (returns a Promise<Blob>) w3c/FileAPI#140, by @domenic.
-
Update to constructor operations w3c/FileAPI#139, by @Ms2ger.
-
Specification status report for TPAC 2019 w3c/FileAPI#138, by @LJWatson.
-
[FileAPI] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/FileAPI#137, by @dmurph.
-
-
2 issues received 6 new comments.
-
[FileAPI] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/FileAPI#137 (4 comments by @annevk, @dmurph, @mkruisselbrink)
-
w3c/ServiceWorker
-
8 issues opened.
-
Should the order of registrations returned by getRegistrations() be sorted by scope? w3c/ServiceWorker#1465, by @makotoshimazu.
-
Update to constructor operations w3c/ServiceWorker#1464, by @Ms2ger.
-
Measuring performance with and without Service Worker w3c/ServiceWorker#1462, by @aashishbarnwal.
-
Clarify "waiting for all" in Install w3c/ServiceWorker#1461, by @Ms2ger.
-
Create F2F agenda - 16 September 2019 w3c/ServiceWorker#1460, by @mfalken.
-
CFC: Transition V1 spec to CR w3c/ServiceWorker#1458, by @jakearchibald.
-
support efficient offline redirects w3c/ServiceWorker#1457, by @wanderview.
-
spec says cache should return responses with immutable headers, but no browser does that w3c/ServiceWorker#1456, by @wanderview.
-
-
13 issues received 45 new comments.
-
A way to specify a pattern of destination URLs to hit/skip SW w3c/ServiceWorker#1454 (12 comments by @asutherland, @jakearchibald, @kinu, @makotoshimazu, @wanderview)
-
support efficient offline redirects w3c/ServiceWorker#1457 (10 comments by @annevk, @asutherland, @wanderview)
-
Create F2F agenda - 16 September 2019 w3c/ServiceWorker#1460 (4 comments by @asakusuma, @mfalken, @wanderview)
-
Measuring performance with and without Service Worker w3c/ServiceWorker#1462 (2 comments by @aashishbarnwal, @wanderview)
-
w3c/ServiceWorker#947 (1 comment by @mohammad-masud)
-
w3c/ServiceWorker#693 (1 comment by @loganpowell)
-
w3c/ServiceWorker#882 (1 comment by @jungkees)
-
w3c/ServiceWorker#1372 (1 comment by @makotoshimazu)
-
-
3 pull requests opened.
-
Editorial: Update 'wait for all' usage. w3c/ServiceWorker#1463, by @Ms2ger.
-
Fix a typo w3c/ServiceWorker#1459, by @jungkees.
-
Clarify determination of active service worker and spec plan w3c/ServiceWorker#1455, by @jungkees.
-
-
4 pull requests merged.
-
Fix a typo w3c/ServiceWorker#1459.
-
Clarify determination of active service worker and spec plan w3c/ServiceWorker#1455.
-
Define service worker events w3c/ServiceWorker#1452.
-
Set default value of optional dictionary to {} w3c/ServiceWorker#1448.
-
-
3 pull requests received 6 new comments.
-
Editorial: Update 'wait for all' usage. w3c/ServiceWorker#1463 (3 comments by @mfalken, @Ms2ger, @sideshowbarker)
-
Clarify determination of active service worker and spec plan w3c/ServiceWorker#1455 (2 comments by @jakearchibald, @jungkees)
-
w3c/badging
-
1 issue opened.
-
Separate API for tab badging vs app badging w3c/badging#49, by @mgiuca.
-
-
1 issue closed.
-
Talk a bit more about app vs. tab? w3c/badging#1.
-
-
4 issues received 8 new comments.
-
w3c/badging#1 (1 comment by @mgiuca)
-
4 pull requests opened.
-
Explainer: Separate APIs for URL-scoped badge vs document badge w3c/badging#51, by @mgiuca.
-
Respond to TAG feedback w3c/badging#50, by @mgiuca.
-
Update explainer.md w3c/badging#48, by @marcoscaceres.
-
Rework explainer w3c/badging#47, by @mgiuca.
-
-
2 pull requests merged.
-
Respond to TAG feedback w3c/badging#50.
-
Rework explainer w3c/badging#47.
-
-
4 pull requests received 85 new comments.
-
Explainer: Separate APIs for URL-scoped badge vs document badge w3c/badging#51 (1 comment by @marcoscaceres)
w3c/push-api
-
4 issues opened.
-
Update to constructor operations w3c/push-api#318, by @Ms2ger.
-
Specification status report for TPAC 2019 w3c/push-api#316, by @LJWatson.
-
"handle functional event" no longer a thing w3c/push-api#315, by @marcoscaceres.
-
How do I authenticate a user w3c/push-api#314, by @ghost.
-
-
2 pull requests opened.
-
Editorial: use new constructor IDL syntax w3c/push-api#319, by @marcoscaceres.
-
Remove errant character w3c/push-api#317, by @martinthomson.
-
-
1 pull request merged.
-
Remove errant character w3c/push-api#317.
-
-
2 pull requests received 2 new comments.
w3c/screen-orientation
-
3 issues opened.
-
Rotate progress event w3c/screen-orientation#186, by @DongHyunSong.
-
Specification status report for TPAC 2019 w3c/screen-orientation#185, by @LJWatson.
-
lock() should not fail if another lock() is called in the change event w3c/screen-orientation#184, by @mounirlamouri.
-
-
1 issue closed.
-
Rotate progress event w3c/screen-orientation#186.
-
-
2 issues received 7 new comments.
-
lock() should not fail if another lock() is called in the change event w3c/screen-orientation#184 (2 comments by @marcoscaceres, @mounirlamouri)
w3c/web-share
-
4 issues opened.
-
Specification status report for TPAC 2019 w3c/web-share#121, by @LJWatson.
-
What should happen is if underlying page navigates? w3c/web-share#120, by @marcoscaceres.
-
Script abortable shares w3c/web-share#119, by @marcoscaceres.
-
canShare(data) without filepicker w3c/web-share#114, by @10eputzen.
-
-
3 issues closed.
-
What should happen is if underlying page navigates? w3c/web-share#120.
-
Script abortable shares w3c/web-share#119.
-
Intent to Migrate Web Share API w3c/web-share#99.
-
-
6 issues received 29 new comments.
-
What should happen is if underlying page navigates? w3c/web-share#120 (4 comments by @marcoscaceres, @mgiuca)
-
4 pull requests opened.
-
Do 'triggered by user activation' check earlier w3c/web-share#118, by @marcoscaceres.
-
Fix WebIDL validation error w3c/web-share#117, by @saschanaz.
-
chore: add validation via TravisCI w3c/web-share#116, by @marcoscaceres.
-
chore(index): Migration to W3C w3c/web-share#115, by @marcoscaceres.
-
-
3 pull requests merged.
-
Fix WebIDL validation error w3c/web-share#117.
-
chore: add validation via TravisCI w3c/web-share#116.
-
chore(index): Migration to W3C w3c/web-share#115.
-
-
3 pull requests received 13 new comments.
-
Introduce [[sharePromise]] internal slot w3c/web-share#113 (11 comments by @marcoscaceres, @mgiuca, @tobie)
-
w3c/gamepad
-
4 issues opened.
-
Update to constructor operations w3c/gamepad#102, by @Ms2ger.
-
Update spec to new IDL syntax for optional dictionaries w3c/gamepad#101, by @Ms2ger.
-
Specification status report for TPAC 2019 w3c/gamepad#99, by @LJWatson.
-
Move Brandon to "former editor"? w3c/gamepad#97, by @cwilso.
-
-
2 issues closed.
-
Move Brandon to "former editor"? w3c/gamepad#97.
-
Consider changing gamepad-mapping API to match SDL2's w3c/gamepad#24.
-
-
4 issues received 6 new comments.
-
w3c/gamepad#24 (1 comment by @sagoston)
-
3 pull requests opened.
-
Move Scott Graham to former editor w3c/gamepad#100, by @sgraham.
-
Move Brandon from editor to former editor. w3c/gamepad#98, by @cwilso.
-
Do not permit unique info in ID w3c/gamepad#96, by @sagoston.
-
-
2 pull requests merged.
-
Move Scott Graham to former editor w3c/gamepad#100.
-
Move Brandon from editor to former editor. w3c/gamepad#98.
-
-
2 pull requests received 7 new comments.
w3c/IndexedDB
-
4 issues opened.
-
Update to constructor operations w3c/IndexedDB#293, by @Ms2ger.
-
How a transaction is implemented as a queue hang w3c/IndexedDB#291, by @lzira.
-
Specification status report for TPAC 2019 w3c/IndexedDB#290, by @LJWatson.
-
[IndexedDB] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/IndexedDB#288, by @dmurph.
-
-
1 issue closed.
-
Update to Web IDL changes to optional dictionary defaulting w3c/IndexedDB#285.
-
-
5 issues received 5 new comments.
-
w3c/IndexedDB#50 (1 comment by @asutherland)
-
w3c/IndexedDB#35 (1 comment by @inexorabletash)
-
Update to Web IDL changes to optional dictionary defaulting w3c/IndexedDB#285 (1 comment by @inexorabletash)
-
[IndexedDB] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/IndexedDB#288 (1 comment by @dmurph)
-
-
3 pull requests opened.
-
Add dictionary default value w3c/IndexedDB#292, by @saschanaz.
-
Add dictionary default value w3c/IndexedDB#289, by @saschanaz.
-
Improve readability of 'key or key range' w3c/IndexedDB#287, by @sigiesec.
-
-
2 pull requests merged.
-
Add dictionary default value w3c/IndexedDB#292.
-
Improve readability of 'key or key range' w3c/IndexedDB#287.
-
-
1 pull request closed.
-
Add dictionary default value w3c/IndexedDB#289.
-
-
3 pull requests received 4 new comments.
w3c/uievents
-
2 issues opened.
-
Update to constructor operations w3c/uievents#243, by @Ms2ger.
-
Specification status report for TPAC 2019 w3c/uievents#242, by @LJWatson.
-
-
1 issue reopened.
w3c/manifest
-
6 issues opened.
-
Adaptive icons on Android 9 w3c/manifest#783, by @TorstenDittmann.
-
Specification status report for TPAC 2019 w3c/manifest#782, by @LJWatson.
-
beforeinstallprompt not fire with "prefer_related_applications": true w3c/manifest#780, by @outprogs.
-
Dynamic Theme Color w3c/manifest#779, by @MehrdadKhnzd.
-
Add link type "manifest" to HTML w3c/manifest#778, by @Malvoz.
-
When fetching manifest, credentials should be omitted w3c/manifest#776, by @marcoscaceres.
-
-
2 issues closed.
-
When fetching manifest, credentials should be omitted w3c/manifest#776.
-
purpose member type check missing w3c/manifest#771.
-
-
1 issue reopened.
-
manifest.webmanifest or manifest.json w3c/manifest#689, by @marcoscaceres.
-
-
7 issues received 22 new comments.
-
beforeinstallprompt not fire with "prefer_related_applications": true w3c/manifest#780 (3 comments by @alancutter, @outprogs)
-
When fetching manifest, credentials should be omitted w3c/manifest#776 (3 comments by @dominickng, @marcoscaceres)
-
3 pull requests opened.
-
Add dictionary default value w3c/manifest#781, by @saschanaz.
-
fix: omit credentials by default when obtaining w3c/manifest#777, by @marcoscaceres.
-
fix: purpose member type check + empty string handling w3c/manifest#775, by @marcoscaceres.
-
-
3 pull requests merged.
-
Add dictionary default value w3c/manifest#781.
-
fix: omit credentials by default when obtaining w3c/manifest#777.
-
fix: purpose member type check + empty string handling w3c/manifest#775.
-
-
1 pull request closed.
-
feat: Add splashscreens member + purpose (closes #510) w3c/manifest#530.
-
-
2 pull requests received 11 new comments.
-
fix: purpose member type check + empty string handling w3c/manifest#775 (6 comments by @dominickng, @marcoscaceres)
-
fix: omit credentials by default when obtaining w3c/manifest#777 (5 comments by @kenchris, @marcoscaceres)
-
w3c/webappswg
-
1 issue opened.
-
TPAC 2019: Specification status reports w3c/webappswg#19, by @LJWatson.
-
-
2 issues closed.
-
Pointerlock still failing to auto-publish w3c/webappswg#16.
-
Contact editors to prepare for TPAC w3c/webappswg#13.
-
-
3 issues received 14 new comments.
-
Pointerlock still failing to auto-publish w3c/webappswg#16 (5 comments by @deniak, @marcoscaceres, @siusin)
-
RFC: TPAC meeting structure w3c/webappswg#10 (5 comments by @anssiko, @LJWatson, @marcoscaceres, @szager-chromium)
-
Contact editors to prepare for TPAC w3c/webappswg#13 (4 comments by @LJWatson, @marcoscaceres, @szager-chromium)
-
w3c/web-locks
-
2 issues received 4 new comments.
w3c/contact-picker
-
2 issues opened.
-
Closer HTML alignment w3c/contact-picker#21, by @marcoscaceres.
-
We REALLY need this! w3c/contact-picker#20, by @marcoscaceres.
-
-
4 issues received 36 new comments.
-
Closer HTML alignment w3c/contact-picker#21 (16 comments by @aarongustafson, @beverloo, @marcoscaceres, @markcellus, @rayankans, @tomayac)
-
Consider contact API that does not reveal contact info to the website w3c/contact-picker#7 (7 comments by @dtruffaut, @Gozala, @rayankans, @tomayac)
-
We REALLY need this! w3c/contact-picker#20 (7 comments by @aarongustafson, @beverloo, @marcoscaceres, @rayankans)
-
Detect which contact properties are supported by the browser w3c/contact-picker#19 (6 comments by @domenic, @rayankans)
-
-
2 pull requests opened.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#23, by @rayankans.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#22, by @rayankans.
-
-
1 pull request merged.
-
Copy edit the README. w3c/contact-picker#18.
-
-
2 pull requests closed.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#23.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#22.
-
-
2 pull requests received 5 new comments.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#23 (4 comments by @beverloo, @domenic, @rayankans, @yoavweiss)
-
TR publications
-
15 documents published.
-
Web App Manifest published twice as a Working Draft. History of Web App Manifest
-
Push API published 6 times as a Working Draft. History of Push API
-
The Screen Orientation API published twice as a Working Draft. History of The Screen Orientation API
-
HTML Accessibility API Mappings 1.0 published 3 times as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
ARIA in HTML published twice as a Working Draft. History of ARIA in HTML
-
Participants
-
1 participant joined.
-
Michael[tm] Smith (sideshowbarker) (W3C) joined.
-
-
4 organizations joined.
-
Apple Inc. joined.
-
BBVA joined.
-
Igalia joined.
-
Microsoft Corporation joined.
-
GitHub
w3c/ServiceWorker
-
5 issues opened.
-
A way to specify a pattern of destination URLs to hit/skip SW w3c/ServiceWorker#1454, by @kinu.
-
Service worker cache localisation w3c/ServiceWorker#1453, by @robinglen.
-
content-type in csp report on fetch is missed w3c/ServiceWorker#1449, by @maxkuzmin.
-
Request's origin needs to be set for [[Update]] algorithm w3c/ServiceWorker#1447, by @makotoshimazu.
-
"Not Ready For Implementation" w3c/ServiceWorker#1446, by @mfalken.
-
-
2 issues closed.
-
Service worker cache localisation w3c/ServiceWorker#1453.
-
"Not Ready For Implementation" w3c/ServiceWorker#1446.
-
-
10 issues received 27 new comments.
-
A way to specify a pattern of destination URLs to hit/skip SW w3c/ServiceWorker#1454 (9 comments by @asakusuma, @asutherland, @kinu, @mkruisselbrink, @n8schloss)
-
Service worker cache localisation w3c/ServiceWorker#1453 (3 comments by @jeffposnick, @robinglen, @tomayac)
-
w3c/ServiceWorker#719 (2 comments by @mfalken)
-
w3c/ServiceWorker#1372 (1 comment by @josephliccini)
-
w3c/ServiceWorker#1013 (1 comment by @jungkees)
-
w3c/ServiceWorker#1375 (1 comment by @Malvoz)
-
w3c/ServiceWorker#658 (1 comment by @shmdhussain)
-
-
4 pull requests opened.
-
Define service worker events w3c/ServiceWorker#1452, by @jungkees.
-
Add a note about termination during activation. w3c/ServiceWorker#1451, by @josephliccini.
-
Leave notes on service worker script fetching for V1 w3c/ServiceWorker#1450, by @jungkees.
-
Set default value of optional dictionary to {} w3c/ServiceWorker#1448, by @CYBAI.
-
-
2 pull requests merged.
-
Leave notes on service worker script fetching for V1 w3c/ServiceWorker#1450.
-
How to create registration objects w3c/ServiceWorker#1445.
-
-
1 pull request reopened.
-
Set default value of optional dictionary to {} w3c/ServiceWorker#1448, by @CYBAI.
-
-
6 pull requests received 28 new comments.
-
Add an option to include frozen documents. w3c/ServiceWorker#1442 (15 comments by @asutherland, @dtapuska, @jakearchibald, @youennf)
-
Set default value of optional dictionary to {} w3c/ServiceWorker#1448 (3 comments by @CYBAI, @jakearchibald)
-
Add a note about termination during activation. w3c/ServiceWorker#1451 (1 comment by @josephliccini)
-
w3c/contact-picker
-
1 issue opened.
-
Detect which contact properties are supported by the browser w3c/contact-picker#19, by @rayankans.
-
-
2 issues received 3 new comments.
-
Contacts Picker UI should have a "Select All" option w3c/contact-picker#15 (2 comments by @comp615, @rayankans)
-
-
1 pull request opened.
-
Copy edit the README. w3c/contact-picker#18, by @jpmedley.
-
-
1 pull request received 3 new comments.
w3c/FileAPI
-
2 issues opened.
-
add dataURL method w3c/FileAPI#136, by @petele.
-
Sort out when blob: URLs can be fetched / navigated w3c/FileAPI#135, by @annevk.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update to Web IDL changes to optional dictionary defaulting w3c/FileAPI#134, by @marcoscaceres.
-
-
1 pull request merged.
-
Update to Web IDL changes to optional dictionary defaulting w3c/FileAPI#134.
-
w3c/badging
-
6 issues opened.
-
Update Spec to Match Explainer w3c/badging#45, by @fallaciousreasoning.
-
Badge permission... w3c/badging#44, by @marcoscaceres.
-
Scoping Badges is Complicated w3c/badging#43, by @fallaciousreasoning.
-
Consider separate 'Cleared' and 'Unset' values for badges. w3c/badging#42, by @fallaciousreasoning.
-
Resetting Badges w3c/badging#41, by @fallaciousreasoning.
-
Badging Bookmark Icons w3c/badging#40, by @fallaciousreasoning.
-
-
7 issues closed.
-
Badging Bookmark Icons w3c/badging#40.
-
API surface: namespace vs. class with static methods w3c/badging#9.
-
Attach to navigator instead? w3c/badging#14.
-
Consider adding a getter w3c/badging#18.
-
Editorial: cross-link to special values w3c/badging#10.
-
Desktop App Badge w3c/badging#27.
-
dealing with lifetime w3c/badging#3.
-
-
2 issues reopened.
-
IPC calls for promise w3c/badging#35, by @raymeskhoury.
-
Attach to navigator instead? w3c/badging#14, by @fallaciousreasoning.
-
-
11 issues received 50 new comments.
-
Scoping Badges is Complicated w3c/badging#43 (15 comments by @fallaciousreasoning, @marcoscaceres, @mgiuca)
-
Update Spec to Match Explainer w3c/badging#45 (4 comments by @fallaciousreasoning, @marcoscaceres, @mgiuca)
-
IPC calls for promise w3c/badging#35 (3 comments by @fallaciousreasoning, @marcoscaceres, @raymeskhoury)
-
w3c/badging#5 (1 comment by @fallaciousreasoning)
-
Consider separate 'Cleared' and 'Unset' values for badges. w3c/badging#42 (1 comment by @fallaciousreasoning)
-
-
4 pull requests opened.
-
Adds Overview of Badgable Concepts w3c/badging#46, by @fallaciousreasoning.
-
Address TAG review feedback w3c/badging#39, by @fallaciousreasoning.
-
Change Badge from interface to namespace w3c/badging#38, by @marcoscaceres.
-
Adds cross links for special values w3c/badging#37, by @fallaciousreasoning.
-
-
5 pull requests merged.
-
Adds Overview of Badgable Concepts w3c/badging#46.
-
Address TAG review feedback w3c/badging#39.
-
Change Badge from interface to namespace w3c/badging#38.
-
Adds cross links for special values w3c/badging#37.
-
-
5 pull requests received 100 new comments.
-
Address TAG review feedback w3c/badging#39 (86 comments by @fallaciousreasoning, @marcoscaceres, @mgiuca)
-
Change Badge from interface to namespace w3c/badging#38 (7 comments by @domenic, @fallaciousreasoning, @marcoscaceres)
-
Adds Overview of Badgable Concepts w3c/badging#46 (5 comments by @fallaciousreasoning, @raymeskhoury)
-
Makes a note that user agents can clear the badge at any time in the spec. w3c/badging#36 (1 comment by @marcoscaceres)
-
w3c/manifest
-
3 issues opened.
-
Add offline_url option w3c/manifest#774, by @Snugug.
-
Please add caption property to screenshots w3c/manifest#773, by @SpeednetGroup.
-
purpose member type check missing w3c/manifest#771, by @marcoscaceres.
-
-
1 issue closed.
-
Add offline_url option w3c/manifest#774.
-
-
10 issues received 57 new comments.
-
Add offline_url option w3c/manifest#774 (15 comments by @b1tr0t, @glennhartmann, @jakearchibald, @kenchris, @marcoscaceres, @mgiuca, @reillyeon, @Snugug)
-
Introduce window.Application global object aside manifest.webmanifest w3c/manifest#769 (10 comments by @marcoscaceres, @OmidHekayati, @samad-aghaei)
-
Please add caption property to screenshots w3c/manifest#773 (9 comments by @aarongustafson, @dominickng, @jgw96, @marcoscaceres, @SpeednetGroup)
-
More restrictive standalone mode w3c/manifest#770 (5 comments by @aarongustafson, @madmoizo, @marcoscaceres)
-
w3c/manifest#421 (1 comment by @marcoscaceres)
-
w3c/manifest#449 (1 comment by @RichardNeill)
-
-
1 pull request opened.
-
editorial: enable MDN annotations w3c/manifest#772, by @marcoscaceres.
-
-
1 pull request merged.
-
editorial: enable MDN annotations w3c/manifest#772.
-
-
1 pull request closed.
-
Export WebAppManifest dfn as a dictionary w3c/manifest#767.
-
-
3 pull requests received 17 new comments.
-
Export WebAppManifest dfn as a dictionary w3c/manifest#767 (8 comments by @aarongustafson, @jyasskin, @marcoscaceres)
-
editorial: enable MDN annotations w3c/manifest#772 (6 comments by @kenchris, @marcoscaceres, @torgo)
-
w3c/IndexedDB
-
1 issue opened.
-
Update to Web IDL changes to optional dictionary defaulting w3c/IndexedDB#285, by @inexorabletash.
-
-
4 issues received 10 new comments.
-
Update to Web IDL changes to optional dictionary defaulting w3c/IndexedDB#285 (3 comments by @inexorabletash, @marcoscaceres)
-
w3c/IndexedDB#36 (1 comment by @inexorabletash)
-
2 pull requests opened.
-
Editorial: Use better markdown for domintro sections w3c/IndexedDB#286, by @inexorabletash.
-
Some editorial fixes w3c/IndexedDB#284, by @sigiesec.
-
-
2 pull requests merged.
-
Editorial: Use better markdown for domintro sections w3c/IndexedDB#286.
-
Some editorial fixes w3c/IndexedDB#284.
-
-
2 pull requests received 5 new comments.
-
Editorial: Use better markdown for domintro sections w3c/IndexedDB#286 (1 comment by @inexorabletash)
w3c/screen-orientation
-
1 issue opened.
-
Privacy notes are overly dismissive w3c/screen-orientation#181, by @marcoscaceres.
-
-
1 issue received 3 new comments.
-
2 pull requests opened.
-
BREAKING CHANGE: unlock() returns a pormise w3c/screen-orientation#183, by @marcoscaceres.
-
Editorial: simplify initialization of type+angle w3c/screen-orientation#182, by @marcoscaceres.
-
-
1 pull request received 5 new comments.
-
BREAKING CHANGE: unlock() returns a pormise w3c/screen-orientation#183 (5 comments by @marcoscaceres, @mounirlamouri)
-
w3c/uievents
-
3 issues opened.
-
Pen pendockchange event w3c/uievents#240, by @gked.
-
Pen Button Events w3c/uievents#237, by @gked.
-
-
1 issue closed.
-
Identify which of multiple keyboards an event came from w3c/uievents#226.
-
-
3 issues received 12 new comments.
-
Should require Input event to be fired within same event loop as keydown? keypress? neither? w3c/uievents#238 (4 comments by @annevk, @dbates-wk)
-
Should an element remain focused and receive key events if it's display:none-ed? w3c/uievents#236 (3 comments by @rniwa, @tkent-google)
-
1 pull request opened.
-
set default for optional dictionary w3c/uievents#239, by @marcoscaceres.
-
w3c/web-share
-
6 issues opened.
-
Distinguishing between data errors and user abort w3c/web-share#112, by @marcoscaceres.
-
Clarifying behavior of multiple simultaneous shares w3c/web-share#110, by @marcoscaceres.
-
why "optional" in share(optional ShareData data)? w3c/web-share#109, by @marcoscaceres.
-
canShare() is not future compatible w3c/web-share#108, by @marcoscaceres.
-
Drop the levels/versioning w3c/web-share#107, by @marcoscaceres.
-
Document no longer fully active while showing share w3c/web-share#106, by @marcoscaceres.
-
-
3 issues closed.
-
Document no longer fully active while showing share w3c/web-share#106.
-
why "optional" in share(optional ShareData data)? w3c/web-share#109.
-
How can we share an Image/Video from URL directly w3c/web-share#104.
-
-
7 issues received 25 new comments.
-
Intent to Migrate Web Share API w3c/web-share#99 (11 comments by @edent, @ewilligers, @GirlyGeekdom, @grorg, @marcoscaceres, @philnash, @raymeskhoury)
-
canShare() is not future compatible w3c/web-share#108 (5 comments by @ewilligers, @marcoscaceres, @raymeskhoury)
-
Document no longer fully active while showing share w3c/web-share#106 (3 comments by @marcoscaceres)
-
Distinguishing between data errors and user abort w3c/web-share#112 (3 comments by @ewilligers, @marcoscaceres)
-
w3c/web-share#12 (1 comment by @anik587)
-
-
2 pull requests opened.
-
Introduce [[sharePromise]] internal slot w3c/web-share#113, by @marcoscaceres.
-
fix: default share(data) to empty dictionary w3c/web-share#111, by @marcoscaceres.
-
-
1 pull request merged.
-
fix: default share(data) to empty dictionary w3c/web-share#111.
-
-
1 pull request received 5 new comments.
-
fix: default share(data) to empty dictionary w3c/web-share#111 (5 comments by @ewilligers, @marcoscaceres)
-
w3c/webappswg
-
4 issues opened.
-
Pointerlock still failing to auto-publish w3c/webappswg#16, by @marcoscaceres.
-
Check specs have an accessibility section w3c/webappswg#15, by @marcoscaceres.
-
Make sure editors are WG members w3c/webappswg#14, by @LJWatson.
-
Contact editors to prepare for TPAC w3c/webappswg#13, by @marcoscaceres.
-
-
2 issues closed.
-
Make sure editors are WG members w3c/webappswg#14.
-
Need Echidna publication token for pointerlock w3c/webappswg#9.
-
-
3 issues received 4 new comments.
-
2 pull requests opened.
-
editing => text editing w3c/webappswg#18, by @johanneswilm.
-
Adds info for Editing TF w3c/webappswg#17, by @LJWatson.
-
-
2 pull requests merged.
-
editing => text editing w3c/webappswg#18.
-
Adds info for Editing TF w3c/webappswg#17.
-
w3c/push-api
-
1 issue opened.
-
userVisibleOnly should be standardized to match browser behaviour w3c/push-api#313, by @mgiuca.
-
-
3 issues closed.
-
The term webapp seems odd w3c/push-api#77.
-
"set its value to a BufferSource" w3c/push-api#290.
-
Need to define where the EventHandler type comes from w3c/push-api#233.
-
-
1 issue received 1 new comment.
-
w3c/push-api#233 (1 comment by @marcoscaceres)
-
-
5 pull requests opened.
-
Change PushSubscriptionChangeInit to PushSubscriptionChangeEventInit. w3c/push-api#312, by @rayankans.
-
Editorial: drop 'webapp' formal definition w3c/push-api#311, by @marcoscaceres.
-
fix: set to ArrayBuffer instead of BufferSource w3c/push-api#310, by @marcoscaceres.
-
Editorial: use promises-guide for promises w3c/push-api#309, by @marcoscaceres.
-
Update to Web IDL changes to optional dictionary defaulting w3c/push-api#308, by @marcoscaceres.
-
-
5 pull requests merged.
-
Editorial: drop 'webapp' formal definition w3c/push-api#311.
-
Change PushSubscriptionChangeInit to PushSubscriptionChangeEventInit. w3c/push-api#312.
-
Editorial: use promises-guide for promises w3c/push-api#309.
-
fix: set to ArrayBuffer instead of BufferSource w3c/push-api#310.
-
Update to Web IDL changes to optional dictionary defaulting w3c/push-api#308.
-
-
2 pull requests received 3 new comments.
-
Editorial: drop 'webapp' formal definition w3c/push-api#311 (2 comments by @marcoscaceres, @martinthomson)
-
Change PushSubscriptionChangeInit to PushSubscriptionChangeEventInit. w3c/push-api#312 (1 comment by @marcoscaceres)
-
w3c/gamepad
-
1 issue received 1 new comment.
-
w3c/gamepad#46 (1 comment by @sagoston)
-
w3c/pointerlock
-
1 issue received 1 new comment.
-
w3c/pointerlock#36 (1 comment by @eliwald)
-
-
3 pull requests opened.
-
Add lock options to requestPointerLock w3c/pointerlock#49, by @NavidZ.
-
Editorial: Add a missing ref-name for requestPointerLock method w3c/pointerlock#48, by @NavidZ.
-
Add caniuse link w3c/pointerlock#47, by @NavidZ.
-
-
2 pull requests merged.
-
Editorial: Add a missing ref-name for requestPointerLock method w3c/pointerlock#48.
-
Add caniuse link w3c/pointerlock#47.
-
-
2 pull requests received 28 new comments.
-
Editorial: Add a missing ref-name for requestPointerLock method w3c/pointerlock#48 (7 comments by @marcoscaceres, @NavidZ)
w3c/using-aria
-
3 issues opened.
-
Should we re-publish this? w3c/using-aria#49, by @marcoscaceres.
-
Outdated links w3c/using-aria#48, by @marcoscaceres.
-
Change the headings for rules w3c/using-aria#47, by @marcoscaceres.
-
-
2 issues closed.
-
Link to ARIA-APG is broken. w3c/using-aria#43.
-
Move to WebApps WG w3c/using-aria#44.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Chore: set up link/respec validation w3c/using-aria#46, by @marcoscaceres.
-
-
3 pull requests merged.
-
Chore: set up link/respec validation w3c/using-aria#46.
-
Update link to 'Just use a (native) HTML button' w3c/using-aria#41.
-
Changed ARIA 1.1 links to 1.2 and HTTPS w3c/using-aria#45.
-
TR publications
-
13 documents published.
-
HTML Accessibility API Mappings 1.0 published 4 times as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
The Screen Orientation API published twice as a Working Draft. History of The Screen Orientation API
-
Selection API published 4 times as a Working Draft. History of Selection API
-
Pointer Lock 2.0 published as a Working Draft. History of Pointer Lock 2.0
-
Clipboard API and events published as a Working Draft. History of Clipboard API and events
-
Push API published as a Working Draft. History of Push API
-
Participants
-
2 participants joined.
-
Johannes Wilm (W3C Invited Experts) joined.
-
Kagami Rosylight (Mozilla Foundation) joined.
-
-
1 organization joined.
-
eyeo GmbH joined.
-
GitHub
w3c/manifest
-
2 issues opened.
-
More restrictive standalone mode w3c/manifest#770, by @madmoizo.
-
Introduce window.Application global object aside manifest.webmanifest w3c/manifest#769, by @OmidHekayati.
-
-
8 issues received 16 new comments.
-
w3c/manifest#582 (2 comments by @aarongustafson)
-
w3c/manifest#421 (1 comment by @Malvoz)
-
w3c/manifest#97 (1 comment by @OmidHekayati)
-
w3c/manifest#764 (1 comment by @aarongustafson)
-
1 pull request opened.
-
Add shortcuts feature to the explainer and spec w3c/manifest#768, by @aarongustafson.
-
-
1 pull request received 16 new comments.
-
Add shortcuts feature to the explainer and spec w3c/manifest#768 (16 comments by @aarongustafson, @kenchris, @siusin)
-
w3c/uievents
-
2 issues opened.
-
Should an element remain focused and receive key events if it's display:none-ed? w3c/uievents#236, by @dbates-wk.
-
Change click/auxclick/contextment/dblclick event types to PointerEvent? w3c/uievents#235, by @NavidZ.
-
-
1 issue closed.
-
Broken links to Web IDL spec w3c/uievents#172.
-
-
2 issues received 9 new comments.
-
Should an element remain focused and receive key events if it's display:none-ed? w3c/uievents#236 (8 comments by @annevk, @dbates-wk, @othermaciej, @rniwa)
-
Change click/auxclick/contextment/dblclick event types to PointerEvent? w3c/uievents#235 (1 comment by @patrickhlauke)
-
-
1 pull request merged.
-
Fix references to Web IDL w3c/uievents#176.
-
-
1 pull request reopened.
-
Fix references to Web IDL w3c/uievents#176, by @marcoscaceres.
-
w3c/web-share
-
3 issues opened.
-
Document Web Share vs. native share destination capabilities more clearly w3c/web-share#105, by @repentsinner.
-
How can we share an Image/Video from URL directly w3c/web-share#104, by @lakshaylbb.
-
Demos don't check for https to make error messaging less obtuse w3c/web-share#100, by @repentsinner.
-
-
2 issues closed.
-
Document Web Share vs. native share destination capabilities more clearly w3c/web-share#105.
-
Demos don't check for https to make error messaging less obtuse w3c/web-share#100.
-
-
3 issues received 4 new comments.
-
Document Web Share vs. native share destination capabilities more clearly w3c/web-share#105 (2 comments by @ewilligers, @repentsinner)
-
-
3 pull requests opened.
-
fix: algorithm aborts before promise is returned w3c/web-share#103, by @marcoscaceres.
-
Editorial: ReSpec fixes w3c/web-share#102, by @marcoscaceres.
-
Demo now checks for https w3c/web-share#101, by @ewilligers.
-
-
3 pull requests merged.
-
fix: algorithm aborts before promise is returned w3c/web-share#103.
-
Editorial: ReSpec fixes w3c/web-share#102.
-
Demo now checks for https w3c/web-share#101.
-
-
3 pull requests received 4 new comments.
w3c/ServiceWorker
-
12 issues opened.
-
How can I pass or post params to sevirce worker on register or install? w3c/ServiceWorker#1441, by @mkkeck.
-
@alimsaeed2020 w3c/ServiceWorker#1439, by @alimsaeed10.
-
Registering service workers for unique origins? w3c/ServiceWorker#1437, by @mjbvz.
-
Add a WPT test for credentialed requests in register()/update w3c/ServiceWorker#1435, by @mfalken.
-
Should we restore the registration record removing step in Clear Registration? w3c/ServiceWorker#1433, by @jungkees.
-
Broken links to v1 w3c/ServiceWorker#1431, by @mfalken.
-
Should update() always reject if there is an installing worker? w3c/ServiceWorker#1429, by @Yannic.
-
ServiceWorker, ServiceWorkerRegistration should be moved out of "Client Context" section w3c/ServiceWorker#1427, by @mfalken.
-
maxScopeString definition is missing the trailing '/' w3c/ServiceWorker#1423, by @mfalken.
-
oncurrentchange in test w3c/ServiceWorker#1421, by @jakearchibald.
-
Object equality of service worker registrations w3c/ServiceWorker#1420, by @jakearchibald.
-
Should register() trigger an update if only updateViaCache changes? w3c/ServiceWorker#1414, by @mfalken.
-
-
18 issues closed.
-
How can I pass or post params to sevirce worker on register or install? w3c/ServiceWorker#1441.
-
Find a way for service workers to get their current state w3c/ServiceWorker#1077.
-
@alimsaeed2020 w3c/ServiceWorker#1439.
-
Use ASCII serialization for origins w3c/ServiceWorker#1142.
-
Broken links to v1 w3c/ServiceWorker#1431.
-
Should update() called on an installing worker reject (as currently does?) w3c/ServiceWorker#1155.
-
Missing task queuing w3c/ServiceWorker#1403.
-
"Unregister" operation may be interrupted by `ServiceWorker#postMessage` w3c/ServiceWorker#1146.
-
ServiceWorker, ServiceWorkerRegistration should be moved out of "Client Context" section w3c/ServiceWorker#1427.
-
oncurrentchange in test w3c/ServiceWorker#1421.
-
maxScopeString definition is missing the trailing '/' w3c/ServiceWorker#1423.
-
Object equality of service worker registrations w3c/ServiceWorker#1420.
-
resurrected service workers don't fire an activate event which may break expectations w3c/ServiceWorker#1204.
-
Should a SW client.id persists across Discards/Reloads of the same page? w3c/ServiceWorker#1263.
-
Should add “script type” and “update via cache” when check two jobs are equivalent. w3c/ServiceWorker#1358.
-
Should add a “script type” check in the register algorithm. w3c/ServiceWorker#1359.
-
Should register() trigger byte-for-byte checking when WorkerType is updated? w3c/ServiceWorker#1408.
-
Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? w3c/ServiceWorker#1189.
-
-
1 issue reopened.
-
Should update() always reject if there is an installing worker? w3c/ServiceWorker#1429, by @mfalken.
-
-
26 issues received 78 new comments.
-
Top-level await integration for ServiceWorkers running modules w3c/ServiceWorker#1407 (13 comments by @annevk, @domenic, @jakearchibald, @Jamesernator, @littledan, @wanderview)
-
Should update() always reject if there is an installing worker? w3c/ServiceWorker#1429 (5 comments by @jakearchibald, @mfalken, @Yannic)
-
How can I pass or post params to sevirce worker on register or install? w3c/ServiceWorker#1441 (3 comments by @jakearchibald, @mkkeck)
-
Registering service workers for unique origins? w3c/ServiceWorker#1437 (2 comments by @asutherland, @wanderview)
-
w3c/ServiceWorker#1273 (2 comments by @jakearchibald)
-
Object equality of service worker registrations w3c/ServiceWorker#1420 (2 comments by @jakearchibald, @wanderview)
-
Should we restore the registration record removing step in Clear Registration? w3c/ServiceWorker#1433 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#1155 (1 comment by @mfalken)
-
w3c/ServiceWorker#1403 (1 comment by @mfalken)
-
ServiceWorker, ServiceWorkerRegistration should be moved out of "Client Context" section w3c/ServiceWorker#1427 (1 comment by @mfalken)
-
maxScopeString definition is missing the trailing '/' w3c/ServiceWorker#1423 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#1200 (1 comment by @mfalken)
-
w3c/ServiceWorker#1263 (1 comment by @jakearchibald)
-
Should register() trigger an update if only updateViaCache changes? w3c/ServiceWorker#1414 (1 comment by @wanderview)
-
w3c/ServiceWorker#1204 (1 comment by @jakearchibald)
-
w3c/ServiceWorker#1358 (1 comment by @mfalken)
-
w3c/ServiceWorker#1359 (1 comment by @mfalken)
-
Should register() trigger byte-for-byte checking when WorkerType is updated? w3c/ServiceWorker#1408 (1 comment by @mfalken)
-
w3c/ServiceWorker#1189 (1 comment by @mfalken)
-
23 pull requests opened.
-
How to create registration objects w3c/ServiceWorker#1445, by @jakearchibald.
-
Handle asynchronous modules (top-level await). w3c/ServiceWorker#1444, by @Ms2ger.
-
Experimenting with abortable algorithms w3c/ServiceWorker#1443, by @jakearchibald.
-
Add an option to include frozen documents. w3c/ServiceWorker#1442, by @dtapuska.
-
Create a Kill Service Workers algorithm w3c/ServiceWorker#1440, by @asakusuma.
-
Export the Clear Registration Algorithm w3c/ServiceWorker#1438, by @asakusuma.
-
Update order w3c/ServiceWorker#1436, by @jakearchibald.
-
Removing failed registrations w3c/ServiceWorker#1434, by @jakearchibald.
-
Improving service worker state w3c/ServiceWorker#1432, by @jakearchibald.
-
Bikeshed improvements to *force bypass cache for import scripts flag* w3c/ServiceWorker#1430, by @mfalken.
-
One ServiceWorker object per service worker per realm w3c/ServiceWorker#1428, by @jakearchibald.
-
Adding self.serviceWorker to service workers. w3c/ServiceWorker#1426, by @jakearchibald.
-
Fixing a couple of bikeshed errors w3c/ServiceWorker#1425, by @jakearchibald.
-
Fixing max scope to include trailing slash. w3c/ServiceWorker#1424, by @jakearchibald.
-
Add trailing '/' to example of max scope w3c/ServiceWorker#1422, by @jeffposnick.
-
Check for Run Service Worker failure and disallow starting redundant workers. w3c/ServiceWorker#1419, by @mfalken.
-
Fix early return value from Handle Fetch. w3c/ServiceWorker#1418, by @mfalken.
-
Unify the event skipping algorithm when there is no event handler. w3c/ServiceWorker#1417, by @mfalken.
-
Central algorithm for updating service worker state and registrations w3c/ServiceWorker#1416, by @jakearchibald.
-
Kill resurrection w3c/ServiceWorker#1415, by @jakearchibald.
-
Fixing link to "scope" and copying changes to v1. w3c/ServiceWorker#1413, by @jakearchibald.
-
Fixing deploy w3c/ServiceWorker#1412, by @jakearchibald.
-
Improve "update via cache" and "worker type" in register algorithms. w3c/ServiceWorker#1411, by @mfalken.
-
-
16 pull requests merged.
-
Adding self.serviceWorker to service workers. w3c/ServiceWorker#1426.
-
Use ASCII serialization for origins w3c/ServiceWorker#1151.
-
Removing failed registrations w3c/ServiceWorker#1434.
-
Improving service worker state w3c/ServiceWorker#1432.
-
Bikeshed improvements to *force bypass cache for import scripts flag* w3c/ServiceWorker#1430.
-
Check for Run Service Worker failure and disallow starting redundant workers. w3c/ServiceWorker#1419.
-
One ServiceWorker object per service worker per realm w3c/ServiceWorker#1428.
-
Fixing a couple of bikeshed errors w3c/ServiceWorker#1425.
-
Fixing max scope to include trailing slash. w3c/ServiceWorker#1424.
-
Add trailing '/' to example of max scope w3c/ServiceWorker#1422.
-
Fix early return value from Handle Fetch. w3c/ServiceWorker#1418.
-
Kill resurrection w3c/ServiceWorker#1415.
-
Unify the event skipping algorithm when there is no event handler. w3c/ServiceWorker#1417.
-
Improve "update via cache" and "worker type" in register algorithms. w3c/ServiceWorker#1411.
-
Fixing link to "scope" and copying changes to v1. w3c/ServiceWorker#1413.
-
Fixing deploy w3c/ServiceWorker#1412.
-
-
1 pull request closed.
-
Export the Clear Registration Algorithm w3c/ServiceWorker#1438.
-
-
18 pull requests received 165 new comments.
-
Central algorithm for updating service worker state and registrations w3c/ServiceWorker#1416 (28 comments by @jakearchibald, @mfalken, @wanderview)
-
Add an option to include frozen documents. w3c/ServiceWorker#1442 (22 comments by @annevk, @dtapuska, @jakearchibald, @tabatkins, @wanderview)
-
Check for Run Service Worker failure and disallow starting redundant workers. w3c/ServiceWorker#1419 (21 comments by @jakearchibald, @mfalken)
-
Handle asynchronous modules (top-level await). w3c/ServiceWorker#1444 (13 comments by @annevk, @jakearchibald, @littledan, @Ms2ger)
-
Adding self.serviceWorker to service workers. w3c/ServiceWorker#1426 (11 comments by @jakearchibald, @mfalken, @wanderview)
-
Experimenting with abortable algorithms w3c/ServiceWorker#1443 (9 comments by @asakusuma, @jakearchibald, @mfalken, @wanderview)
-
Improve "update via cache" and "worker type" in register algorithms. w3c/ServiceWorker#1411 (7 comments by @jakearchibald, @mfalken)
-
Export the Clear Registration Algorithm w3c/ServiceWorker#1438 (5 comments by @asakusuma, @jakearchibald)
-
Create a Kill Service Workers algorithm w3c/ServiceWorker#1440 (4 comments by @asakusuma, @jakearchibald)
-
Bikeshed improvements to *force bypass cache for import scripts flag* w3c/ServiceWorker#1430 (4 comments by @jakearchibald, @mfalken)
-
Fixing max scope to include trailing slash. w3c/ServiceWorker#1424 (4 comments by @jakearchibald, @mfalken)
-
Add trailing '/' to example of max scope w3c/ServiceWorker#1422 (3 comments by @jakearchibald, @mfalken)
-
Unify the event skipping algorithm when there is no event handler. w3c/ServiceWorker#1417 (3 comments by @jakearchibald, @mfalken)
-
w3c/ServiceWorker#1151 (1 comment by @jungkees)
-
w3c/badging
-
2 issues opened.
-
IPC calls for promise w3c/badging#35, by @marcoscaceres.
-
-
4 issues closed.
-
Add security/privacy section w3c/badging#25.
-
Add internationalization section w3c/badging#23.
-
Explore removing clear() and possibly change set method? w3c/badging#19.
-
1 issue reopened.
-
Disassociate from install w3c/badging#12, by @raymeskhoury.
-
-
6 issues received 15 new comments.
-
Top most wanted feature from our feedback in PWA and some behavioral questions w3c/badging#30 (4 comments by @fallaciousreasoning, @g-ortuno, @Malvoz)
-
IPC calls for promise w3c/badging#35 (4 comments by @fallaciousreasoning, @marcoscaceres, @raymeskhoury)
-
w3c/badging#12 (1 comment by @raymeskhoury)
-
-
6 pull requests opened.
-
Spec cleanup w3c/badging#34, by @fallaciousreasoning.
-
Adds an internationalization section w3c/badging#33, by @fallaciousreasoning.
-
Update privacy security section w3c/badging#32, by @fallaciousreasoning.
-
Adds a origin trial feedback. w3c/badging#31, by @fallaciousreasoning.
-
Adds a privacy and security review for TAG w3c/badging#29, by @fallaciousreasoning.
-
5 pull requests merged.
-
Update privacy security section w3c/badging#32.
-
Spec cleanup w3c/badging#34.
-
Adds an internationalization section w3c/badging#33.
-
Adds a origin trial feedback. w3c/badging#31.
-
Adds a privacy and security review for TAG w3c/badging#29.
-
-
5 pull requests received 28 new comments.
-
Makes a note that user agents can clear the badge at any time in the spec. w3c/badging#36 (11 comments by @fallaciousreasoning, @Malvoz, @marcoscaceres, @raymeskhoury)
-
Adds an internationalization section w3c/badging#33 (3 comments by @fallaciousreasoning, @raymeskhoury)
-
w3c/screen-orientation
-
1 issue opened.
-
Page visibility transition can fire when false/true/false happens within a frame w3c/screen-orientation#179, by @toddreifsteck.
-
-
1 issue received 3 new comments.
-
Page visibility transition can fire when false/true/false happens within a frame w3c/screen-orientation#179 (3 comments by @marcoscaceres, @toddreifsteck)
-
-
1 pull request opened.
-
fix(.travis.yml): use https for URL w3c/screen-orientation#180, by @marcoscaceres.
-
-
1 pull request merged.
-
fix(.travis.yml): use https for URL w3c/screen-orientation#180.
-
w3c/webappswg
-
4 issues opened.
-
uievents missing .travis file w3c/webappswg#12, by @marcoscaceres.
-
"not authorized" to publish pointer lock w3c/webappswg#11, by @marcoscaceres.
-
RFC: TPAC meeting structure w3c/webappswg#10, by @LJWatson.
-
Need Echidna publication token for pointerlock w3c/webappswg#9, by @marcoscaceres.
-
-
2 issues closed.
-
"not authorized" to publish pointer lock w3c/webappswg#11.
-
Send out meeting proposal once everyone rejoins w3c/webappswg#3.
-
-
5 issues received 9 new comments.
-
w3c/webappswg#3 (1 comment by @LJWatson)
w3c/IndexedDB
-
6 issues opened.
-
Specify keyPath sequence caching behavior on IDBObjectStore w3c/IndexedDB#283, by @saschanaz.
-
Backward-compatible schema changes are very hard w3c/IndexedDB#282, by @sicking.
-
getAll() will crash sometimes in Electron w3c/IndexedDB#276, by @kasnihuang.
-
Crash for getAll() api in Electron w3c/IndexedDB#274, by @kasnihuang.
-
Definitions for IDBKeyRange lowerBound and upperBound aren't linked correctly. w3c/IndexedDB#271, by @mkruisselbrink.
-
IDBKeyRange.includes or IDBKeyRange._includes? w3c/IndexedDB#270, by @mkruisselbrink.
-
-
11 issues closed.
-
Specify keyPath sequence caching behavior on IDBObjectStore w3c/IndexedDB#283.
-
Should it be clarified that `IDBDatabase.close()` is idempotent? w3c/IndexedDB#222.
-
Async LocalStorage (transactionless key-value API over IDB) w3c/IndexedDB#91.
-
Security and Web Worker access for IndexedDB w3c/IndexedDB#141.
-
Durable database writes w3c/IndexedDB#99.
-
Transaction storm in idb-transaction-commit explainer sample w3c/IndexedDB#245.
-
getAll() will crash sometimes in Electron w3c/IndexedDB#276.
-
Crash for getAll() api in Electron w3c/IndexedDB#274.
-
IDBKeyRange.includes or IDBKeyRange._includes? w3c/IndexedDB#270.
-
Extract common steps of `IDBObjectStore`'s `put()` and`add()` w3c/IndexedDB#261.
-
-
1 issue reopened.
-
IDBKeyRange.includes or IDBKeyRange._includes? w3c/IndexedDB#270, by @inexorabletash.
-
-
17 issues received 40 new comments.
-
IDBKeyRange.includes or IDBKeyRange._includes? w3c/IndexedDB#270 (4 comments by @inexorabletash, @mkruisselbrink)
-
Specify keyPath sequence caching behavior on IDBObjectStore w3c/IndexedDB#283 (3 comments by @inexorabletash, @saschanaz)
-
w3c/IndexedDB#261 (2 comments by @inexorabletash)
-
w3c/IndexedDB#191 (1 comment by @NullVoxPopuli)
-
w3c/IndexedDB#64 (1 comment by @inexorabletash)
-
w3c/IndexedDB#91 (1 comment by @inexorabletash)
-
w3c/IndexedDB#141 (1 comment by @inexorabletash)
-
w3c/IndexedDB#222 (1 comment by @inexorabletash)
-
w3c/IndexedDB#245 (1 comment by @inexorabletash)
-
9 pull requests opened.
-
Editorial: Add note about close() being idempotent. w3c/IndexedDB#281, by @inexorabletash.
-
Speculative getAllEntries() spec w3c/IndexedDB#280, by @inexorabletash.
-
Editorial: Replace flag set/unset with true/false. w3c/IndexedDB#279, by @inexorabletash.
-
Editorial: Simplify wording around async request invocation w3c/IndexedDB#278, by @inexorabletash.
-
Editorial: Simplify 'steps to' w3c/IndexedDB#277, by @inexorabletash.
-
Use Infra terms to simplify text. w3c/IndexedDB#275, by @inexorabletash.
-
Editorial: Fix _includes link, add note. w3c/IndexedDB#273, by @inexorabletash.
-
Editorial: Correct linking for IDBKeyRange lowerBound/upperBound w3c/IndexedDB#272, by @inexorabletash.
-
Factor common steps out of add()/put(). w3c/IndexedDB#269, by @inexorabletash.
-
-
9 pull requests merged.
-
Editorial: Add note about close() being idempotent. w3c/IndexedDB#281.
-
Editorial: Replace flag set/unset with true/false. w3c/IndexedDB#279.
-
Use Infra terms to simplify text. w3c/IndexedDB#275.
-
Editorial: Simplify wording around async request invocation w3c/IndexedDB#278.
-
Editorial: Simplify 'steps to' w3c/IndexedDB#277.
-
Editorial: Correct linking for IDBKeyRange lowerBound/upperBound w3c/IndexedDB#272.
-
Editorial: Fix _includes link, add note. w3c/IndexedDB#273.
-
Factor common steps out of add()/put(). w3c/IndexedDB#269.
-
chore(index.bs): now part of webapps WG w3c/IndexedDB#267.
-
-
9 pull requests received 22 new comments.
-
Use Infra terms to simplify text. w3c/IndexedDB#275 (7 comments by @aliams, @aphillips, @inexorabletash)
-
Editorial: Correct linking for IDBKeyRange lowerBound/upperBound w3c/IndexedDB#272 (4 comments by @inexorabletash, @mkruisselbrink)
-
Editorial: Add note about close() being idempotent. w3c/IndexedDB#281 (3 comments by @brettz9, @inexorabletash)
-
Editorial: Simplify wording around async request invocation w3c/IndexedDB#278 (1 comment by @inexorabletash)
-
w3c/using-aria
-
2 issues opened.
-
Move to WebApps WG w3c/using-aria#44, by @marcoscaceres.
-
Link to ARIA-APG is broken. w3c/using-aria#43, by @a11ydoer.
-
-
1 pull request opened.
-
Changed ARIA 1.1 links to 1.2 and HTTPS w3c/using-aria#45, by @aardrian.
-
-
1 pull request received 1 new comment.
w3c/contact-picker
-
1 issue closed.
-
Spec feedback w3c/contact-picker#17.
-
-
3 issues received 3 new comments.
-
Contacts Picker UI should have a "Select All" option w3c/contact-picker#15 (1 comment by @aarongustafson)
-
w3c/FileAPI
-
1 issue opened.
-
Refactor text() et al to share more infrastructure with Fetch w3c/FileAPI#133, by @annevk.
-
-
1 pull request reopened.
-
Modernize Blob constructor a tiny bit w3c/FileAPI#125, by @marcoscaceres.
-
-
1 pull request received 1 new comment.
-
w3c/FileAPI#125 (1 comment by @marcoscaceres)
-
w3c/pointerlock
-
3 pull requests opened.
-
add encrypted token w3c/pointerlock#46, by @siusin.
-
Chore: Spec xref fixup w3c/pointerlock#45, by @marcoscaceres.
-
chore: enable autopub w3c/pointerlock#44, by @marcoscaceres.
-
-
3 pull requests merged.
-
add encrypted token w3c/pointerlock#46.
-
Chore: Spec xref fixup w3c/pointerlock#45.
-
chore: enable autopub w3c/pointerlock#44.
-
-
1 pull request received 1 new comment.
w3c/push-api
-
1 pull request merged.
-
chore(.travis): set up validation w3c/push-api#307.
-
-
1 pull request received 1 new comment.
Lifecycle
-
1 charter started.
-
Chartered until 14 December 2020. Participants had to rejoin under this charter.
-
TR publications
-
21 documents published.
-
ARIA in HTML published twice as a Working Draft. History of ARIA in HTML
-
File API published twice as a Working Draft. History of File API
-
Gamepad published twice as a Working Draft. History of Gamepad
-
HTML Accessibility API Mappings 1.0 published twice as a Working Draft. History of HTML Accessibility API Mappings 1.0
-
Intersection Observer published twice as a Working Draft. History of Intersection Observer
-
The Screen Orientation API published twice as a Working Draft. History of The Screen Orientation API
-
Web App Manifest published twice as a Working Draft. History of Web App Manifest
-
Clipboard API and events published as a Working Draft. History of Clipboard API and events
-
Input Events Level 1 published as a Working Draft. History of Input Events Level 1
-
Input Events Level 2 published as a Working Draft. History of Input Events Level 2
-
Pointer Lock 2.0 published as a Working Draft. History of Pointer Lock 2.0
-
Push API published as a Working Draft. History of Push API
-
Selection API published as a Working Draft. History of Selection API
-
UI Events published as a Working Draft. History of UI Events
-
Participants
-
2 participants joined.
-
Yves Lafon (W3C) joined.
-
Xiaoqian Wu (W3C) joined.
-
-
9 organizations joined.
-
Google LLC joined.
-
Wells Fargo Bank N.A. joined.
-
OpenJS Foundation joined.
-
Deque Systems, Inc. joined.
-
Thinktecture joined.
-
TPGi joined.
-
Intel Corporation joined.
-
TetraLogical Services Ltd joined.
-
Mozilla Foundation joined.
-
GitHub
w3c/contact-picker
-
2 issues opened.
-
Spec feedback w3c/contact-picker#17, by @jakearchibald.
-
Save contact? w3c/contact-picker#16, by @vladimirbrasil.
-
-
3 issues received 4 new comments.
-
Contacts Picker UI should have a "Select All" option w3c/contact-picker#15 (1 comment by @rayankans)
-
1 pull request merged.
-
Create a spec skeleton with a few filled out parts. w3c/contact-picker#14.
-
w3c/pointerlock
-
1 pull request merged.
-
improve markup language w3c/pointerlock#37.
-
w3c/webappswg
-
4 issues opened.
-
Republish GamePad API w3c/webappswg#8, by @marcoscaceres.
-
Republish FileAPI w3c/webappswg#7, by @marcoscaceres.
-
Make sure all WD specs are on auto publish w3c/webappswg#6, by @marcoscaceres.
-
Charter nit with contentEditable w3c/webappswg#5, by @marcoscaceres.
-
-
4 issues closed.
-
Republish FileAPI w3c/webappswg#7.
-
Republish GamePad API w3c/webappswg#8.
-
Charter nit with contentEditable w3c/webappswg#5.
-
Update group ids in all the repos w3c/webappswg#1.
-
-
1 issue reopened.
-
Update group ids in all the repos w3c/webappswg#1, by @marcoscaceres.
-
-
4 issues received 8 new comments.
-
w3c/webappswg#1 (3 comments by @marcoscaceres)
w3c/screen-orientation
-
1 pull request opened.
-
chore(.travis): enable ReSpec validator w3c/screen-orientation#178, by @marcoscaceres.
-
-
1 pull request merged.
-
chore(.travis): enable ReSpec validator w3c/screen-orientation#178.
-
-
1 pull request reopened.
-
chore(.travis): enable ReSpec validator w3c/screen-orientation#178, by @marcoscaceres.
-
w3c/ServiceWorker
-
4 issues opened.
-
Export "clear registration" w3c/ServiceWorker#1410, by @marcoscaceres.
-
Should register() trigger byte-for-byte checking when WorkerType is updated? w3c/ServiceWorker#1408, by @makotoshimazu.
-
Top-level await integration for ServiceWorkers running modules w3c/ServiceWorker#1407, by @littledan.
-
New 'update via cache' value doesn't take effect in register algorithm. w3c/ServiceWorker#1406, by @tingshao.
-
-
9 issues closed.
-
Service-Worker-Allowed can be cross-origin to the script URL. w3c/ServiceWorker#1307.
-
Discuss the maxScopeString and Service-Worker-Allowed in security considerations w3c/ServiceWorker#1405.
-
Client.postMessage() throwing for unloaded client is problematic w3c/ServiceWorker#1291.
-
Add cookie accessor/setter methods? w3c/ServiceWorker#707.
-
importScripts() on ServiceWorkerGlobalScope w3c/ServiceWorker#1319.
-
Align "uncaught runtime script error" with the HTML spec w3c/ServiceWorker#1334.
-
Tracking JS issue in firefox pwa w3c/ServiceWorker#1401.
-
New 'update via cache' value doesn't take effect in register algorithm. w3c/ServiceWorker#1406.
-
Pass credentials on navigator.serviceWorker.register("/service_worker.js"); w3c/ServiceWorker#1399.
-
-
14 issues received 34 new comments.
-
Top-level await integration for ServiceWorkers running modules w3c/ServiceWorker#1407 (9 comments by @jakearchibald, @littledan, @wanderview)
-
w3c/ServiceWorker#1345 (2 comments by @rejhgadellaa)
-
Should register() trigger byte-for-byte checking when WorkerType is updated? w3c/ServiceWorker#1408 (2 comments by @makotoshimazu, @mfalken)
-
New 'update via cache' value doesn't take effect in register algorithm. w3c/ServiceWorker#1406 (2 comments by @makotoshimazu, @tingshao)
-
w3c/ServiceWorker#1405 (1 comment by @mfalken)
-
w3c/ServiceWorker#707 (1 comment by @mfalken)
-
w3c/ServiceWorker#1319 (1 comment by @mfalken)
-
w3c/ServiceWorker#1334 (1 comment by @mfalken)
-
w3c/ServiceWorker#1401 (1 comment by @mfalken)
-
w3c/ServiceWorker#1399 (1 comment by @SystemR)
-
-
1 pull request opened.
-
Refinements and description of Service-Worker-Allowed. w3c/ServiceWorker#1409, by @mfalken.
-
-
2 pull requests merged.
-
Refinements and description of Service-Worker-Allowed. w3c/ServiceWorker#1409.
-
Make Client.postMessage to unloaded client not throw w3c/ServiceWorker#1293.
-
-
2 pull requests received 8 new comments.
-
Refinements and description of Service-Worker-Allowed. w3c/ServiceWorker#1409 (7 comments by @jakearchibald, @mfalken)
-
w3c/ServiceWorker#1293 (1 comment by @jungkees)
-
w3c/gamepad
-
1 issue opened.
-
Clarify what "up" and "down" mean for input axes w3c/gamepad#94, by @jacobcdewitt.
-
-
4 issues received 4 new comments.
-
w3c/gamepad#88 (1 comment by @sagoston)
-
w3c/gamepad#83 (1 comment by @marcoscaceres)
-
w3c/gamepad#77 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
chore(travis): perform spec validation w3c/gamepad#95, by @marcoscaceres.
-
-
1 pull request merged.
-
chore(travis): perform spec validation w3c/gamepad#95.
-
w3c/push-api
-
2 issues received 2 new comments.
-
w3c/push-api#292 (1 comment by @beverloo)
-
w3c/push-api#212 (1 comment by @ghost)
-
-
1 pull request opened.
-
chore(.travis): set up validation w3c/push-api#307, by @marcoscaceres.
-
-
1 pull request received 5 new comments.
w3c/FileAPI
-
1 issue opened.
-
"Code point" should point to infra w3c/FileAPI#130, by @marcoscaceres.
-
-
2 issues closed.
-
"Code point" should point to infra w3c/FileAPI#130.
-
Implementer interest in this spec w3c/FileAPI#111.
-
-
1 issue received 1 new comment.
-
w3c/FileAPI#111 (1 comment by @marcoscaceres)
-
-
4 pull requests opened.
-
chore(travis): email Marcos auto-pub result w3c/FileAPI#132, by @marcoscaceres.
-
editorial: use infra code point w3c/FileAPI#131, by @marcoscaceres.
-
chore(.travis): enable auto-publish w3c/FileAPI#129, by @marcoscaceres.
-
chore(index.bs): now part of webapps WG w3c/FileAPI#128, by @marcoscaceres.
-
-
4 pull requests merged.
-
chore(travis): email Marcos auto-pub result w3c/FileAPI#132.
-
chore(.travis): enable auto-publish w3c/FileAPI#129.
-
editorial: use infra code point w3c/FileAPI#131.
-
chore(index.bs): now part of webapps WG w3c/FileAPI#128.
-
-
3 pull requests reopened.
-
chore(travis): email Marcos auto-pub result w3c/FileAPI#132, by @deniak.
-
chore(travis): email Marcos auto-pub result w3c/FileAPI#132, by @marcoscaceres.
-
chore(travis): email Marcos auto-pub result w3c/FileAPI#132, by @marcoscaceres.
-
-
4 pull requests received 18 new comments.
-
chore(.travis): enable auto-publish w3c/FileAPI#129 (13 comments by @deniak, @marcoscaceres, @mkruisselbrink, @siusin)
-
chore(index.bs): now part of webapps WG w3c/FileAPI#128 (2 comments by @marcoscaceres, @mkruisselbrink)
-
w3c/web-share
-
1 issue opened.
-
Intent to Migrate Web Share API w3c/web-share#99, by @marcoscaceres.
-
-
1 issue received 5 new comments.
-
Intent to Migrate Web Share API w3c/web-share#99 (5 comments by @ewilligers, @hober, @marcoscaceres)
-
w3c/manifest
-
1 issue opened.
-
Add Manifest property to hint whether the navigation UI should be visible w3c/manifest#765, by @mounirlamouri.
-
-
1 issue closed.
-
Manifast and Service Worker updateViaCache w3c/manifest#690.
-
-
2 pull requests opened.
-
Export WebAppManifest dfn as a dictionary w3c/manifest#767, by @jyasskin.
-
Add navigation_ui property (fixes #765). w3c/manifest#766, by @mounirlamouri.
-
-
1 pull request merged.
-
Respec validator w3c/manifest#740.
-
-
2 pull requests received 4 new comments.
-
Add navigation_ui property (fixes #765). w3c/manifest#766 (2 comments by @marcoscaceres, @mounirlamouri)
-
Export WebAppManifest dfn as a dictionary w3c/manifest#767 (2 comments by @jyasskin, @marcoscaceres)
-
w3c/IndexedDB
-
1 issue opened.
-
FPWD of v3? w3c/IndexedDB#268, by @marcoscaceres.
-
-
1 issue closed.
-
Integrate with window.onerror w3c/IndexedDB#49.
-
-
3 issues received 6 new comments.
-
1 pull request opened.
-
chore(index.bs): now part of webapps WG w3c/IndexedDB#267, by @marcoscaceres.
-
-
1 pull request received 1 new comment.
w3c/badging
-
5 issues opened.
-
Notification Background Updates w3c/badging#28, by @docluv.
-
Desktop App Badge w3c/badging#27, by @docluv.
-
Add security/privacy section w3c/badging#25, by @marcoscaceres.
-
Add accessibility section w3c/badging#24, by @marcoscaceres.
-
Add internationalization section w3c/badging#23, by @marcoscaceres.
-
-
1 issue received 1 new comment.
w3c/uievents
-
1 issue opened.
-
Don't redefine event target w3c/uievents#231, by @annevk.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
docs(README): Remove meetings timetable w3c/uievents#234, by @marcoscaceres.
-
Switch to WebAppsWG w3c/uievents#232, by @marcoscaceres.
-
-
4 pull requests merged.
-
docs(README): Remove meetings timetable w3c/uievents#234.
-
Minor tweaks to wording and capitalisation w3c/uievents#204.
-
chore:add PULL_REQUEST_TEMPLATE.md w3c/uievents#215.
-
Switch to WebAppsWG w3c/uievents#232.
-
w3c/uievents-code
-
1 pull request opened.
-
Switch to webapps wg w3c/uievents-code#26, by @marcoscaceres.
-
-
2 pull requests merged.
-
Switch to webapps wg w3c/uievents-code#26.
-
chore:add PULL_REQUEST_TEMPLATE.md w3c/uievents-code#23.
-
-
1 pull request received 1 new comment.
w3c/uievents-key
-
1 issue opened.
-
Where is the .bs file? w3c/uievents-key#51, by @marcoscaceres.
-
-
1 issue closed.
-
Where is the .bs file? w3c/uievents-key#51.
-
-
1 issue received 1 new comment.