References for Web Specifications (http://webref.herokuapp.com/)
dontcallmedom/api-design-cookbook 2
A cookbook for Web API design
A node-based Web app to record and play a distributed canon song (Frère Jacques for now)
Web Vision
dontcallmedom/adoption-monitor 1
https://dontcallmedom.github.io/adoption-monitor/
:bike: A preprocessor for anyone writing specifications that converts source files into actual specs.
An HTML-based code displayer, that allows to talk through the creation of a piece of a code (e.g. for a tutorial)
The ownCloud Android App
Accessible Platform Architectures WG deliverables
PR opened w3c/webrtc-pc
Automated changes by create-pull-request GitHub action
pr created time in 2 days
PR closed w3c/webrtc-pc
Automated changes by create-pull-request GitHub action
pr closed time in 9 days
pull request commentw3c/webrtc-pc
Update to latest ReSpec version
needs the changes in #2663, so closing without merging
comment created time in 9 days
push eventw3c/mediacapture-main
commit sha 66835270e230ce54b750ec17f5bda355d05bddb1
Update to latest ReSpec version
commit sha 3037fc11efeaeca17653de0e83469f55d9b2d35a
Merge pull request #807 from w3c/respec-26.9.4 Update to latest ReSpec version
push time in 9 days
PR merged w3c/mediacapture-main
Automated changes by create-pull-request GitHub action
pr closed time in 9 days
pull request commentw3c/browser-specs
given that it's unlikely to be browser targeting, is there any reason not to put it in the ignore list?
comment created time in 9 days
PR opened w3c/webrtc-pc
Automated changes by create-pull-request GitHub action
pr created time in 9 days
PR opened w3c/mediacapture-main
Automated changes by create-pull-request GitHub action
pr created time in 9 days
issue commentw3c/ash-nazg
Work jointly done by a CG & a WG
no work needed in ash-nazg on this, closing the issue
comment created time in 12 days
issue closedw3c/ash-nazg
Work jointly done by a CG & a WG
There are at least two reasonably clear cases of WGs that want to operate their repositories under the joint aegis of a WG and a CG: WebAssembly and WebGPU.
Right now, the IPR manager isn't able to handle this case, and requires joint work to be under groups of the same type (either several WGs, or several CGs).
A possible model for an IPR check on joint CG/WG work would be:
- if contributor is covered by WG IPR commitment, OK
- if contributor is covered by CG IPR commitment (but not WG), flag the need to obtain an FSA commitment
- otherwise, flag as needing action
@wseltzer thoughts?
closed time in 12 days
dontcallmedomissue commentmdn/browser-compat-data
Issue with "KeyboardEvent.metaKey": I don't think this works on Firefox but is marked as compatible
Would it be worth documenting in the BCD section itself (and thus in the data) the fact that the Windows key is no longer considered the metaKey since FF48?
comment created time in 12 days
pull request commentw3c/webrtc-identity
Upgrade respec version to deal with latest WebIDL support
The error linked to [[IsClosed]] is a combination of waiting for a respec upgrade in WebRTC, and then the WebRTC spec needing to mark the said internal slot as exported.
Since the current spec is more broken than this, I'll merge with error pending.
comment created time in 13 days
push eventw3c/webrtc-identity
commit sha e6b246d087e7145dcd5a4216315a568fdb0ac521
Use reference to internal slot for IsClosed
push time in 13 days
issue commentmdn/content
Issue with "KeyboardEvent.metaKey": I don't think this works on Firefox but is marked as compatible
(this should be moved to browser-compat-data in any case)
comment created time in 13 days
issue closedw3c/ash-nazg
Metaverse Interoperability Community Group missing from list
I'm trying to import a repository in to the repo manager, but our community group isn't on the list of groups. Could add the metaverse-interop community group? I'm trying to add the IPR bot, w3c.json, etc. Thanks!
closed time in 13 days
robertlongissue openedw3c/ash-nazg
There are at least two ways the checker can fail to process a pull request:
- it doesn't recognize the repo (e.g. after a name change #64)
- the secret used to verify the origin of the check is wrong (which has happened a number of times, although I'm not sure how)
… and probably more. Right now, these failures are simply logged as a webook failure - useful for debugging, not for noticing there is a configuration issue.
These should instead be reported - either on the pull request itself, or on this repo (probably both - e.g. it could stay in "pending" state on the pull request status with an appropriate message, while reporting the issue here).
created time in 13 days
issue commentw3c/ash-nazg
Metaverse Interoperability Community Group missing from list
group now added - let us know if you encounter any other hiccup in the process
comment created time in 13 days