W3C mailing list search service
Search among 2,305,887 messages in the W3C mailing list archives:
Daily github digest (i18n review comments)
- Date
- Mon, 23 Feb 2026 00:04:13 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * w3c/csswg-drafts (+0/-0/💬1) 1 i
Daily github digest (i18n review comments)
- Date
- Sat, 21 Feb 2026 00:04:25 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * w3c/csswg-drafts (+0/-0/💬3) 2 i
Daily github digest (i18n review comments)
- Date
- Fri, 20 Feb 2026 00:04:32 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * w3c/csswg-drafts (+1/-0/💬0) 1 i
Weekly github digest (Review comments)
- List
- public-i18n-core
- Date
- Wed, 18 Feb 2026 17:06:01 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * w3c/data-shapes (+0/-1/💬1) 1 is
Daily github digest (i18n review comments)
- Date
- Wed, 18 Feb 2026 00:04:40 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * w3c/data-shapes (+0/-1/💬1) 1 is
Re: Public Comment on Proposed DCMI Term: Accessibility Note
- Date
- Mon, 16 Feb 2026 17:33:27 +0000
- Author
- Phil Barker <phil.barker@pjjk.co.uk>
Thank you all for your consideration of this proposal, and for the comment on it which is much appreciated. The DCMI Usage Board will be considering all the comments at the end of the comment period.
RE: Public Comment on Proposed DCMI Term: Accessibility Note
- Date
- Thu, 12 Feb 2026 21:24:10 +0530
- Author
- "Avneesh Singh" <avneesh.sg@gmail.com>
Thanks Phil, I have added it to today’s accessibility task force agenda. With regards Avneesh From: Phil Barker <phil.barker@pjjk.co.uk> Sent: Thursday, February 12, 2026 4:10 PM To: public-publish
Public Comment on Proposed DCMI Term: Accessibility Note
- Date
- Thu, 12 Feb 2026 10:39:50 +0000
- Author
- Phil Barker <phil.barker@pjjk.co.uk>
Dear All, I hope this is appropriate for this list and relevant to those of you with an interest in metadata and accessibility. I would like to share the information that DCMI (Dublin Core Metadata I
Weekly github digest (Review comments)
- List
- public-i18n-core
- Date
- Wed, 11 Feb 2026 17:06:16 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * w3c/csswg-drafts (+1/-0/💬3) 1 i
Daily github digest (i18n review comments)
- Date
- Tue, 10 Feb 2026 00:04:46 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * w3c/csswg-drafts (+1/-0/💬3) 1 i
Daily github digest (i18n review comments)
- Date
- Sun, 08 Feb 2026 00:04:23 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * w3c/wcag3 (+0/-0/💬2) 2 issues r
Daily github digest (i18n review comments)
- Date
- Fri, 06 Feb 2026 00:04:46 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * whatwg/html (+0/-0/💬1) 1 issues
Daily github digest (i18n review comments)
- Date
- Thu, 05 Feb 2026 00:04:41 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * whatwg/html (+0/-0/💬1) 1 issues
Weekly github digest (Review comments)
- List
- public-i18n-core
- Date
- Wed, 04 Feb 2026 17:06:11 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * whatwg/html (+0/-0/💬7) 1 issues
Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Date
- Wed, 04 Feb 2026 05:44:41 -0800
- Author
- Noam Rosenthal <notifications@github.com>
noamr left a comment (WICG/webcomponents#1116) It creates an addressable syntax that can have semantics (e.g. for streaming, range highlights, buffering control flow) but doesn't interfere with the n
Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Date
- Wed, 04 Feb 2026 05:36:41 -0800
- Author
- Steve Orvell <notifications@github.com>
sorvell left a comment (WICG/webcomponents#1116) Can you explain why? Is it because it creates new space in the syntax to describe API? -- Reply to this email directly or view it on GitHub: https://g
Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Date
- Tue, 03 Feb 2026 23:18:50 -0800
- Author
- Noam Rosenthal <notifications@github.com>
noamr left a comment (WICG/webcomponents#1116) No it would just be a processing instruction. We analyzed the HTTP archive and there is very little use of PI syntax in the wild. If there are particula
Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Date
- Tue, 03 Feb 2026 19:58:46 -0800
- Author
- Justin Fagnani <notifications@github.com>
justinfagnani left a comment (WICG/webcomponents#1116) How would that be done in a backwards compatible way? Would processing instruction be a subclass ofb comment? Would they be returned in contexts
Daily github digest (i18n review comments)
- Date
- Wed, 04 Feb 2026 00:04:45 +0000
- Author
- W3C Webmaster via GitHub API <noreply@w3.org>
Events with label "HR:i18n-comment", "HR:i18n-tracking", "i18n", "i18n-comment", "i18n-needs-resolution", "i18n-review", "i18n-tracker", "i18n-tracking" Issues -- * whatwg/html (+0/-0/💬4) 1 issues
Re: Éric Vyncke's No Objection on draft-ietf-httpbis-incremental-03: (with COMMENT)
- List
- ietf-http-wg
- Date
- Wed, 04 Feb 2026 10:03:11 +1100
- Author
- "Martin Thomson" <mt@lowentropy.net>
Hi Éric, We're dealing with these in some greater detail in responses to Med and Roman. Thanks for highlighting that. The "SHOULD" usage in this document is unfortunate, but a consequence of the pro
Help and hints for using this service
W3C Member? Check the Member-only interface. W3C staff? Use the Team-only interface.