Technical Architecture Group - Activity in 2024
No matches.
TR publications
-
1 document published.
-
Ethical Web Principles published as a Statement. History of Ethical Web Principles
-
Past meetings
-
13 meetings.
GitHub
w3ctag/tag.w3.org
-
5 pull requests opened.
-
Align the explainer template with the explainer explainer. w3ctag/tag.w3.org#58, by @jyasskin.
-
Reorganize the Explainer Explainer, take 2 w3ctag/tag.w3.org#57, by @jyasskin.
-
Build a history of TAG Associates' service. w3ctag/tag.w3.org#56, by @jyasskin.
-
Update history with 2024 election results, and fix some older data. w3ctag/tag.w3.org#55, by @dbaron.
-
Remove two duplicate links from the list of Findings. w3ctag/tag.w3.org#54, by @jyasskin.
-
-
1 pull request merged.
-
Update history with 2024 election results, and fix some older data. w3ctag/tag.w3.org#55.
-
-
1 pull request received 1 new comment.
-
Update history with 2024 election results, and fix some older data. w3ctag/tag.w3.org#55 (1 comment by @dbaron)
-
w3ctag/ethical-web-principles
-
3 issues opened.
-
What are "our websites"? w3ctag/ethical-web-principles#144, by @jyasskin.
-
Please help to clarify "authors" in 1.1 w3ctag/ethical-web-principles#141, by @lianqi.
-
2.12 People should be able to choose how they engage with the web w3ctag/ethical-web-principles#140, by @mgifford.
-
-
1 issue closed.
-
Oxford comma w3ctag/ethical-web-principles#132.
-
-
3 issues received 5 new comments.
-
Please help to clarify "authors" in 1.1 w3ctag/ethical-web-principles#141 (3 comments by @jyasskin, @lianqi)
-
New principal: help businesses and individuals succeed through automation of base principals w3ctag/ethical-web-principles#128 (1 comment by @mgifford)
-
-
4 pull requests opened.
-
Clarify informing a broader scope of technical and community reports w3ctag/ethical-web-principles#143, by @csarven.
-
Switch [spec] authors to "editors" in the Purpose section. w3ctag/ethical-web-principles#142, by @jyasskin.
-
the W3C -> W3C per recommended usage w3ctag/ethical-web-principles#139, by @ylafon.
-
editorial change in Section 1.1 w3ctag/ethical-web-principles#138, by @ylafon.
-
-
3 pull requests merged.
-
editorial change in Section 1.1 w3ctag/ethical-web-principles#138.
-
Fix some commas w3ctag/ethical-web-principles#136.
-
Address [objectors'] Proposal w3ctag/ethical-web-principles#135.
-
-
2 pull requests received 4 new comments.
-
Switch [spec] authors to "editors" in the Purpose section. w3ctag/ethical-web-principles#142 (3 comments by @csarven, @jyasskin)
-
Clarify informing a broader scope of technical and community reports w3ctag/ethical-web-principles#143 (1 comment by @jyasskin)
-
w3ctag/design-reviews
-
7 issues opened.
-
Custom Functions (@function) w3ctag/design-reviews#1031, by @andruud.
-
[HTML] 2D canvas floating point support w3ctag/design-reviews#1030, by @ccameron-chromium.
-
Final Review Request of seven (7) W3C VCWG Specifications w3ctag/design-reviews#1029, by @msporny.
-
CSS `dynamic-range-limit` w3ctag/design-reviews#1027, by @ccameron-chromium.
-
WebRTC API Proposed Amendments w3ctag/design-reviews#1026, by @dontcallmedom.
-
CSS Inline `text-box`, `text-box-trim`, and `text-box-edge` properties w3ctag/design-reviews#1021, by @kojiishi.
-
-
10 issues closed.
-
HTMLSelectElement showPicker() w3ctag/design-reviews#900.
-
Captured Surface Control w3ctag/design-reviews#962.
-
CSS reading-flow property w3ctag/design-reviews#978.
-
EPUB 3.3 Recommendation with Candidate Corrections 2024-10-17 > 2024-12-19 w3ctag/design-reviews#1006.
-
Early Design Review: Allowing First-Party SameSite=None Cookies in Sandboxed Contexts w3ctag/design-reviews#1004.
-
[Handwriting] Add Handwriting CSS Value w3ctag/design-reviews#1018.
-
Controller Documents v1.0 w3ctag/design-reviews#960.
-
Web Authentication's PublicKeyCredential signal methods w3ctag/design-reviews#996.
-
هلا w3ctag/design-reviews#1028.
-
Vision for W3C: request horizontal architectural review and wide TAG review w3ctag/design-reviews#1008.
-
-
19 issues received 27 new comments.
-
[Handwriting] Add Handwriting CSS Value w3ctag/design-reviews#1018 (2 comments by @martinthomson, @slightlyoff)
-
Early Design Review: Partitioned Popins w3ctag/design-reviews#956 (2 comments by @johannhof, @plinss)
-
Fenced frames with local unpartitioned data access w3ctag/design-reviews#975 (2 comments by @shivanigithub)
-
[HTML] 2D canvas floating point support w3ctag/design-reviews#1030 (1 comment by @ccameron-chromium)
-
EPUB 3.3 Recommendation with Candidate Corrections 2024-10-17 > 2024-12-19 w3ctag/design-reviews#1006 (1 comment by @hadleybeeman)
-
Early Design Review: Allowing First-Party SameSite=None Cookies in Sandboxed Contexts w3ctag/design-reviews#1004 (1 comment by @jyasskin)
-
Web Authentication's PublicKeyCredential signal methods w3ctag/design-reviews#996 (1 comment by @maxpassion)
-
Vision for W3C: request horizontal architectural review and wide TAG review w3ctag/design-reviews#1008 (1 comment by @jyasskin)
-
3 pull requests opened.
-
Add a link to the early design review in the specification review request w3ctag/design-reviews#1032, by @jyasskin.
-
Create an issue template for questions w3ctag/design-reviews#1025, by @martinthomson.
-
Update first_party_sets_feedback.md w3ctag/design-reviews#1022, by @torgo.
-
-
2 pull requests merged.
-
Create an issue template for questions w3ctag/design-reviews#1025.
-
Update first_party_sets_feedback.md w3ctag/design-reviews#1022.
-
-
2 pull requests received 2 new comments.
w3ctag/user-agents
-
3 issues opened.
-
Elaborate the ecosystem section w3ctag/user-agents#3, by @jyasskin.
-
Do we need a "discretion" duty? w3ctag/user-agents#2, by @jyasskin.
-
Try to find a better name for the "Honesty" duty w3ctag/user-agents#1, by @jyasskin.
-
w3ctag/design-principles
-
10 issues opened.
-
Improve link text for RFC 9205 w3ctag/design-principles#545, by @martinthomson.
-
New principle: Don't invent something new just because the existing thing isn't perfect w3ctag/design-principles#539, by @martinthomson.
-
New principle: Write [Symbol.dispose]() and [Symbol.asyncDispose]() methods when appropriate w3ctag/design-principles#537, by @jyasskin.
-
Consider adding publishers into the Priority of Constituencies w3ctag/design-principles#535, by @jyasskin.
-
Additional examples around element overloading w3ctag/design-principles#533, by @LeaVerou.
-
New principle: Avoid introducing mode errors w3ctag/design-principles#532, by @LeaVerou.
-
Reduce specific guidance in textual formats principle and link to other principles instead w3ctag/design-principles#531, by @LeaVerou.
-
Assistive technologies: tightening up the text w3ctag/design-principles#529, by @hadleybeeman.
-
New principle: Capabilities are just like devices w3ctag/design-principles#526, by @martinthomson.
-
Advice for list types does not belong in section about default values w3ctag/design-principles#523, by @plinss.
-
-
17 issues closed.
-
New principle: Patterns for URLs in APIs w3ctag/design-principles#303.
-
"while a JavaScript event loop is running." is probably not intended w3ctag/design-principles#456.
-
New principle: Discourage overloading (in HTML) w3ctag/design-principles#370.
-
New principle: Text-based syntaxes should be designed to be usable by humans w3ctag/design-principles#453.
-
Assistive technology emphasis adjustments w3ctag/design-principles#498.
-
New principle: Capabilities are just like devices w3ctag/design-principles#526.
-
Terminology jumps away from principle's subject ("Use care when exposing identifying information about devices") w3ctag/design-principles#479.
-
New principle: Guidance on options dictionaries and default values w3ctag/design-principles#391.
-
Encourage UTF-8 for new formats and APIs w3ctag/design-principles#322.
-
New principle: don't break core part of the web platform in order to enable embellishments w3ctag/design-principles#493.
-
"Make method arguments optional if possible" section has bad advice w3ctag/design-principles#437.
-
Link errors in current w3ctag/design-principles#484.
-
New principle: balancing privacy and other concerns w3ctag/design-principles#511.
-
New Principle: Use `[Exposed=*]` to make only purely computational APIs available w3ctag/design-principles#509.
-
Guidance for when to use inheritance vs composition w3ctag/design-principles#298.
-
Guidance about return values of (conceptually) void functions w3ctag/design-principles#286.
-
Principle against overfitting w3ctag/design-principles#513.
-
-
19 issues received 37 new comments.
-
New principle: Write [Symbol.dispose]() and [Symbol.asyncDispose]() methods when appropriate w3ctag/design-principles#537 (4 comments by @annevk, @syg)
-
I18N string best practices vs. design-principles w3ctag/design-principles#454 (4 comments by @annevk, @aphillips, @jyasskin, @ylafon)
-
Consider adding publishers into the Priority of Constituencies w3ctag/design-principles#535 (3 comments by @annevk, @cwilso, @martinthomson)
-
New principle: Patterns for URLs in APIs w3ctag/design-principles#303 (3 comments by @annevk, @jyasskin, @ylafon)
-
Assistive technologies: tightening up the text w3ctag/design-principles#529 (3 comments by @alice, @jcsteh)
-
Assistive technology emphasis adjustments w3ctag/design-principles#498 (2 comments by @hadleybeeman, @nigelmegitt)
-
New principle: balancing privacy and other concerns w3ctag/design-principles#511 (2 comments by @martinthomson)
-
New principle: don't break core part of the web platform in order to enable embellishments w3ctag/design-principles#493 (2 comments by @hober, @LeaVerou)
-
Harmonize with WebAppSec Powerful Features Draft w3ctag/design-principles#481 (2 comments by @jyasskin)
-
New principle: How to attach meta-information to a document w3ctag/design-principles#506 (2 comments by @bkardell, @LeaVerou)
-
New principle: Don't invent something new just because the existing thing isn't perfect w3ctag/design-principles#539 (1 comment by @csarven)
-
New principle: Discourage overloading (in HTML) w3ctag/design-principles#370 (1 comment by @LeaVerou)
-
Reduce specific guidance in textual formats principle and link to other principles instead w3ctag/design-principles#531 (1 comment by @martinthomson)
-
New Principle: Use `[Exposed=*]` to make only purely computational APIs available w3ctag/design-principles#509 (1 comment by @LeaVerou)
-
What should the casing rules be for headers? w3ctag/design-principles#422 (1 comment by @martinthomson)
-
-
20 pull requests opened.
-
Merge the HTTP guidance into the "consult other specs" section. w3ctag/design-principles#546, by @jyasskin.
-
Switch the GH Action to spec-prod. w3ctag/design-principles#544, by @jyasskin.
-
Fix the bikeshed warnings. w3ctag/design-principles#543, by @jyasskin.
-
Add a section about looking for guidance in other specs. w3ctag/design-principles#542, by @jyasskin.
-
Add Martin and Jeffrey as co-editors; remove Sangwhan. w3ctag/design-principles#541, by @jyasskin.
-
Correct grammatical error w3ctag/design-principles#540, by @martinthomson.
-
Whitespace not white space w3ctag/design-principles#538, by @martinthomson.
-
Improve the run-to-completion principle. w3ctag/design-principles#536, by @jyasskin.
-
Use more semantic references to HTTP RFCs. w3ctag/design-principles#534, by @jyasskin.
-
add TAG alumni to the list of Acknowledgments w3ctag/design-principles#530, by @ylafon.
-
Friendly amendments to #521 w3ctag/design-principles#528, by @martinthomson.
-
Capabilities and devices w3ctag/design-principles#527, by @martinthomson.
-
Device access permissions and fingerprinting w3ctag/design-principles#525, by @martinthomson.
-
Only use UTF-8 for #322 w3ctag/design-principles#524, by @rhiaro.
-
Default values should be the common choice w3ctag/design-principles#522, by @martinthomson.
-
Modify "leave the web better" to add statement addressing 493 w3ctag/design-principles#521, by @torgo.
-
These are abominable w3ctag/design-principles#520, by @martinthomson.
-
Update Permissions / Powerful APIs (1.4) w3ctag/design-principles#519, by @torgo.
-
Correct bad advice on undefined conversion w3ctag/design-principles#518, by @martinthomson.
-
adding a note to ensure consistency with 'Defining string' section of [international-spec] w3ctag/design-principles#517, by @ylafon.
-
-
28 pull requests merged.
-
Add a section about looking for guidance in other specs. w3ctag/design-principles#542.
-
Improve the run-to-completion principle. w3ctag/design-principles#536.
-
Switch the GH Action to spec-prod. w3ctag/design-principles#544.
-
Fix the bikeshed warnings. w3ctag/design-principles#543.
-
Add Martin and Jeffrey as co-editors; remove Sangwhan. w3ctag/design-principles#541.
-
Use more semantic references to HTTP RFCs. w3ctag/design-principles#534.
-
Correct grammatical error w3ctag/design-principles#540.
-
Whitespace not white space w3ctag/design-principles#538.
-
Establish a rule about element overloading w3ctag/design-principles#502.
-
add TAG alumni to the list of Acknowledgments w3ctag/design-principles#530.
-
Text formats are for people w3ctag/design-principles#505.
-
Friendly amendments to #521 w3ctag/design-principles#528.
-
Device access permissions and fingerprinting w3ctag/design-principles#525.
-
Default values should be the common choice w3ctag/design-principles#522.
-
Only use UTF-8 for #322 w3ctag/design-principles#524.
-
adding a note to ensure consistency with 'Defining string' section of [international-spec] w3ctag/design-principles#517.
-
Update Permissions / Powerful APIs (1.4) w3ctag/design-principles#519.
-
Modify "leave the web better" to add statement addressing 493 w3ctag/design-principles#521.
-
Correct bad advice on undefined conversion w3ctag/design-principles#518.
-
These are abominable w3ctag/design-principles#520.
-
Readme and more w3ctag/design-principles#515.
-
Remove extensible web text w3ctag/design-principles#516.
-
New text for guidance on exposing interfaces everywhere w3ctag/design-principles#510.
-
Prefer composition w3ctag/design-principles#504.
-
New principle: Return undefined from side-effect-causing functions. w3ctag/design-principles#500.
-
Update principle on HTTP usage w3ctag/design-principles#487.
-
Update CODE_OF_CONDUCT.md to point to new w3c code w3ctag/design-principles#482.
-
Fix typos. w3ctag/design-principles#508.
-
-
3 pull requests closed.
-
First pass at #453 (text-based syntaxes should be designed for humans) w3ctag/design-principles#472.
-
Capabilities and devices w3ctag/design-principles#527.
-
Add principle on use of delta seconds w3ctag/design-principles#467.
-
-
19 pull requests received 68 new comments.
-
Improve the run-to-completion principle. w3ctag/design-principles#536 (28 comments by @annevk, @dbaron, @jakearchibald, @jan-ivar, @jyasskin, @martinthomson)
-
Add a section about looking for guidance in other specs. w3ctag/design-principles#542 (7 comments by @annevk, @cynthia, @jyasskin, @martinthomson)
-
Device access permissions and fingerprinting w3ctag/design-principles#525 (5 comments by @jyasskin, @martinthomson)
-
Switch the GH Action to spec-prod. w3ctag/design-principles#544 (3 comments by @jyasskin, @martinthomson)
-
Editorial updates to media types section w3ctag/design-principles#488 (3 comments by @annevk, @martinthomson)
-
Update Permissions / Powerful APIs (1.4) w3ctag/design-principles#519 (3 comments by @jyasskin, @martinthomson)
-
Merge the HTTP guidance into the "consult other specs" section. w3ctag/design-principles#546 (2 comments by @jyasskin, @martinthomson)
-
adding a note to ensure consistency with 'Defining string' section of [international-spec] w3ctag/design-principles#517 (2 comments by @jyasskin)
-
New principle: A Promise represents completion or a value, not a callback (#342) w3ctag/design-principles#496 (1 comment by @jyasskin)
-
First pass at #453 (text-based syntaxes should be designed for humans) w3ctag/design-principles#472 (1 comment by @plinss)
-
Modify "leave the web better" to add statement addressing 493 w3ctag/design-principles#521 (1 comment by @rhiaro)
-
w3ctag/societal-impact-questionnaire
-
1 issue closed.
-
Surveillance w3ctag/societal-impact-questionnaire#3.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Question: surveillence (for #3) w3ctag/societal-impact-questionnaire#9.
-
w3ctag/.github
-
1 pull request opened.
-
Create CODE_OF_CONDUCT.md w3ctag/.github#1, by @jyasskin.
-
w3ctag/gaps
-
2 issues opened.
-
Service discovery w3ctag/gaps#10, by @plinss.
-
HTTP for non-global namespaces w3ctag/gaps#9, by @martinthomson.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
fix URL w3ctag/gaps#3.
-
w3ctag/tracking-issues
-
1 issue closed.
-
negative value for gamepad id w3ctag/tracking-issues#1.
-
TR publications
-
1 document published.
-
Privacy Principles published as a Note. History of Privacy Principles
-
Past meetings
-
14 meetings.
GitHub
w3ctag/design-reviews
-
10 issues opened.
-
CSP report-hash keyword w3ctag/design-reviews#1020, by @yoavweiss.
-
Normative Changes of the Input Events Level 2 w3ctag/design-reviews#1019, by @siusin.
-
[Handwriting] Add Handwriting CSS Value w3ctag/design-reviews#1018, by @gastonrod.
-
ClipboardChange event API w3ctag/design-reviews#1017, by @roraja.
-
FYI - Web Authentication API: PublicKeyCredential’s getClientCapabilities() method w3ctag/design-reviews#1016, by @natiahlyi.
-
Payment link type in HTML w3ctag/design-reviews#1015, by @ynyhxfo.
-
Document-Policy: expect-no-linked-resources w3ctag/design-reviews#1014, by @alexnj.
-
Paint/presentation timestamps in performance APIs w3ctag/design-reviews#1013, by @noamr.
-
User-defined script "entry points" for performance timing w3ctag/design-reviews#1012, by @noamr.
-
Spec Review for scroll-start-target w3ctag/design-reviews#1011, by @DavMila.
-
-
11 issues closed.
-
Fenced frames with local unpartitioned data access w3ctag/design-reviews#975.
-
Web Install API - Cross-Origin w3ctag/design-reviews#946.
-
Review for Protected Audiences Bidding and Auction Services API w3ctag/design-reviews#1009.
-
Customizable select element w3ctag/design-reviews#1007.
-
CSS Masonry Layout w3ctag/design-reviews#1003.
-
Element Capture w3ctag/design-reviews#954.
-
Reference Target w3ctag/design-reviews#961.
-
Spec review for Animation.progress w3ctag/design-reviews#994.
-
Early review request for "Explicit JavaScript Compile Hints" w3ctag/design-reviews#947.
-
CSS :open pseudo-class w3ctag/design-reviews#1010.
-
Spec Review for scroll-start-target w3ctag/design-reviews#1011.
-
-
2 issues reopened.
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875, by @torgo.
-
CSS advanced attr() function w3ctag/design-reviews#513, by @dbaron.
-
-
26 issues received 61 new comments.
-
Reference Target w3ctag/design-reviews#961 (9 comments by @alice, @dandclark, @LeaVerou, @matatk, @sorvell)
-
CSS reading-flow property w3ctag/design-reviews#978 (5 comments by @dizhang168, @matatk, @tabatkins)
-
Fenced frames with local unpartitioned data access w3ctag/design-reviews#975 (4 comments by @jyasskin, @martinthomson, @shivanigithub)
-
[Handwriting] Add Handwriting CSS Value w3ctag/design-reviews#1018 (4 comments by @gastonrod, @jyasskin)
-
Dispatching Toggle Events for Dialog open/close w3ctag/design-reviews#1005 (4 comments by @jyasskin, @keithamus)
-
Review for Protected Audiences Bidding and Auction Services API w3ctag/design-reviews#1009 (3 comments by @jyasskin)
-
Early Design Review: Partitioned Popins w3ctag/design-reviews#956 (2 comments by @johannhof, @torgo)
-
Web Authentication's PublicKeyCredential signal methods w3ctag/design-reviews#996 (2 comments by @jyasskin, @maxpassion)
-
Accessibility conformance Testing (ACT) Rules Format 1.1 w3ctag/design-reviews#977 (1 comment by @matatk)
-
Vision for W3C: request horizontal architectural review and wide TAG review w3ctag/design-reviews#1008 (1 comment by @jyasskin)
-
Early review request for "Explicit JavaScript Compile Hints" w3ctag/design-reviews#947 (1 comment by @torgo)
-
Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute w3ctag/design-reviews#1000 (1 comment by @LeaVerou)
-
w3ctag/w3ctagbot
-
2 pull requests received 2 new comments.
-
w3ctag/w3ctagbot#7 (1 comment by @jyasskin)
-
w3ctag/w3ctagbot#1 (1 comment by @jyasskin)
-
w3ctag/design-principles
-
2 issues opened.
-
New principle: only extend problematic and non-consensus features if the extension acts to fix the problems w3ctag/design-principles#514, by @jyasskin.
-
Principle against overfitting w3ctag/design-principles#513, by @LeaVerou.
-
-
1 issue received 2 new comments.
-
New Principle: Use `[Exposed=*]` to make only purely computational APIs available w3ctag/design-principles#509 (2 comments by @ptomato)
-
-
2 pull requests opened.
-
Remove extensible web text w3ctag/design-principles#516, by @martinthomson.
-
Readme and more w3ctag/design-principles#515, by @martinthomson.
-
-
2 pull requests received 6 new comments.
-
New text for guidance on exposing interfaces everywhere w3ctag/design-principles#510 (3 comments by @bakkot, @littledan, @ptomato)
-
New principle: A Promise represents completion or a value, not a callback (#342) w3ctag/design-principles#496 (3 comments by @jan-ivar)
-
w3ctag/privacy-principles
-
1 issue opened.
-
Seeking horizontal review? w3ctag/privacy-principles#452, by @aphillips.
-
-
1 issue closed.
-
Seeking horizontal review? w3ctag/privacy-principles#452.
-
-
2 issues received 3 new comments.
-
2 pull requests opened.
-
Remove the endorsement of exchanging personal data for content. w3ctag/privacy-principles#451, by @jyasskin.
-
Avoid the "ceiling" metaphor for privacy protections. w3ctag/privacy-principles#450, by @jyasskin.
-
-
6 pull requests merged.
-
Remove the endorsement of exchanging personal data for content. w3ctag/privacy-principles#451.
-
Avoid the "ceiling" metaphor for privacy protections. w3ctag/privacy-principles#450.
-
labour -> labor per W3C manual of style US spelling w3ctag/privacy-principles#429.
-
Update OECD, GPC, and EWP references w3ctag/privacy-principles#428.
-
Mention local regulations in de-identified data section. w3ctag/privacy-principles#441.
-
Avoid "true intent" term. w3ctag/privacy-principles#432.
-
-
4 pull requests received 9 new comments.
-
Say users can say whether pieces of information are sensitive. w3ctag/privacy-principles#442 (4 comments by @dmarti, @jyasskin, @pes10k)
-
Remove the endorsement of exchanging personal data for content. w3ctag/privacy-principles#451 (3 comments by @dmarti, @jyasskin, @thegreatfatzby)
-
Add that ancillary APIs aren't _directly_ needed for the user's immediate goals. w3ctag/privacy-principles#444 (1 comment by @torgo)
-
Past meetings
-
15 meetings.
GitHub
w3ctag/design-reviews
-
11 issues opened.
-
CSS :open pseudo-class w3ctag/design-reviews#1010, by @josepharhar.
-
Review for Protected Audiences Bidding and Auction Services API w3ctag/design-reviews#1009, by @brusshamilton.
-
Vision for W3C: request horizontal architectural review and wide TAG review w3ctag/design-reviews#1008, by @tantek.
-
Customizable select element w3ctag/design-reviews#1007, by @josepharhar.
-
EPUB 3.3 Recommendation with Candidate Corrections 2024-10-17 > 2024-12-19 w3ctag/design-reviews#1006, by @iherman.
-
Dispatching Toggle Events for Dialog open/close w3ctag/design-reviews#1005, by @keithamus.
-
Early Design Review: Allowing First-Party SameSite=None Cookies in Sandboxed Contexts w3ctag/design-reviews#1004, by @aamuley.
-
CSS Masonry Layout w3ctag/design-reviews#1003, by @fantasai.
-
Review for CR transition of WebAssembly specifications for version 2.0 features w3ctag/design-reviews#1002, by @dschuff.
-
CSS view transition auto name generation w3ctag/design-reviews#1001, by @noamr.
-
Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute w3ctag/design-reviews#1000, by @KurtCattiSchmidt.
-
-
11 issues closed.
-
"With Credentials" flag possibly inconsistent with web architecture w3ctag/design-reviews#76.
-
Review for CR transition of WebAssembly specifications for version 2.0 features w3ctag/design-reviews#1002.
-
Multiple import maps w3ctag/design-reviews#980.
-
FYI Private State Token API Permissions Policy Default Allowlist Wildcard w3ctag/design-reviews#990.
-
Early design review: Future browsing context group dependency hint w3ctag/design-reviews#979.
-
A layer attribute for layering of linked CSS style sheets in HTML w3ctag/design-reviews#970.
-
CSS Selectors 4; :local-link w3ctag/design-reviews#998.
-
Realms Initialization Control w3ctag/design-reviews#985.
-
CSS Scoping; :has-slotted w3ctag/design-reviews#999.
-
TAG Review for CSS Values & Units Level 5 w3ctag/design-reviews#993.
-
Vibration API w3ctag/design-reviews#971.
-
-
26 issues received 90 new comments.
-
Reference Target w3ctag/design-reviews#961 (18 comments by @dandclark, @jyasskin, @LeaVerou, @michaelwarren1106, @nolanlawson, @plinss, @Westbrook)
-
Multiple import maps w3ctag/design-reviews#980 (12 comments by @justinfagnani, @jyasskin, @martinthomson, @yoavweiss)
-
Dispatching Toggle Events for Dialog open/close w3ctag/design-reviews#1005 (7 comments by @dandclark, @josepharhar, @jyasskin, @keithamus, @martinthomson)
-
Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute w3ctag/design-reviews#1000 (6 comments by @jyasskin, @martinthomson, @phumai98, @plinss, @Westbrook)
-
Review for CR transition of WebAssembly specifications for version 2.0 features w3ctag/design-reviews#1002 (6 comments by @dschuff, @martinthomson, @torgo)
-
Captured Surface Control w3ctag/design-reviews#962 (5 comments by @eladalon1983, @jyasskin, @matatk)
-
Spec review for Animation.progress w3ctag/design-reviews#994 (4 comments by @DavMila, @jyasskin, @torgo)
-
Early design review: Future browsing context group dependency hint w3ctag/design-reviews#979 (4 comments by @kjmcnee, @martinthomson)
-
FYI Private State Token API Permissions Policy Default Allowlist Wildcard w3ctag/design-reviews#990 (1 comment by @martinthomson)
-
confidence reporting for PerformanceNavigationTiming w3ctag/design-reviews#878 (1 comment by @mwjacksonmsft)
-
A layer attribute for layering of linked CSS style sheets in HTML w3ctag/design-reviews#970 (1 comment by @jyasskin)
-
w3ctag/privacy-principles
-
3 issues opened.
-
Global opt-out discussion is long and not clear about what decision is reaffirmed on each interaction w3ctag/privacy-principles#449, by @jyasskin.
-
Update current PING references to PrivacyWG w3ctag/privacy-principles#447, by @pes10k.
-
De-Identification principal should also apply to api-designers and user agents w3ctag/privacy-principles#445, by @pes10k.
-
-
3 issues closed.
-
De-Identification principal should also apply to api-designers and user agents w3ctag/privacy-principles#445.
-
Update current PING references to PrivacyWG w3ctag/privacy-principles#447.
-
Write (or remove) section on "pay for use in data" w3ctag/privacy-principles#189.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
update some PING references to be PrivacyWG w3ctag/privacy-principles#448, by @pes10k.
-
mark de-identification principal as applying to API designers w3ctag/privacy-principles#446, by @pes10k.
-
Add that ancillary APIs aren't _directly_ needed for the user's immediate goals. w3ctag/privacy-principles#444, by @jyasskin.
-
-
9 pull requests merged.
-
mark de-identification principal as applying to API designers w3ctag/privacy-principles#446.
-
update some PING references to be PrivacyWG w3ctag/privacy-principles#448.
-
Discuss sites that users pay for with data. w3ctag/privacy-principles#436.
-
Remove redundant line w3ctag/privacy-principles#430.
-
Mention tradeoffs inherent in building designed-for-purpose APIs. w3ctag/privacy-principles#440.
-
Say the suggestions for handling new ancillary personal data are examples. w3ctag/privacy-principles#435.
-
Explain an implication of the vulnerability section. w3ctag/privacy-principles#434.
-
Say who should enforcement mechanism. w3ctag/privacy-principles#433.
-
Move the list of principles to the top. w3ctag/privacy-principles#443.
-
-
7 pull requests received 13 new comments.
-
Rename "ancillary" to "supporting" and "non-ancillary" to "essential." w3ctag/privacy-principles#438 (3 comments by @chrisn, @jyasskin)
-
Mention local regulations in de-identified data section. w3ctag/privacy-principles#441 (3 comments by @jyasskin, @wseltzer)
-
Explain how a "3 visits free" model can be compatible with the identity principle. w3ctag/privacy-principles#437 (1 comment by @jyasskin)
-
w3ctag/design-principles
-
1 issue opened.
-
New principle: Guidance on HTTP Headers w3ctag/design-principles#512, by @johannhof.
-
-
2 issues received 15 new comments.
-
New Principle: Use `[Exposed=*]` to make only purely computational APIs available w3ctag/design-principles#509 (13 comments by @annevk, @bakkot, @padenot, @ptomato)
-
New principle: Guidance on HTTP Headers w3ctag/design-principles#512 (2 comments by @annevk, @ylafon)
-
-
2 pull requests received 14 new comments.
-
New principle: A Promise represents completion or a value, not a callback (#342) w3ctag/design-principles#496 (11 comments by @jan-ivar, @jyasskin, @martinthomson)
-
New text for guidance on exposing interfaces everywhere w3ctag/design-principles#510 (3 comments by @bakkot, @ptomato)
-
w3ctag/ethical-web-principles
-
1 issue received 11 new comments.
-
Principle: Individual Digital Sovereignty w3ctag/ethical-web-principles#137 (11 comments by @csarven, @darobin, @lknik, @martinthomson, @mediaprophet, @timbl)
-
w3ctag/tag.w3.org
-
2 pull requests merged.
-
added some references to appointements w3ctag/tag.w3.org#47.
-
appointed by the Team, no longer Tim w3ctag/tag.w3.org#53.
-
Past meetings
GitHub
w3ctag/design-principles
-
1 issue opened.
-
New principle: balancing privacy and other concerns w3ctag/design-principles#511, by @martinthomson.
-
-
5 issues received 10 new comments.
-
New Principle: Use `[Exposed=*]` to make only purely computational APIs available w3ctag/design-principles#509 (5 comments by @annevk, @mgaudet, @ptomato, @zcorpan)
-
New principle: name things for what they do, not how they do it w3ctag/design-principles#507 (2 comments by @domenic, @martinthomson)
-
New principle: balancing privacy and other concerns w3ctag/design-principles#511 (1 comment by @annevk)
-
Several core architectural features of the Web Platform may allow heuristic detectability of assistive technology w3ctag/design-principles#293 (1 comment by @cookiecrook)
-
New principle: Avoid adding (non-constructor) functions to the global scope w3ctag/design-principles#426 (1 comment by @tabatkins)
-
-
1 pull request opened.
-
New text for guidance on exposing interfaces everywhere w3ctag/design-principles#510, by @ptomato.
-
-
2 pull requests received 4 new comments.
-
New text for guidance on exposing interfaces everywhere w3ctag/design-principles#510 (3 comments by @caridy, @jyasskin)
-
New principle: A Promise represents completion or a value, not a callback (#342) w3ctag/design-principles#496 (1 comment by @jan-ivar)
-
w3ctag/design-reviews
-
11 issues opened.
-
CSS Scoping; :has-slotted w3ctag/design-reviews#999, by @keithamus.
-
CSS Selectors 4; :local-link w3ctag/design-reviews#998, by @keithamus.
-
[HTML] Canvas place element w3ctag/design-reviews#997, by @khushalsagar.
-
Web Authentication's PublicKeyCredential signal methods w3ctag/design-reviews#996, by @nsatragno.
-
Document-Isolation-Policy w3ctag/design-reviews#995, by @camillelamy.
-
Spec review for Animation.progress w3ctag/design-reviews#994, by @DavMila.
-
TAG Review for CSS Values & Units Level 5 w3ctag/design-reviews#993, by @fantasai.
-
FedCM as a trust signal for the Storage Access API w3ctag/design-reviews#992, by @johannhof.
-
Writing Assistance APIs w3ctag/design-reviews#991, by @domenic.
-
FYI Private State Token API Permissions Policy Default Allowlist Wildcard w3ctag/design-reviews#990, by @arichiv.
-
Entering IPv6 Zone Identifiers in User Interfaces w3ctag/design-reviews#989, by @martinthomson.
-
-
15 issues closed.
-
DOM state-preserving move w3ctag/design-reviews#976.
-
Call stacks in crash reports from unresponsive web pages w3ctag/design-reviews#981.
-
WebXR Device API (delta/aiming 2nd CRS) w3ctag/design-reviews#983.
-
Add Skip-Ad media session action w3ctag/design-reviews#957.
-
COOP: restrict-properties early review w3ctag/design-reviews#760.
-
Entering IPv6 Zone Identifiers in User Interfaces w3ctag/design-reviews#989.
-
Early Design Review: Lightweight FedCM w3ctag/design-reviews#986.
-
Early TAG review request for Playout Statistics API for WebAudio w3ctag/design-reviews#939.
-
Entry and Exit Animations w3ctag/design-reviews#829.
-
Conversion to RGB in VideoFrame.copyTo() w3ctag/design-reviews#951.
-
Design Review: Prioritized Task Scheduling (big picture) w3ctag/design-reviews#967.
-
Speculation rules: target_hint field w3ctag/design-reviews#931.
-
text-wrap: pretty w3ctag/design-reviews#864.
-
Spec review for scheduler.yield() w3ctag/design-reviews#966.
-
Support Video Chapter in MediaMetadata w3ctag/design-reviews#952.
-
-
32 issues received 62 new comments.
-
Entering IPv6 Zone Identifiers in User Interfaces w3ctag/design-reviews#989 (7 comments by @becarpenter, @jyasskin, @michaelrsweet)
-
Add Skip-Ad media session action w3ctag/design-reviews#957 (5 comments by @chrisn, @martinthomson, @matatk, @miketaylr)
-
Early Design Review: Lightweight FedCM w3ctag/design-reviews#986 (5 comments by @bvandersloot-mozilla, @johannhof, @jyasskin, @rhiaro, @samuelgoto)
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (5 comments by @dmurph, @LuHuangMSFT, @martinthomson)
-
Speculation rules: target_hint field w3ctag/design-reviews#931 (3 comments by @jeremyroman, @jyasskin)
-
COOP: restrict-properties early review w3ctag/design-reviews#760 (2 comments by @camillelamy, @jyasskin)
-
Fenced frames with local unpartitioned data access w3ctag/design-reviews#975 (2 comments by @shivanigithub)
-
Call stacks in crash reports from unresponsive web pages w3ctag/design-reviews#981 (1 comment by @jyasskin)
-
Early TAG review request for Playout Statistics API for WebAudio w3ctag/design-reviews#939 (1 comment by @matatk)
-
FYI Private State Token API Permissions Policy Default Allowlist Wildcard w3ctag/design-reviews#990 (1 comment by @jyasskin)
-
Design Review: Prioritized Task Scheduling (big picture) w3ctag/design-reviews#967 (1 comment by @martinthomson)
-
Adding support for High Dynamic Range (HDR) imagery to HTML Canvas w3ctag/design-reviews#917 (1 comment by @jyasskin)
-
-
1 pull request opened.
-
Refinements to early design review w3ctag/design-reviews#988, by @martinthomson.
-
-
2 pull requests merged.
-
Refinements to early design review w3ctag/design-reviews#988.
-
Mirror design reviews to a private discussion repository w3ctag/design-reviews#987.
-
-
2 pull requests received 9 new comments.
-
Refinements to early design review w3ctag/design-reviews#988 (8 comments by @jyasskin, @martinthomson)
-
Mirror design reviews to a private discussion repository w3ctag/design-reviews#987 (1 comment by @jyasskin)
-
w3ctag/privacy-principles
-
1 issue opened.
-
Address the longer Formal Objection w3ctag/privacy-principles#431, by @jyasskin.
-
-
14 pull requests opened.
-
Move the list of principles to the top. w3ctag/privacy-principles#443, by @jyasskin.
-
Say users can say whether pieces of information are sensitive. w3ctag/privacy-principles#442, by @jyasskin.
-
Mention local regulations in de-identified data section. w3ctag/privacy-principles#441, by @jyasskin.
-
Mention tradeoffs inherent in building designed-for-purpose APIs. w3ctag/privacy-principles#440, by @jyasskin.
-
Add payment as an example ancillary API. w3ctag/privacy-principles#439, by @jyasskin.
-
Rename "ancillary" to "supporting" and "non-ancillary" to "essential." w3ctag/privacy-principles#438, by @jyasskin.
-
Explain how a "3 visits free" model can be compatible with the identity principle. w3ctag/privacy-principles#437, by @jyasskin.
-
Discuss sites that users pay for with data. w3ctag/privacy-principles#436, by @jyasskin.
-
Say the suggestions for handling new ancillary personal data are examples. w3ctag/privacy-principles#435, by @jyasskin.
-
Explain an implication of the vulnerability section. w3ctag/privacy-principles#434, by @jyasskin.
-
Say who should enforcement mechanism. w3ctag/privacy-principles#433, by @jyasskin.
-
Avoid "true intent" term. w3ctag/privacy-principles#432, by @jyasskin.
-
Remove redundant line w3ctag/privacy-principles#430, by @mmocny.
-
labour -> labor per W3C manual of style US spelling w3ctag/privacy-principles#429, by @tantek.
-
-
3 pull requests received 3 new comments.
-
Say users can say whether pieces of information are sensitive. w3ctag/privacy-principles#442 (1 comment by @martinthomson)
-
Discuss sites that users pay for with data. w3ctag/privacy-principles#436 (1 comment by @martinthomson)
-
labour -> labor per W3C manual of style US spelling w3ctag/privacy-principles#429 (1 comment by @jyasskin)
-
w3ctag/ethical-web-principles
-
2 issues opened.
-
Principle: Individual Digital Sovereignty w3ctag/ethical-web-principles#137, by @timbl.
-
Oxford comma w3ctag/ethical-web-principles#132, by @martinthomson.
-
-
1 issue received 1 new comment.
-
4 pull requests opened.
-
Fix some commas w3ctag/ethical-web-principles#136, by @martinthomson.
-
Address [objectors'] Proposal w3ctag/ethical-web-principles#135, by @torgo.
-
correct people's possessive w3ctag/ethical-web-principles#134, by @tantek.
-
fix CEPC ref to Code of Conduct w3ctag/ethical-web-principles#133, by @tantek.
-
-
2 pull requests merged.
-
correct people's possessive w3ctag/ethical-web-principles#134.
-
fix CEPC ref to Code of Conduct w3ctag/ethical-web-principles#133.
-
-
3 pull requests received 6 new comments.
-
Address [objectors'] Proposal w3ctag/ethical-web-principles#135 (4 comments by @jyasskin, @martinthomson, @torgo, @ylafon)
-
An alternative framing for the harms section w3ctag/ethical-web-principles#126 (1 comment by @martinthomson)
-
w3ctag/gaps
-
4 issues opened.
-
Link Previews w3ctag/gaps#8, by @jyasskin.
-
Align color across the platform w3ctag/gaps#7, by @jyasskin.
-
User-consented bug reports w3ctag/gaps#6, by @jyasskin.
-
Privately-aggregated reports of user problems w3ctag/gaps#5, by @jyasskin.
-
-
1 issue received 2 new comments.
w3ctag/tag.w3.org
-
1 issue opened.
-
Focus: pending/complete w3ctag/tag.w3.org#52, by @martinthomson.
-
-
1 pull request opened.
-
appointed by the Team, no longer Tim w3ctag/tag.w3.org#53, by @tantek.
-
-
1 pull request merged.
-
Ask people to list non-consensus dependencies in their explainers. w3ctag/tag.w3.org#40.
-
-
1 pull request received 2 new comments.
-
Work mode: update to reflect github labels, and progress tracking w3ctag/tag.w3.org#49 (2 comments by @hober, @jyasskin)
-
w3ctag/meetings
-
1 issue opened.
-
This person have hacking me in 3 month w3ctag/meetings#52, by @Avsky1.
-
-
1 issue closed.
-
This person have hacking me in 3 month w3ctag/meetings#52.
-
-
1 pull request closed.
-
Discuss Controllers between California & Australia. w3ctag/meetings#51.
-
-
1 pull request received 1 new comment.
w3ctag/explainer-explainer
-
1 issue received 2 new comments.
-
Explainer explainer should explain how to describe Accessibility, Internationalization, Privacy, and Security Considerations w3ctag/explainer-explainer#17 (2 comments by @jyasskin, @martinthomson)
-
TR publications
-
2 documents published.
-
Ethical Web Principles published as a Note. History of Ethical Web Principles
-
Privacy Principles published as a Note. History of Privacy Principles
-
GitHub
w3ctag/design-reviews
-
6 issues opened.
-
Early Design Review: Lightweight FedCM w3ctag/design-reviews#986, by @bvandersloot-mozilla.
-
Realms Initialization Control w3ctag/design-reviews#985, by @weizman.
-
WebXR Device API (delta/aiming 2nd CRS) w3ctag/design-reviews#983, by @himorin.
-
Early design review: Storage Access Headers w3ctag/design-reviews#982, by @cfredric.
-
Call stacks in crash reports from unresponsive web pages w3ctag/design-reviews#981, by @issackjohn.
-
Multiple import maps w3ctag/design-reviews#980, by @yoavweiss.
-
-
11 issues closed.
-
Requesting review of HTML Ruby Markup Extensions w3ctag/design-reviews#959.
-
Early design review: Storage Access Headers w3ctag/design-reviews#982.
-
WebAssembly JavaScript Promise Integration API w3ctag/design-reviews#809.
-
Web Install API - Same Origin w3ctag/design-reviews#888.
-
Specification review for CSS Anchor Positioning w3ctag/design-reviews#848.
-
Private Aggregation API w3ctag/design-reviews#846.
-
JS String Builtins for WebAssembly w3ctag/design-reviews#940.
-
Spec review for Snap Events w3ctag/design-reviews#943.
-
View Transitions: list of types w3ctag/design-reviews#908.
-
Web Translation API w3ctag/design-reviews#948.
-
26 issues received 63 new comments.
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (8 comments by @dmurph, @LuHuangMSFT, @martinthomson, @torgo)
-
Early Design Review: Lightweight FedCM w3ctag/design-reviews#986 (4 comments by @bvandersloot-mozilla, @johannhof, @jyasskin, @samuelgoto)
-
Speculation rules: target_hint field w3ctag/design-reviews#931 (3 comments by @domenic, @nhiroki, @plinss)
-
Before 6 August 2023 -- Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) - Google Chrome - Daniel (w3.org) w3ctag/design-reviews#973 (2 comments by @daniel-montalvo, @matatk)
-
Early TAG review request for Playout Statistics API for WebAudio w3ctag/design-reviews#939 (1 comment by @Hernqvist)
-
1 pull request opened.
-
Mirror design reviews to a private discussion repository w3ctag/design-reviews#987, by @jyasskin.
-
-
1 pull request received 1 new comment.
-
Mirror design reviews to a private discussion repository w3ctag/design-reviews#987 (1 comment by @LeaVerou)
-
w3ctag/privacy-principles
-
1 pull request opened.
-
Update OECD, GPC, and EWP references w3ctag/privacy-principles#428, by @plehegar.
-
-
1 pull request received 1 new comment.
w3ctag/gaps
-
1 issue opened.
w3ctag/meetings
-
1 pull request opened.
-
Discuss Controllers between California & Australia. w3ctag/meetings#51, by @jyasskin.
-
w3ctag/design-principles
-
1 issue opened.
-
New Principle: Use `[Exposed=*]` to make only purely computational APIs available w3ctag/design-principles#509, by @ptomato.
-
-
1 issue received 1 new comment.
-
New principle: How to attach meta-information to a document w3ctag/design-principles#506 (1 comment by @annevk)
-
-
1 pull request opened.
-
Fix typos. w3ctag/design-principles#508, by @jan-ivar.
-
-
4 pull requests received 21 new comments.
-
Text formats are for people w3ctag/design-principles#505 (14 comments by @hober, @LeaVerou, @martinthomson)
-
Guidance about reflecting state in HTML attributes w3ctag/design-principles#501 (3 comments by @annevk, @martinthomson)
-
w3ctag/ethical-web-principles
-
1 issue received 6 new comments.
-
Principle: The Web should not owned by anyone w3ctag/ethical-web-principles#120 (6 comments by @diekus, @martinthomson, @mwbender, @Schepp, @slightlyoff, @torgo)
-
w3ctag/web-without-3p-cookies
-
3 issues opened.
-
Addressing issue: calling out use cases w3ctag/web-without-3p-cookies#30, by @torgo.
-
Addressing issue: consider mitigating high-entropy API use w3ctag/web-without-3p-cookies#29, by @torgo.
-
Addressing issue: encourage browser vendors to adopt APIs that facilitate a smoother transition w3ctag/web-without-3p-cookies#28, by @torgo.
-
-
1 pull request received 1 new comment.
w3ctag/tag.w3.org
-
1 pull request opened.
-
Update history for latest members and fix a few errors. w3ctag/tag.w3.org#51, by @dbaron.
-
-
1 pull request merged.
-
Update history for latest members and fix a few errors. w3ctag/tag.w3.org#51.
-
TR publications
-
3 documents published.
-
Web Platform Design Principles published as a Note. History of Web Platform Design Principles
-
Ethical Web Principles published as a Draft Note. History of Ethical Web Principles
-
Privacy Principles published as a Draft Note. History of Privacy Principles
-
Participants
-
2 participants joined.
-
Jeffrey Yasskin joined.
-
Tristan Nitot joined.
-
GitHub
w3ctag/design-reviews
-
8 issues opened.
-
Early design review: Future browsing context group dependency hint w3ctag/design-reviews#979, by @kjmcnee.
-
CSS reading-flow property w3ctag/design-reviews#978, by @dizhang168.
-
Accessibility conformance Testing (ACT) Rules Format 1.1 w3ctag/design-reviews#977, by @daniel-montalvo.
-
DOM state-preserving move w3ctag/design-reviews#976, by @noamr.
-
Fenced frames with local unpartitioned data access w3ctag/design-reviews#975, by @shivanigithub.
-
FedCM's IdP Registration API w3ctag/design-reviews#974, by @samuelgoto.
-
D w3ctag/design-reviews#972, by @Btaxxpress.
-
-
6 issues closed.
-
`noopener-allow-popups` value in COOP w3ctag/design-reviews#964.
-
Timing Info for ServiceWorker static routing API w3ctag/design-reviews#958.
-
Incremental Font Transfer: Patch Subset w3ctag/design-reviews#849.
-
Review Request for Attribution Reporting API w3ctag/design-reviews#724.
-
D w3ctag/design-reviews#972.
-
Early review for adding a new value to the standard list of `name`s for a meta tag w3ctag/design-reviews#819.
-
-
20 issues received 51 new comments.
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (10 comments by @dmurph, @LuHuangMSFT, @martinthomson, @reillyeon)
-
Web Translation API w3ctag/design-reviews#948 (9 comments by @domenic, @jasonmayes, @LeaVerou, @martinthomson, @matatk, @plinss)
-
Specification review for fenced frames w3ctag/design-reviews#838 (5 comments by @domfarolino, @martinthomson, @shivanigithub, @torgo, @yoavweiss)
-
CSS calc-size() function w3ctag/design-reviews#955 (5 comments by @dbaron, @LeaVerou, @plinss, @tabatkins)
-
Timing Info for ServiceWorker static routing API w3ctag/design-reviews#958 (2 comments by @martinthomson, @quasi-mod)
-
FedCM bundle: Continuation API, account labels, custom parameters, scopes w3ctag/design-reviews#945 (2 comments by @cbiesinger, @samuelgoto)
-
Early TAG review request for Playout Statistics API for WebAudio w3ctag/design-reviews#939 (2 comments by @martinthomson, @matatk)
-
Web Audio API: RenderCapacity API w3ctag/design-reviews#843 (2 comments by @martinthomson, @padenot)
-
MediaStreamTrack Insertable Media Processing using Streams w3ctag/design-reviews#603 (1 comment by @jan-ivar)
-
FedCM API extension: Button Mode and User Other Account API w3ctag/design-reviews#935 (1 comment by @samuelgoto)
-
Early review for adding a new value to the standard list of `name`s for a meta tag w3ctag/design-reviews#819 (1 comment by @slightlyoff)
-
Constructors for RTC encoded frames with custom metadata w3ctag/design-reviews#942 (1 comment by @martinthomson)
-
w3ctag/web-without-3p-cookies
-
2 issues opened.
-
Link previous finding / limits w3ctag/web-without-3p-cookies#27, by @bkardell.
-
This finding needs and update w3ctag/web-without-3p-cookies#21, by @torgo.
-
-
2 issues closed.
-
Link previous finding / limits w3ctag/web-without-3p-cookies#27.
-
This finding needs and update w3ctag/web-without-3p-cookies#21.
-
-
2 issues received 2 new comments.
-
5 pull requests opened.
-
Concentrate on use cases w3ctag/web-without-3p-cookies#26, by @martinthomson.
-
Stop using 'deprecated' w3ctag/web-without-3p-cookies#25, by @martinthomson.
-
QA changes w3ctag/web-without-3p-cookies#24, by @koalie.
-
QA changes w3ctag/web-without-3p-cookies#23, by @koalie.
-
Update finding w3ctag/web-without-3p-cookies#22, by @torgo.
-
-
3 pull requests merged.
-
Stop using 'deprecated' w3ctag/web-without-3p-cookies#25.
-
QA changes w3ctag/web-without-3p-cookies#24.
-
Update finding w3ctag/web-without-3p-cookies#22.
-
-
1 pull request closed.
-
QA changes w3ctag/web-without-3p-cookies#23.
-
-
4 pull requests received 38 new comments.
-
Update finding w3ctag/web-without-3p-cookies#22 (34 comments by @hadleybeeman, @hober, @jyasskin, @martinthomson, @plinss, @rhiaro, @torgo)
-
w3ctag/design-principles
-
5 issues opened.
-
New principle: name things for what they do, not how they do it w3ctag/design-principles#507, by @martinthomson.
-
New principle: How to attach meta-information to a document w3ctag/design-principles#506, by @martinthomson.
-
CSS Principle: Document not using boolean values for properties w3ctag/design-principles#503, by @plinss.
-
naming-common-words in English w3ctag/design-principles#499, by @csarven.
-
Assistive technology emphasis adjustments w3ctag/design-principles#498, by @nigelmegitt.
-
-
1 issue closed.
-
naming-common-words in English w3ctag/design-principles#499.
-
-
10 issues received 23 new comments.
-
naming-common-words in English w3ctag/design-principles#499 (11 comments by @annevk, @csarven, @cynthia, @LeaVerou, @riannella)
-
New principle: name things for what they do, not how they do it w3ctag/design-principles#507 (2 comments by @hober, @LeaVerou)
-
Examples for "overloading" principle w3ctag/design-principles#431 (2 comments by @LeaVerou, @martinthomson)
-
Feedback on "11.1. Use common words" w3ctag/design-principles#261 (2 comments by @csarven, @cynthia)
-
New principle: How to attach meta-information to a document w3ctag/design-principles#506 (1 comment by @hober)
-
New principle: The value of HTML boolean attributes doesn't matter w3ctag/design-principles#451 (1 comment by @LeaVerou)
-
New principle: Discourage overloading (in HTML) w3ctag/design-principles#370 (1 comment by @martinthomson)
-
New principle: Document whether to add things to Document, Navigator, Window, or SomeOtherInterface w3ctag/design-principles#448 (1 comment by @domenic)
-
New principle: Do not design around third-party tools unless it actually breaks the Web w3ctag/design-principles#335 (1 comment by @carlosmintfan)
-
-
5 pull requests opened.
-
Text formats are for people w3ctag/design-principles#505, by @martinthomson.
-
Prefer composition w3ctag/design-principles#504, by @martinthomson.
-
Establish a rule about element overloading w3ctag/design-principles#502, by @martinthomson.
-
Guidance about reflecting state in HTML attributes w3ctag/design-principles#501, by @LeaVerou.
-
New principle: Return undefined from side-effect-causing functions. w3ctag/design-principles#500, by @hober.
-
-
7 pull requests received 48 new comments.
-
Guidance about reflecting state in HTML attributes w3ctag/design-principles#501 (15 comments by @annevk, @hober, @LeaVerou)
-
Establish a rule about element overloading w3ctag/design-principles#502 (11 comments by @annevk, @hober, @LeaVerou)
-
Text formats are for people w3ctag/design-principles#505 (10 comments by @hober, @LeaVerou, @plinss)
-
New principle: A Promise represents completion or a value, not a callback (#342) w3ctag/design-principles#496 (8 comments by @alvestrand, @jan-ivar, @jyasskin, @LeaVerou)
-
New principle: Return undefined from side-effect-causing functions. w3ctag/design-principles#500 (1 comment by @domenic)
-
w3ctag/ethical-web-principles
-
1 issue opened.
-
New principal: help businesses and individuals succeed through automation of base principals w3ctag/ethical-web-principles#128, by @WW3.
-
-
1 issue closed.
-
Align language in section titles w3ctag/ethical-web-principles#121.
-
-
4 issues received 4 new comments.
-
Document should discourage features that'd lead to a more centralized web w3ctag/ethical-web-principles#94 (1 comment by @pes10k)
-
Principle: The Web should not owned by anyone w3ctag/ethical-web-principles#120 (1 comment by @almereyda)
-
-
2 pull requests opened.
-
The web... w3ctag/ethical-web-principles#130, by @martinthomson.
-
autoplaying videos is just content w3ctag/ethical-web-principles#129, by @martinthomson.
-
-
2 pull requests merged.
-
The web... w3ctag/ethical-web-principles#130.
-
autoplaying videos is just content w3ctag/ethical-web-principles#129.
-
-
1 pull request closed.
-
Adjust phrasing of principles w3ctag/ethical-web-principles#124.
-
-
2 pull requests received 2 new comments.
-
An alternative framing for the harms section w3ctag/ethical-web-principles#126 (1 comment by @martinthomson)
-
w3ctag/process
-
1 issue opened.
-
High-level web platform vision and improving the TAG’s Impact/Effort ratio w3ctag/process#36, by @LeaVerou.
-
-
2 issues received 3 new comments.
-
High-level web platform vision and improving the TAG’s Impact/Effort ratio w3ctag/process#36 (2 comments by @adrianhopebailie, @LeaVerou)
-
w3ctag/tag.w3.org
-
1 issue opened.
-
done w3ctag/tag.w3.org#50, by @VivekMangukiya11.
-
-
1 issue closed.
-
done w3ctag/tag.w3.org#50.
-
w3ctag/gaps
-
2 issues opened.
-
IDREF attributes are fragile and painful to use w3ctag/gaps#2, by @LeaVerou.
-
SVG images should be able to utilize local resources w3ctag/gaps#1, by @LeaVerou.
-
w3ctag/tracking-issues
-
1 issue opened.
-
[wg/aria] [Accessible Rich Internet Applications] Group Charter w3ctag/tracking-issues#82, by @w3cbot.
-
w3ctag/privacy-principles
-
1 issue closed.
-
Data portability threat model, mitigations w3ctag/privacy-principles#424.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Make all citations Camel-Case, and alphabetize them. w3ctag/privacy-principles#427, by @jyasskin.
-
Link to DTI's data portability threat model. w3ctag/privacy-principles#426, by @jyasskin.
-
-
1 pull request merged.
-
Link to DTI's data portability threat model. w3ctag/privacy-principles#426.
-
-
1 pull request received 2 new comments.
-
Link to DTI's data portability threat model. w3ctag/privacy-principles#426 (2 comments by @lisad, @torgo)
-
TR publications
-
1 document published.
-
Ethical Web Principles published as a Draft Note. History of Ethical Web Principles
-
GitHub
w3ctag/design-reviews
-
11 issues opened.
-
Vibration API w3ctag/design-reviews#971, by @anssiko.
-
A layer attribute for layering of linked CSS style sheets in HTML w3ctag/design-reviews#970, by @mirisuzanne.
-
Compression Dictionary Transport: Align on a single Content-Encoding for the web? w3ctag/design-reviews#969, by @pmeenan.
-
Design Review: Prioritized Task Scheduling (big picture) w3ctag/design-reviews#967, by @shaseley.
-
Spec review for scheduler.yield() w3ctag/design-reviews#966, by @shaseley.
-
improvements to <details> styling (widget structure) w3ctag/design-reviews#965, by @dbaron.
-
`noopener-allow-popups` value in COOP w3ctag/design-reviews#964, by @yoavweiss.
-
ServiceWorkerAutoPreload w3ctag/design-reviews#963, by @sisidovski.
-
Captured Surface Control w3ctag/design-reviews#962, by @eladalon1983.
-
Reference Target w3ctag/design-reviews#961, by @dandclark.
-
Controller Documents v1.0 w3ctag/design-reviews#960, by @msporny.
-
-
10 issues closed.
-
Updated review of WebNN API w3ctag/design-reviews#933.
-
document.caretPositionFromPoint API in shadow DOM scenario w3ctag/design-reviews#949.
-
Wide review request for Pointer Events Level 3 w3ctag/design-reviews#941.
-
ServiceWorkerAutoPreload w3ctag/design-reviews#963.
-
Compression Dictionary Transport: Align on a single Content-Encoding for the web? w3ctag/design-reviews#969.
-
improvements to <details> styling (widget structure) w3ctag/design-reviews#965.
-
Long Animation Frame API (LoAF) w3ctag/design-reviews#911.
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798.
-
Captured Mouse Events w3ctag/design-reviews#872.
-
Early Design Review: Opener Protections w3ctag/design-reviews#916.
-
-
27 issues received 61 new comments.
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (4 comments by @diekus, @dmurph, @LuHuangMSFT, @martinthomson)
-
CSS calc-size() function w3ctag/design-reviews#955 (4 comments by @dbaron, @LeaVerou, @martinthomson, @tabatkins)
-
Timing Info for ServiceWorker static routing API w3ctag/design-reviews#958 (3 comments by @quasi-mod, @torgo)
-
document.caretPositionFromPoint API in shadow DOM scenario w3ctag/design-reviews#949 (3 comments by @LeaVerou, @siliu1)
-
Adding support for High Dynamic Range (HDR) imagery to HTML Canvas w3ctag/design-reviews#917 (3 comments by @palemieux)
-
Compression Dictionary Transport: Align on a single Content-Encoding for the web? w3ctag/design-reviews#969 (3 comments by @plinss, @pmeenan)
-
improvements to <details> styling (widget structure) w3ctag/design-reviews#965 (3 comments by @dbaron, @LeaVerou, @martinthomson)
-
Early review for adding a new value to the standard list of `name`s for a meta tag w3ctag/design-reviews#819 (2 comments by @LeaVerou, @martinthomson)
-
Wide review request for Pointer Events Level 3 w3ctag/design-reviews#941 (2 comments by @patrickhlauke, @torgo)
-
Specification review for CSS Anchor Positioning w3ctag/design-reviews#848 (2 comments by @mfreed7, @torgo)
-
`noopener-allow-popups` value in COOP w3ctag/design-reviews#964 (2 comments by @martinthomson, @yoavweiss)
-
Early TAG review request for Playout Statistics API for WebAudio w3ctag/design-reviews#939 (1 comment by @matatk)
-
FedCM bundle: Continuation API, account labels, custom parameters, scopes w3ctag/design-reviews#945 (1 comment by @torgo)
-
1 pull request opened.
-
Fix a typo w3ctag/design-reviews#968, by @aphillips.
-
-
1 pull request merged.
-
Fix a typo w3ctag/design-reviews#968.
-
-
1 pull request received 1 new comment.
w3ctag/tracking-issues
-
2 issues opened.
-
URI in Profile triggers CORS Unsafe Request Header Byte rule w3ctag/tracking-issues#81, by @w3cbot.
-
[wg/rdf-star] RDF-star Group Charter w3ctag/tracking-issues#80, by @w3cbot.
-
w3ctag/design-principles
-
2 issues opened.
-
New principle: Prefer reusing existing syntax even with validity constraints to introducing new syntax w3ctag/design-principles#497, by @LeaVerou.
-
"HTML attribute" as a term w3ctag/design-principles#495, by @martinthomson.
-
-
5 issues closed.
-
New principle: Deployability and Monitoring w3ctag/design-principles#368.
-
Use of "attribute" confusing/ambiguous w3ctag/design-principles#457.
-
New: Avoid revealing that consent was denied w3ctag/design-principles#475.
-
Second consistency pass for attributes/properties/methods/functions etc. w3ctag/design-principles#315.
-
Newlines in source cause broken links w3ctag/design-principles#491.
-
-
12 issues received 16 new comments.
-
New principle: Prefer reusing existing syntax even with validity constraints to introducing new syntax w3ctag/design-principles#497 (2 comments by @dbaron, @tabatkins)
-
New principle: The value of HTML boolean attributes doesn't matter w3ctag/design-principles#451 (2 comments by @hober, @plinss)
-
New principle: Support common promise practices w3ctag/design-principles#342 (2 comments by @jan-ivar, @martinthomson)
-
Guidance for when to use inheritance vs composition w3ctag/design-principles#298 (2 comments by @LeaVerou, @martinthomson)
-
New principle: Consider many & diverse use cases to avoid overfitting w3ctag/design-principles#450 (1 comment by @LeaVerou)
-
New principle: Remove deprecated functionality responsibly w3ctag/design-principles#361 (1 comment by @torgo)
-
HTML: Receive complex data via JS or element subtrees? w3ctag/design-principles#348 (1 comment by @LeaVerou)
-
[Meta] Tackling design problems earlier than design review / A Q&A section for API design w3ctag/design-principles#319 (1 comment by @martinthomson)
-
Terminology jumps away from principle's subject ("Use care when exposing identifying information about devices") w3ctag/design-principles#479 (1 comment by @matatk)
-
-
1 pull request opened.
-
New principle: A Promise represents completion or a value, not a callback (#342) w3ctag/design-principles#496, by @jan-ivar.
-
-
4 pull requests merged.
-
fix duplicative text in new-features w3ctag/design-principles#494.
-
It looks like this text was duplicated w3ctag/design-principles#477.
-
Attempt to split attribute by type w3ctag/design-principles#485.
-
Denying consent is better if undetectable as such w3ctag/design-principles#476.
-
-
4 pull requests received 20 new comments.
-
New principle: A Promise represents completion or a value, not a callback (#342) w3ctag/design-principles#496 (12 comments by @alvestrand, @jan-ivar, @martinthomson)
-
Denying consent is better if undetectable as such w3ctag/design-principles#476 (2 comments by @rhiaro)
-
w3ctag/ethical-web-principles
-
2 issues closed.
-
Participating in the Open Web with the Expectation You Won't Be Part of Data Harvests w3ctag/ethical-web-principles#109.
-
Should we talk about interoperability vs "evolution-ability" as a tension / design goal for the web? w3ctag/ethical-web-principles#61.
-
-
4 issues received 18 new comments.
-
Align language in section titles w3ctag/ethical-web-principles#121 (15 comments by @darobin, @mnot, @rhiaro, @torgo)
-
Participating in the Open Web with the Expectation You Won't Be Part of Data Harvests w3ctag/ethical-web-principles#109 (1 comment by @torgo)
-
Consider the relationship between rights and responsibilities w3ctag/ethical-web-principles#71 (1 comment by @torgo)
-
Should we talk about interoperability vs "evolution-ability" as a tension / design goal for the web? w3ctag/ethical-web-principles#61 (1 comment by @torgo)
-
-
5 pull requests opened.
-
An alternative framing for the harms section w3ctag/ethical-web-principles#126, by @martinthomson.
-
Remove trailing whitespace w3ctag/ethical-web-principles#125, by @martinthomson.
-
Adjust phrasing of principles w3ctag/ethical-web-principles#124, by @mnot.
-
Remove as much hedging as I think is possible with minimal tweaks w3ctag/ethical-web-principles#123, by @darobin.
-
Align section title with grammar of others w3ctag/ethical-web-principles#122, by @rhiaro.
-
-
2 pull requests merged.
-
Remove trailing whitespace w3ctag/ethical-web-principles#125.
-
Align section title with grammar of others w3ctag/ethical-web-principles#122.
-
-
3 pull requests received 13 new comments.
-
Remove as much hedging as I think is possible with minimal tweaks w3ctag/ethical-web-principles#123 (7 comments by @cwilso, @darobin, @martinthomson, @mnot)
-
An alternative framing for the harms section w3ctag/ethical-web-principles#126 (4 comments by @hober, @martinthomson)
-
Adjust phrasing of principles w3ctag/ethical-web-principles#124 (2 comments by @martinthomson, @mnot)
-
w3ctag/privacy-principles
-
1 issue opened.
-
Non-retaliation as a design principle w3ctag/privacy-principles#425, by @martinthomson.
-
-
1 issue closed.
-
Non-retaliation as a design principle w3ctag/privacy-principles#425.
-
-
3 issues received 8 new comments.
-
Data portability threat model, mitigations w3ctag/privacy-principles#424 (3 comments by @lisad, @torgo)
-
Non-retaliation as a design principle w3ctag/privacy-principles#425 (3 comments by @hober, @martinthomson, @rhiaro)
-
Add a principle that sites should not be _able_ to retaliate when users say no w3ctag/privacy-principles#418 (2 comments by @hober, @torgo)
-
w3ctag/meetings
-
1 pull request opened.
-
Seattle F2F: also link to the BoD's meeting page. w3ctag/meetings#50, by @hober.
-
-
1 pull request merged.
-
Seattle F2F: also link to the BoD's meeting page. w3ctag/meetings#50.
-
TR publications
-
2 documents published.
-
Ethical Web Principles published as a Draft Note. History of Ethical Web Principles
-
Privacy Principles published as a Draft Note. History of Privacy Principles
-
GitHub
w3ctag/design-reviews
-
8 issues opened.
-
Requesting review of HTML Ruby Markup Extensions w3ctag/design-reviews#959, by @frivoal.
-
Timing Info for ServiceWorker static routing API w3ctag/design-reviews#958, by @quasi-mod.
-
Add Skip-Ad media session action w3ctag/design-reviews#957, by @jiajiabingcheng.
-
Early Design Review: Partitioned Popins w3ctag/design-reviews#956, by @arichiv.
-
CSS calc-size() function w3ctag/design-reviews#955, by @dbaron.
-
Element Capture w3ctag/design-reviews#954, by @eladalon1983.
-
Support Video Chapter in MediaMetadata w3ctag/design-reviews#952, by @jiajiabingcheng.
-
Conversion to RGB in VideoFrame.copyTo() w3ctag/design-reviews#951, by @Djuffin.
-
-
3 issues closed.
-
Web Audio API: Add error reporting via AudioContext.onerror w3ctag/design-reviews#950.
-
Importmap integrity w3ctag/design-reviews#944.
-
early design review: Permissions-Policy: unload w3ctag/design-reviews#738.
-
-
20 issues received 44 new comments.
-
Local Peer-to-Peer API w3ctag/design-reviews#932 (7 comments by @anssiko, @backkem, @matatk, @simoneonofri, @wangw-1991)
-
Specification review for CSS Anchor Positioning w3ctag/design-reviews#848 (6 comments by @fantasai, @LeaVerou, @mfreed7, @plinss, @tabatkins)
-
Support Video Chapter in MediaMetadata w3ctag/design-reviews#952 (3 comments by @hober, @jiajiabingcheng)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (3 comments by @beaufortfrancois, @LeaVerou, @steimelchrome)
-
document.caretPositionFromPoint API in shadow DOM scenario w3ctag/design-reviews#949 (3 comments by @martinthomson, @siliu1, @zcorpan)
-
Web Audio API: Add error reporting via AudioContext.onerror w3ctag/design-reviews#950 (2 comments by @LeaVerou, @martinthomson)
-
Adding support for High Dynamic Range (HDR) imagery to HTML Canvas w3ctag/design-reviews#917 (1 comment by @svgeesus)
-
Permissions Policy Reporting and Report-Only mode w3ctag/design-reviews#909 (1 comment by @clelland)
-
Early TAG review request for Playout Statistics API for WebAudio w3ctag/design-reviews#939 (1 comment by @Hernqvist)
-
-
1 pull request opened.
-
Tidy up; add Focus labels by default w3ctag/design-reviews#953, by @rhiaro.
-
w3ctag/ethical-web-principles
-
2 issues opened.
-
Align language in section titles w3ctag/ethical-web-principles#121, by @mnot.
-
Principle: The Web should not owned by anyone w3ctag/ethical-web-principles#120, by @mnot.
-
-
2 issues closed.
-
Extend I18N/L10N to include support for languages and especially cultures w3ctag/ethical-web-principles#116.
-
A small modification to principle 2.5 w3ctag/ethical-web-principles#112.
-
-
4 issues received 8 new comments.
-
A small modification to principle 2.5 w3ctag/ethical-web-principles#112 (5 comments by @mnot, @rhiaro, @simoneonofri)
-
Extend I18N/L10N to include support for languages and especially cultures w3ctag/ethical-web-principles#116 (1 comment by @torgo)
-
-
2 pull requests opened.
-
2.4 All people: mention languages and cultures, for #116 w3ctag/ethical-web-principles#119, by @rhiaro.
-
2.5 Privacy: talk about mitigating harm w3ctag/ethical-web-principles#118, by @rhiaro.
-
-
3 pull requests merged.
-
2.4 All people: mention languages and cultures, for #116 w3ctag/ethical-web-principles#119.
-
2.5 Privacy: talk about mitigating harm w3ctag/ethical-web-principles#118.
-
grammar review w3ctag/ethical-web-principles#113.
-
-
2 pull requests received 6 new comments.
-
2.4 All people: mention languages and cultures, for #116 w3ctag/ethical-web-principles#119 (3 comments by @aphillips, @rhiaro)
-
2.5 Privacy: talk about mitigating harm w3ctag/ethical-web-principles#118 (3 comments by @martinthomson, @rhiaro)
-
w3ctag/privacy-principles
-
3 issues opened.
-
Data portability threat model, mitigations w3ctag/privacy-principles#424, by @lisad.
-
Consider removing or greatly shortening "1.1.2 Privacy Labour" w3ctag/privacy-principles#422, by @pes10k.
-
Add a principle that sites should not be _able_ to retaliate when users say no w3ctag/privacy-principles#418, by @jyasskin.
-
-
25 issues closed.
-
non-retaliation principle audience should probably also include user agents w3ctag/privacy-principles#396.
-
Improve comprehensibility of section 1.1.2 Privacy labour w3ctag/privacy-principles#331.
-
Discuss privacy-labor in the processing section w3ctag/privacy-principles#273.
-
Remove High-Level threats appendix w3ctag/privacy-principles#341.
-
Revisit 2.4 Sensitive Information section w3ctag/privacy-principles#388.
-
Opt-in vs. Opt-out w3ctag/privacy-principles#405.
-
Make targeted lists of principles for each audience w3ctag/privacy-principles#397.
-
Add labels to Principles Summary w3ctag/privacy-principles#413.
-
Simplify the "processing" definition. w3ctag/privacy-principles#375.
-
"respect data rights" principle should apply to API designers too w3ctag/privacy-principles#362.
-
"should best" and collective privacy w3ctag/privacy-principles#351.
-
Consider removing the definition of "vulnerable people". w3ctag/privacy-principles#373.
-
Editors should make sure we are consistent in marking up examples as such w3ctag/privacy-principles#335.
-
Copy edit Transparency section w3ctag/privacy-principles#360.
-
Copy edit section 2.15, Support Choosing Which Information to Present w3ctag/privacy-principles#316.
-
Copy edit section 2.12, Consent, Withdrawal of Consent, Opt-Outs, and Objections w3ctag/privacy-principles#313.
-
Copy edit section 2.13, Notifications and Interruptions w3ctag/privacy-principles#314.
-
Copy edit section 2.14, Non-Retaliation w3ctag/privacy-principles#315.
-
Copy edit section 1.3, User Agents w3ctag/privacy-principles#300.
-
Copy edit section 1.4, Incorporating Different Privacy Principles w3ctag/privacy-principles#301.
-
Copy edit section 2.6, De-identified Data w3ctag/privacy-principles#307.
-
Copy edit section 1.2, Collective Governance w3ctag/privacy-principles#299.
-
Centralization risks of noise as a mitigation tool w3ctag/privacy-principles#261.
-
Editorial: Regarding partition definition and storage w3ctag/privacy-principles#145.
-
Follow the TAG Style Guide w3ctag/privacy-principles#15.
-
-
11 issues received 13 new comments.
-
Data portability threat model, mitigations w3ctag/privacy-principles#424 (2 comments by @jyasskin, @lisad)
-
non-retaliation principle audience should probably also include user agents w3ctag/privacy-principles#396 (1 comment by @darobin)
-
Make the definition of "identifier" consistent with the list of identifiers w3ctag/privacy-principles#374 (1 comment by @darobin)
-
Consider removing the definition of "vulnerable people". w3ctag/privacy-principles#373 (1 comment by @jyasskin)
-
Discuss privacy-labor in the processing section w3ctag/privacy-principles#273 (1 comment by @darobin)
-
Try using the privacy principles to analyze the Environment Integrity API proposal w3ctag/privacy-principles#271 (1 comment by @darobin)
-
Centralization risks of noise as a mitigation tool w3ctag/privacy-principles#261 (1 comment by @darobin)
-
Editorial: Regarding partition definition and storage w3ctag/privacy-principles#145 (1 comment by @darobin)
-
-
5 pull requests opened.
-
Update 2024-05-08-minutes.md w3ctag/privacy-principles#423, by @torgo.
-
remove high level threats and reference RFC6973 instead w3ctag/privacy-principles#421, by @darobin.
-
All information may be sensitive w3ctag/privacy-principles#420, by @darobin.
-
Include UAs as actors that should not retaliate. w3ctag/privacy-principles#419, by @jyasskin.
-
mention potential tension beyond the EWP w3ctag/privacy-principles#417, by @darobin.
-
-
6 pull requests merged.
-
Update 2024-05-08-minutes.md w3ctag/privacy-principles#423.
-
Include UAs as actors that should not retaliate. w3ctag/privacy-principles#419.
-
remove high level threats and reference RFC6973 instead w3ctag/privacy-principles#421.
-
All information may be sensitive w3ctag/privacy-principles#420.
-
mention potential tension beyond the EWP w3ctag/privacy-principles#417.
-
Add labels to the principles summary w3ctag/privacy-principles#416.
-
-
2 pull requests received 4 new comments.
-
All information may be sensitive w3ctag/privacy-principles#420 (3 comments by @darobin, @jyasskin, @pes10k)
-
remove high level threats and reference RFC6973 instead w3ctag/privacy-principles#421 (1 comment by @darobin)
-
w3ctag/design-principles
-
1 issue opened.
-
New principle: don't break core part of the web platform in order to enable embellishments w3ctag/design-principles#493, by @torgo.
-
-
2 issues received 2 new comments.
-
New principle: APIs which vend byte buffers should return a Uint8Array w3ctag/design-principles#463 (1 comment by @Jamesernator)
-
New principle: don't break core part of the web platform in order to enable embellishments w3ctag/design-principles#493 (1 comment by @torgo)
-
-
1 pull request opened.
-
fix duplicative text in new-features w3ctag/design-principles#494, by @marcoscaceres.
-
-
1 pull request received 1 new comment.
w3ctag/obsoletion
-
3 issues opened.
-
Geolocation Sensor API w3ctag/obsoletion#9, by @marcoscaceres.
-
Gyroscope, Accelerometer, Magnetometer, Orientation, Motion APIs w3ctag/obsoletion#8, by @marcoscaceres.
-
Vibration API (Second Edition) w3ctag/obsoletion#7, by @marcoscaceres.
-
-
3 issues closed.
-
Vibration API (Second Edition) w3ctag/obsoletion#7.
-
Gyroscope, Accelerometer, Magnetometer, Orientation, Motion APIs w3ctag/obsoletion#8.
-
Geolocation Sensor API w3ctag/obsoletion#9.
-
-
3 issues received 12 new comments.
-
Gyroscope, Accelerometer, Magnetometer, Orientation, Motion APIs w3ctag/obsoletion#8 (4 comments by @marcoscaceres, @plehegar)
w3ctag/tracking-issues
-
2 issues opened.
-
[wg/lws] Proposed charter: Linked Web Storage Working Group (ex Solid) w3ctag/tracking-issues#79, by @w3cbot.
-
joint work on rights-respecting digital credentials w3ctag/tracking-issues#78, by @w3cbot.
-
w3ctag/tag.w3.org
-
1 pull request opened.
-
Work mode: update to reflect github labels, and progress tracking w3ctag/tag.w3.org#49, by @rhiaro.
-
Past meetings
GitHub
w3ctag/design-reviews
-
9 issues opened.
-
Web Audio API: Add error reporting via AudioContext.onerror w3ctag/design-reviews#950, by @gsinafirooz.
-
document.caretPositionFromPoint API in shadow DOM scenario w3ctag/design-reviews#949, by @siliu1.
-
Web Translation API w3ctag/design-reviews#948, by @domenic.
-
Early review request for "Explicit JavaScript Compile Hints" w3ctag/design-reviews#947, by @marjakh.
-
Web Install API - Cross-Origin w3ctag/design-reviews#946, by @plinss.
-
FedCM bundle: Continuation API, account labels, custom parameters, scopes w3ctag/design-reviews#945, by @cbiesinger.
-
Importmap integrity w3ctag/design-reviews#944, by @yoavweiss.
-
Spec review for Snap Events w3ctag/design-reviews#943, by @DavMila.
-
Constructors for RTC encoded frames with custom metadata w3ctag/design-reviews#942, by @guidou.
-
-
2 issues closed.
-
CSS ::selection Inheritance Model w3ctag/design-reviews#914.
-
Gamepad Trigger Rumble Extension w3ctag/design-reviews#934.
-
-
16 issues received 43 new comments.
-
Specification review for CSS Anchor Positioning w3ctag/design-reviews#848 (8 comments by @LeaVerou, @mfreed7, @plinss, @tabatkins)
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (7 comments by @alancutter, @dmurph, @hober, @LuHuangMSFT, @tomayac, @torgo)
-
Updated review of WebNN API w3ctag/design-reviews#933 (5 comments by @anssiko, @dontcallmedom, @matatk)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (2 comments by @steimelchrome, @torgo)
-
Specification review for fenced frames w3ctag/design-reviews#838 (2 comments by @blu25, @shivanigithub)
-
Early TAG review request for Playout Statistics API for WebAudio w3ctag/design-reviews#939 (1 comment by @matatk)
-
w3ctag/design-principles
-
4 issues opened.
-
Newlines in source cause broken links w3ctag/design-principles#491, by @edent.
-
New principle: Incorporate from existing CSS Design Principles w3ctag/design-principles#490, by @fantasai.
-
New principle: accept arrays of bytes as BufferSource w3ctag/design-principles#486, by @bakkot.
-
Link errors in current w3ctag/design-principles#484, by @martinthomson.
-
-
1 issue closed.
-
New principle: APIs which vend byte buffers should return a Uint8Array w3ctag/design-principles#463.
-
-
8 issues received 11 new comments.
-
New principle: When introducing heuristics or "magic", also include a way to override them w3ctag/design-principles#455 (3 comments by @annevk, @LeaVerou, @martinthomson)
-
New principle: Events should only fire during actual state transitions w3ctag/design-principles#483 (2 comments by @annevk, @LeaVerou)
-
New principle: CSS color functions should always accept `<number>` as well for each numerical component w3ctag/design-principles#447 (1 comment by @fantasai)
-
"while a JavaScript event loop is running." is probably not intended w3ctag/design-principles#456 (1 comment by @torgo)
-
New principle: Incremental author effort should result in commensurate value w3ctag/design-principles#473 (1 comment by @martinthomson)
-
-
5 pull requests opened.
-
fix link, see #491 w3ctag/design-principles#492, by @ylafon.
-
Fix some nits w3ctag/design-principles#489, by @martinthomson.
-
Editorial updates to media types section w3ctag/design-principles#488, by @martinthomson.
-
Update principle on HTTP usage w3ctag/design-principles#487, by @martinthomson.
-
Attempt to split attribute by type w3ctag/design-principles#485, by @martinthomson.
-
-
4 pull requests merged.
-
fix link, see #491 w3ctag/design-principles#492.
-
Fix some nits w3ctag/design-principles#489.
-
New principle: vend byte arrays as Uint8Arrays w3ctag/design-principles#480.
-
More detail on why events should fire before promises w3ctag/design-principles#460.
-
-
8 pull requests received 20 new comments.
-
More detail on why events should fire before promises w3ctag/design-principles#460 (5 comments by @LeaVerou, @martinthomson)
-
New principle: vend byte arrays as Uint8Arrays w3ctag/design-principles#480 (5 comments by @martinthomson)
-
Attempt to split attribute by type w3ctag/design-principles#485 (4 comments by @annevk, @LeaVerou, @martinthomson)
-
w3ctag/ethical-web-principles
-
2 issues opened.
-
Addition to principle 2.2 w3ctag/ethical-web-principles#117, by @simoneonofri.
-
Extend I18N/L10N to include support for languages and especially cultures w3ctag/ethical-web-principles#116, by @aphillips.
-
-
2 issues received 3 new comments.
-
Extend I18N/L10N to include support for languages and especially cultures w3ctag/ethical-web-principles#116 (1 comment by @torgo)
-
1 pull request opened.
-
grammar review w3ctag/ethical-web-principles#113, by @rinchen.
-
w3ctag/privacy-principles
-
1 issue closed.
-
Reconcile browser funding with Loyalty w3ctag/privacy-principles#414.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Add labels to the principles summary w3ctag/privacy-principles#416, by @darobin.
-
-
1 pull request received 2 new comments.
-
Add labels to the principles summary w3ctag/privacy-principles#416 (2 comments by @darobin, @jyasskin)
-
TR publications
-
1 document published.
-
Ethical Web Principles published as a Draft Note. History of Ethical Web Principles
-
GitHub
w3ctag/ethical-web-principles
-
2 issues opened.
-
Are these really principles? w3ctag/ethical-web-principles#111, by @mnot.
-
A small modification to principle 2.5 w3ctag/ethical-web-principles#112, by @simoneonofri.
-
-
4 issues closed.
-
Find a voice w3ctag/ethical-web-principles#79.
-
Be more specific on stakeholders w3ctag/ethical-web-principles#59.
-
Relationship with Design Principles w3ctag/ethical-web-principles#37.
-
Say something about resisting interpersonal abuse w3ctag/ethical-web-principles#44.
-
-
4 issues received 7 new comments.
-
A small modification to principle 2.5 w3ctag/ethical-web-principles#112 (4 comments by @jyasskin, @mnot, @simoneonofri)
-
Say something about resisting interpersonal abuse w3ctag/ethical-web-principles#44 (1 comment by @rhiaro)
-
-
1 pull request opened.
-
Clarify stakeholders... w3ctag/ethical-web-principles#110, by @torgo.
-
-
2 pull requests merged.
-
Clarify stakeholders... w3ctag/ethical-web-principles#110.
-
Mention interpersonal abuse in 'should not cause harm' for #44 w3ctag/ethical-web-principles#108.
-
-
1 pull request received 1 new comment.
w3ctag/design-reviews
-
3 issues opened.
-
Wide review request for Pointer Events Level 3 w3ctag/design-reviews#941, by @patrickhlauke.
-
JS String Builtins for WebAssembly w3ctag/design-reviews#940, by @ajklein.
-
Early TAG review request for Playout Statistics API for WebAudio w3ctag/design-reviews#939, by @Hernqvist.
-
-
5 issues closed.
-
Side Panel w3ctag/design-reviews#903.
-
TAG review request for the IDP signin status API w3ctag/design-reviews#884.
-
Allow transferring ArrayBuffer into WebCodecs object constructors w3ctag/design-reviews#889.
-
DeviceOrientation Event Specification w3ctag/design-reviews#928.
-
Invokers API w3ctag/design-reviews#920.
-
-
21 issues received 44 new comments.
-
DeviceOrientation Event Specification w3ctag/design-reviews#928 (5 comments by @anssiko, @reillyeon, @torgo)
-
BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures w3ctag/design-reviews#922 (4 comments by @martinthomson, @msporny, @simoneonofri, @Wind4Greg)
-
Allow transferring ArrayBuffer into WebCodecs object constructors w3ctag/design-reviews#889 (3 comments by @Djuffin, @torgo)
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (2 comments by @LuHuangMSFT, @torgo)
-
Early TAG review request for Playout Statistics API for WebAudio w3ctag/design-reviews#939 (2 comments by @Hernqvist, @martinthomson)
-
Web Audio API: RenderCapacity API w3ctag/design-reviews#843 (2 comments by @LeaVerou, @martinthomson)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (2 comments by @hober, @matatk)
-
Cross-document View Transitions API w3ctag/design-reviews#851 (2 comments by @khushalsagar, @miketaylr)
w3ctag/design-principles
-
5 issues opened.
-
New principle: Events should only fire during actual state transitions w3ctag/design-principles#483, by @LeaVerou.
-
Harmonize with WebAppSec Powerful Features Draft w3ctag/design-principles#481, by @torgo.
-
Terminology jumps away from principle's subject ("Use care when exposing identifying information about devices") w3ctag/design-principles#479, by @matatk.
-
New principle: HTML attributes can affect semantics w3ctag/design-principles#478, by @chrishtr.
-
New: Avoid revealing that consent was denied w3ctag/design-principles#475, by @martinthomson.
-
-
1 issue closed.
-
Add info to device apis section about privacy w3ctag/design-principles#398.
-
-
8 issues received 15 new comments.
-
New principle: HTML attributes can affect semantics w3ctag/design-principles#478 (4 comments by @annevk, @chrishtr, @domenic)
-
New principle: APIs which vend byte buffers should return a Uint8Array w3ctag/design-principles#463 (3 comments by @bakkot, @plinss)
-
New principle: Text-based syntaxes should be designed to be usable by humans w3ctag/design-principles#453 (3 comments by @martinthomson, @OR13, @plinss)
-
New principle: Events should only fire during actual state transitions w3ctag/design-principles#483 (1 comment by @annevk)
-
New principle: Avoid adding (non-constructor) functions to the global scope w3ctag/design-principles#426 (1 comment by @LeaVerou)
-
New principle: Discourage polyglot formats w3ctag/design-principles#239 (1 comment by @martinthomson)
-
-
4 pull requests opened.
-
Update CODE_OF_CONDUCT.md to point to new w3c code w3ctag/design-principles#482, by @torgo.
-
New principle: vend byte arrays as Uint8Arrays w3ctag/design-principles#480, by @bakkot.
-
It looks like this text was duplicated w3ctag/design-principles#477, by @martinthomson.
-
Denying consent is better if undetectable as such w3ctag/design-principles#476, by @martinthomson.
-
-
3 pull requests merged.
-
Add info to 9.1 ("Use care when exposing identifying information about devices") & change link w3ctag/design-principles#470.
-
New principle: Identity on the web w3ctag/design-principles#396.
-
Short is often better w3ctag/design-principles#474.
-
-
5 pull requests received 17 new comments.
-
New principle: vend byte arrays as Uint8Arrays w3ctag/design-principles#480 (6 comments by @annevk, @bakkot, @martinthomson)
-
Add info to 9.1 ("Use care when exposing identifying information about devices") & change link w3ctag/design-principles#470 (6 comments by @martinthomson, @torgo)
-
It looks like this text was duplicated w3ctag/design-principles#477 (2 comments by @LeaVerou, @martinthomson)
-
First pass at #453 (text-based syntaxes should be designed for humans) w3ctag/design-principles#472 (2 comments by @matatk)
-
w3ctag/privacy-principles
-
2 issues opened.
-
Reconcile browser funding with Loyalty w3ctag/privacy-principles#414, by @jyasskin.
-
Add labels to Principles Summary w3ctag/privacy-principles#413, by @chrisn.
-
-
1 issue closed.
-
Please copy edit acting on data section w3ctag/privacy-principles#406.
-
-
2 issues received 4 new comments.
-
1 pull request opened.
-
Wondering whether a 1-pager would be useful. w3ctag/privacy-principles#412, by @ianbjacobs.
-
-
1 pull request merged.
-
Clarify which data is personal data. w3ctag/privacy-principles#410.
-
-
2 pull requests received 5 new comments.
-
Clarify which data is personal data. w3ctag/privacy-principles#410 (3 comments by @jyasskin, @wseltzer)
-
Wondering whether a 1-pager would be useful. w3ctag/privacy-principles#412 (2 comments by @ianbjacobs, @jyasskin)
-
w3ctag/tag.w3.org
-
1 pull request opened.
-
Workmode: Update with proposed new process w3ctag/tag.w3.org#48, by @rhiaro.
-
-
1 pull request merged.
-
Workmode: Update with proposed new process w3ctag/tag.w3.org#48.
-
-
1 pull request received 64 new comments.
-
Workmode: Update with proposed new process w3ctag/tag.w3.org#48 (64 comments by @LeaVerou, @martinthomson, @matatk, @plinss, @rhiaro, @torgo)
-
TR publications
-
4 documents published.
-
Ethical Web Principles published twice as a Draft Note. History of Ethical Web Principles
-
Privacy Principles published twice as a Draft Note. History of Privacy Principles
-
Participants
-
2 participants joined.
-
Matthew Atkinson joined.
-
Martin Thomson joined.
-
-
2 participants left.
-
Sangwhan Moon left.
-
Rossen Atanassov left.
-
GitHub
w3ctag/privacy-principles
-
3 issues opened.
-
Please copy edit acting on data section w3ctag/privacy-principles#406, by @chaals.
-
Opt-in vs. Opt-out w3ctag/privacy-principles#405, by @torgo.
-
Duty of Honesty w3ctag/privacy-principles#401, by @chrisn.
-
-
3 issues received 8 new comments.
-
Please copy edit acting on data section w3ctag/privacy-principles#406 (4 comments by @chaals, @darobin, @jyasskin)
-
-
8 pull requests opened.
-
Clarify which data is personal data. w3ctag/privacy-principles#410, by @jyasskin.
-
Auto-update our GH Actions dependencies w3ctag/privacy-principles#409, by @jyasskin.
-
Grammar fixes including fixing missing oxford comas. w3ctag/privacy-principles#408, by @rinchen.
-
minor grammar cleanup w3ctag/privacy-principles#407, by @chaals.
-
SOTD fix, document now ready for wide review w3ctag/privacy-principles#404, by @ylafon.
-
UAs should give information, not just try to. w3ctag/privacy-principles#403, by @jyasskin.
-
Vulnerable people wording and links w3ctag/privacy-principles#402, by @dmarti.
-
-
7 pull requests merged.
-
Auto-update our GH Actions dependencies w3ctag/privacy-principles#409.
-
Grammar fixes including fixing missing oxford comas. w3ctag/privacy-principles#408.
-
UAs should give information, not just try to. w3ctag/privacy-principles#403.
-
minor grammar cleanup w3ctag/privacy-principles#407.
-
SOTD fix, document now ready for wide review w3ctag/privacy-principles#404.
-
Vulnerable people wording and links w3ctag/privacy-principles#402.
-
Fix typos w3ctag/privacy-principles#400.
-
-
4 pull requests received 10 new comments.
-
Grammar fixes including fixing missing oxford comas. w3ctag/privacy-principles#408 (4 comments by @darobin, @jyasskin, @rinchen)
-
w3ctag/privacy-principles#411 (1 comment by @jyasskin)
-
w3ctag/design-reviews
-
9 issues opened.
-
View Transition Classes w3ctag/design-reviews#938, by @vmpstr.
-
FedCM API extension: Button Mode and User Other Account API w3ctag/design-reviews#935, by @yi-gu.
-
Gamepad Trigger Rumble Extension w3ctag/design-reviews#934, by @gabrielsanbrito.
-
Updated review of WebNN API w3ctag/design-reviews#933, by @dontcallmedom.
-
Local Peer-to-Peer API w3ctag/design-reviews#932, by @anssiko.
-
Speculation rules: target_hint field w3ctag/design-reviews#931, by @nhiroki.
-
Zstandard Content-Encoding w3ctag/design-reviews#930, by @nidhijaju.
-
DeviceOrientation Event Specification w3ctag/design-reviews#928, by @anssiko.
-
WAI-ARIA 1.3 FPWD w3ctag/design-reviews#927, by @daniel-montalvo.
-
-
16 issues closed.
-
Related Website Sets (formerly First-Party Sets) w3ctag/design-reviews#342.
-
Early design review for the Topics API w3ctag/design-reviews#726.
-
Delayed Clipboard Rendering w3ctag/design-reviews#925.
-
BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures w3ctag/design-reviews#922.
-
Verifiable Credential Status List 2021 w3ctag/design-reviews#874.
-
Zstandard Content-Encoding w3ctag/design-reviews#930.
-
Verifiable Credentials Data Model v2.0 w3ctag/design-reviews#860.
-
WAI-ARIA 1.3 FPWD w3ctag/design-reviews#927.
-
Review request for Protected Audience w3ctag/design-reviews#723.
-
Early design review request: IPA w3ctag/design-reviews#823.
-
requestStorageAccessFor w3ctag/design-reviews#808.
-
TAG spec review of Storage Access Heuristics w3ctag/design-reviews#919.
-
Feature detection for supported clipboard formats w3ctag/design-reviews#901.
-
`field-sizing` CSS property w3ctag/design-reviews#890.
-
Spec review for CSS Nesting w3ctag/design-reviews#791.
-
Fullscreen Popup Windows w3ctag/design-reviews#840.
-
-
2 issues reopened.
-
Related Website Sets (formerly First-Party Sets) w3ctag/design-reviews#342, by @plinss.
-
Early review for adding a new value to the standard list of `name`s for a meta tag w3ctag/design-reviews#819, by @torgo.
-
-
39 issues received 82 new comments.
-
Delayed Clipboard Rendering w3ctag/design-reviews#925 (7 comments by @martinthomson, @plinss, @snianu)
-
Invokers API w3ctag/design-reviews#920 (6 comments by @keithamus, @lukewarlow, @martinthomson, @mfreed7)
-
Adding support for High Dynamic Range (HDR) imagery to HTML Canvas w3ctag/design-reviews#917 (6 comments by @jyasskin, @LeaVerou, @palemieux, @plinss, @svgeesus)
-
Document Render-Blocking w3ctag/design-reviews#886 (6 comments by @khushalsagar, @martinthomson, @noamr, @plinss, @vmpstr)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (4 comments by @beaufortfrancois, @steimelchrome)
-
Early review for adding a new value to the standard list of `name`s for a meta tag w3ctag/design-reviews#819 (3 comments by @diekus, @hober)
-
TAG review request for the IDP signin status API w3ctag/design-reviews#884 (2 comments by @cbiesinger, @rhiaro)
-
early design review: Permissions-Policy: unload w3ctag/design-reviews#738 (2 comments by @fergald, @torgo)
-
Review Request for Attribution Reporting API w3ctag/design-reviews#724 (2 comments by @linnan-github, @torgo)
-
BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures w3ctag/design-reviews#922 (1 comment by @rhiaro)
-
New attribute to control UA-provided writing assistance w3ctag/design-reviews#924 (1 comment by @sanketj)
-
w3ctag/tracking-issues
-
8 issues closed.
-
Detach codec inputs (where feasible) w3ctag/tracking-issues#53.
-
change units of timestamp or rename to timestampMicros w3ctag/tracking-issues#54.
-
Content Module 1 - Distraction values and examples need to be updated w3ctag/tracking-issues#61.
-
Should all MathML elements really be potential hyperlinks / match :visited? w3ctag/tracking-issues#57.
-
Add an explainer w3ctag/tracking-issues#74.
-
remove securing json w3ctag/tracking-issues#75.
-
Should all MathML elements really be potential hyperlinks / match :visited? w3ctag/tracking-issues#59.
-
Should all MathML elements really be potential hyperlinks / match :visited? w3ctag/tracking-issues#58.
-
-
8 issues received 8 new comments.
-
change units of timestamp or rename to timestampMicros w3ctag/tracking-issues#54 (1 comment by @plehegar)
-
Content Module 1 - Distraction values and examples need to be updated w3ctag/tracking-issues#61 (1 comment by @plehegar)
-
Should all MathML elements really be potential hyperlinks / match :visited? w3ctag/tracking-issues#57 (1 comment by @plehegar)
-
Should all MathML elements really be potential hyperlinks / match :visited? w3ctag/tracking-issues#59 (1 comment by @plehegar)
-
Should all MathML elements really be potential hyperlinks / match :visited? w3ctag/tracking-issues#58 (1 comment by @plehegar)
w3ctag/polyfills
-
1 issue closed.
-
https://w3ctag.github.io/polyfills/ show raw text w3ctag/polyfills#33.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Remove reference to polyfill.io w3ctag/polyfills#37, by @triblondon.
-
-
1 pull request merged.
-
Remove reference to polyfill.io w3ctag/polyfills#37.
-
-
1 pull request received 2 new comments.
w3ctag/ethical-web-principles
-
1 issue opened.
-
Participating in the Open Web with the Expectation You Won't Be Part of Data Harvests w3ctag/ethical-web-principles#109, by @cgrobb.
-
-
1 issue closed.
-
Grammatical consistency of principles w3ctag/ethical-web-principles#75.
-
-
1 issue received 3 new comments.
-
Participating in the Open Web with the Expectation You Won't Be Part of Data Harvests w3ctag/ethical-web-principles#109 (3 comments by @cgrobb, @csarven, @rhiaro)
-
-
1 pull request merged.
-
Make principles grammatically consistent as aspirational statements, … w3ctag/ethical-web-principles#105.
-
w3ctag/design-principles
-
1 issue opened.
-
New principle: Incremental author effort should result in commensurate value w3ctag/design-principles#473, by @LeaVerou.
-
-
1 issue received 1 new comment.
-
New principle: Text-based syntaxes should be designed to be usable by humans w3ctag/design-principles#453 (1 comment by @martinthomson)
-
-
2 pull requests opened.
-
Short is often better w3ctag/design-principles#474, by @martinthomson.
-
First pass at #453 (text-based syntaxes should be designed for humans) w3ctag/design-principles#472, by @LeaVerou.
-
-
2 pull requests received 3 new comments.
-
First pass at #453 (text-based syntaxes should be designed for humans) w3ctag/design-principles#472 (2 comments by @LeaVerou, @martinthomson)
-
Add info to 9.1 ("Use care when exposing identifying information about devices") & change link w3ctag/design-principles#470 (1 comment by @matatk)
-
w3ctag/tag.w3.org
-
4 pull requests opened.
-
added some references to appointements w3ctag/tag.w3.org#47, by @ylafon.
-
(Bug) Fixed JSON w3ctag/tag.w3.org#46, by @ianbjacobs.
-
Add Ian Jacobs to history as staff contact w3ctag/tag.w3.org#45, by @ianbjacobs.
-
added link to election results w3ctag/tag.w3.org#44, by @ylafon.
-
-
4 pull requests merged.
-
(Bug) Fixed JSON w3ctag/tag.w3.org#46.
-
Add Ian Jacobs to history as staff contact w3ctag/tag.w3.org#45.
-
Various updates to historical membership data. w3ctag/tag.w3.org#43.
-
added link to election results w3ctag/tag.w3.org#44.
-
-
3 pull requests received 4 new comments.
-
Various updates to historical membership data. w3ctag/tag.w3.org#43 (2 comments by @dbaron, @LeaVerou)
-
TR publications
-
2 documents published.
-
Web Platform Design Principles published as a Note. History of Web Platform Design Principles
-
Privacy Principles published as a Draft Note. History of Privacy Principles
-
GitHub
w3ctag/design-reviews
-
1 issue opened.
-
Delayed Clipboard Rendering w3ctag/design-reviews#925, by @snianu.
-
-
11 issues closed.
-
VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport w3ctag/design-reviews#768.
-
The `FileSystemObserver` interface w3ctag/design-reviews#868.
-
Web Audio API: User-Selectable Render Quantum Size w3ctag/design-reviews#895.
-
New attribute to control UA-provided writing assistance w3ctag/design-reviews#924.
-
Adding a close event to MessagePort API w3ctag/design-reviews#923.
-
DisplayMediaStreamOptions monitorTypeSurfaces w3ctag/design-reviews#892.
-
Tabbed web apps w3ctag/design-reviews#841.
-
early design review: bfcache/prerendering eviction APIs w3ctag/design-reviews#786.
-
Early Design Review: Pending Beacon API w3ctag/design-reviews#776.
-
Navigation Activation Info w3ctag/design-reviews#921.
-
deliveryType (Resource Timing) w3ctag/design-reviews#858.
-
-
2 issues reopened.
-
Feature detection for supported clipboard formats w3ctag/design-reviews#901, by @plinss.
-
early design review: bfcache/prerendering eviction APIs w3ctag/design-reviews#786, by @cynthia.
-
-
41 issues received 90 new comments.
-
Feature detection for supported clipboard formats w3ctag/design-reviews#901 (7 comments by @annevk, @LeaVerou, @snianu)
-
Adding support for High Dynamic Range (HDR) imagery to HTML Canvas w3ctag/design-reviews#917 (6 comments by @palemieux, @svgeesus)
-
Specification review for fenced frames w3ctag/design-reviews#838 (5 comments by @blu25, @gtanzer, @rhiaro, @shivanigithub)
-
Review request for Protected Audience w3ctag/design-reviews#723 (4 comments by @hadleybeeman, @JensenPaul, @lknik)
-
BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures w3ctag/design-reviews#922 (4 comments by @hadleybeeman, @jyasskin, @msporny, @Wind4Greg)
-
TAG spec review of Storage Access Heuristics w3ctag/design-reviews#919 (4 comments by @amaliev, @torgo, @wanderview)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (4 comments by @domenic, @LeaVerou)
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (3 comments by @cynthia, @LuHuangMSFT)
-
Review OffscreenCanvas, including ImageBitmapRenderingContext w3ctag/design-reviews#141 (3 comments by @greggman, @Swoorup)
-
VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport w3ctag/design-reviews#768 (2 comments by @hadleybeeman, @tguild)
-
DisplayMediaStreamOptions monitorTypeSurfaces w3ctag/design-reviews#892 (2 comments by @beaufortfrancois, @cynthia)
-
Extending Storage Access API (SAA) to non-cookie storage w3ctag/design-reviews#906 (2 comments by @arichiv, @torgo)
-
Web Audio API: User-Selectable Render Quantum Size w3ctag/design-reviews#895 (1 comment by @cynthia)
-
Early review for adding a new value to the standard list of `name`s for a meta tag w3ctag/design-reviews#819 (1 comment by @diekus)
-
Review Request for Attribution Reporting API w3ctag/design-reviews#724 (1 comment by @linnan-github)
-
New attribute to control UA-provided writing assistance w3ctag/design-reviews#924 (1 comment by @hober)
-
early design review: bfcache/prerendering eviction APIs w3ctag/design-reviews#786 (1 comment by @cynthia)
-
-
2 pull requests merged.
-
Suggest linking to standards positions w3ctag/design-reviews#898.
-
Add examples of stakeholders to issue template w3ctag/design-reviews#844.
-
-
2 pull requests received 5 new comments.
-
Suggest linking to standards positions w3ctag/design-reviews#898 (3 comments by @cynthia, @miketaylr)
-
Add examples of stakeholders to issue template w3ctag/design-reviews#844 (2 comments by @martinthomson, @miketaylr)
-
w3ctag/tag.w3.org
-
2 pull requests opened.
-
Various updates to historical membership data. w3ctag/tag.w3.org#43, by @dbaron.
-
Hadley Beeman 2023-02-01 appointment w3ctag/tag.w3.org#42, by @tantek.
-
-
1 pull request merged.
-
Hadley Beeman 2023-02-01 appointment w3ctag/tag.w3.org#42.
-
-
2 pull requests received 3 new comments.
-
Ask people to list non-consensus dependencies in their explainers. w3ctag/tag.w3.org#40 (2 comments by @jyasskin, @martinthomson)
-
w3ctag/privacy-principles
-
2 issues opened.
-
Make targeted lists of principles for each audience w3ctag/privacy-principles#397, by @jyasskin.
-
non-retaliation principle audience should probably also include user agents w3ctag/privacy-principles#396, by @npdoty.
-
-
3 issues closed.
-
Match principles with the document's audiences/conformance classes w3ctag/privacy-principles#343.
-
Be consistent/intentional on "must" vs "should" and RFC 2119 language w3ctag/privacy-principles#371.
-
Add a definition for "abuse" w3ctag/privacy-principles#330.
-
-
3 issues received 4 new comments.
-
Consider removing the definition of "vulnerable people". w3ctag/privacy-principles#373 (2 comments by @dmarti, @npdoty)
-
Be consistent/intentional on "must" vs "should" and RFC 2119 language w3ctag/privacy-principles#371 (1 comment by @darobin)
-
-
6 pull requests opened.
-
Simplify data minimization w3ctag/privacy-principles#399, by @torgo.
-
Create 2024-01-17-minutes.md w3ctag/privacy-principles#398, by @torgo.
-
Create 2024-01-10-minutes.md w3ctag/privacy-principles#395, by @torgo.
-
Adds cute little audience pills w3ctag/privacy-principles#394, by @darobin.
-
RFC2119 changes w3ctag/privacy-principles#393, by @darobin.
-
Define abuse, selectively link, include in def of harassment w3ctag/privacy-principles#392, by @darobin.
-
-
8 pull requests merged.
-
Simplify data minimization w3ctag/privacy-principles#399.
-
Create 2024-01-17-minutes.md w3ctag/privacy-principles#398.
-
Adds cute little audience pills w3ctag/privacy-principles#394.
-
RFC2119 changes w3ctag/privacy-principles#393.
-
Define abuse, selectively link, include in def of harassment w3ctag/privacy-principles#392.
-
Create 2024-01-10-minutes.md w3ctag/privacy-principles#395.
-
Status: TAG consensus w3ctag/privacy-principles#391.
-
The Notifications section already mentions autonomy, so remove the issue about it. w3ctag/privacy-principles#390.
-
-
2 pull requests received 7 new comments.
-
Define abuse, selectively link, include in def of harassment w3ctag/privacy-principles#392 (2 comments by @npdoty, @torgo)
w3ctag/design-principles
-
1 issue opened.
-
New principle: APIs which vend byte buffers should return a Uint8Array w3ctag/design-principles#463, by @bakkot.
-
-
2 issues closed.
-
New principle: Naming of factory methods w3ctag/design-principles#378.
-
New principle: Data Minimization w3ctag/design-principles#399.
-
-
4 issues received 6 new comments.
-
Use of "attribute" confusing/ambiguous w3ctag/design-principles#457 (2 comments by @bkardell, @LeaVerou)
-
New principle: When introducing heuristics or "magic", also include a way to override them w3ctag/design-principles#455 (1 comment by @LeaVerou)
-
9 pull requests opened.
-
Add guidance for factory method naming w3ctag/design-principles#471, by @cynthia.
-
Add info to 9.1 ("Use care when exposing identifying information about devices") & change link w3ctag/design-principles#470, by @torgo.
-
Add some discussion on adding removing features w3ctag/design-principles#469, by @martinthomson.
-
[WIP] add forwards compatibility / graceful degradation principle. w3ctag/design-principles#468, by @hober.
-
Add principle on use of delta seconds w3ctag/design-principles#467, by @torgo.
-
Update references to WebIDL in notes w3ctag/design-principles#466, by @ylafon.
-
Add data minimization principle w3ctag/design-principles#465, by @torgo.
-
fix the build w3ctag/design-principles#464, by @hober.
-
Add Lea as editor. w3ctag/design-principles#462, by @cynthia.
-
-
6 pull requests merged.
-
Add guidance for factory method naming w3ctag/design-principles#471.
-
Add data minimization principle w3ctag/design-principles#465.
-
Add some discussion on adding removing features w3ctag/design-principles#469.
-
Update references to WebIDL in notes w3ctag/design-principles#466.
-
fix the build w3ctag/design-principles#464.
-
Add Lea as editor. w3ctag/design-principles#462.
-
-
3 pull requests closed.
-
First pass on backwards compatibility principle w3ctag/design-principles#354.
-
Start developer version w3ctag/design-principles#386.
-
Make 6.1 more inclusive of non-Web JS APIs w3ctag/design-principles#435.
-
-
13 pull requests received 129 new comments.
-
Add some discussion on adding removing features w3ctag/design-principles#469 (44 comments by @cynthia, @hober, @LeaVerou, @martinthomson, @rhiaro, @torgo)
-
Add data minimization principle w3ctag/design-principles#465 (23 comments by @cynthia, @LeaVerou, @rhiaro, @torgo)
-
Add guidance for factory method naming w3ctag/design-principles#471 (17 comments by @cynthia, @LeaVerou, @rhiaro)
-
More detail on why events should fire before promises w3ctag/design-principles#460 (11 comments by @annevk, @jakearchibald, @LeaVerou, @martinthomson)
-
First pass on backwards compatibility principle w3ctag/design-principles#354 (8 comments by @LeaVerou, @martinthomson)
-
New principle: Identity on the web w3ctag/design-principles#396 (7 comments by @cynthia, @rhiaro, @torgo)
-
[WIP] add forwards compatibility / graceful degradation principle. w3ctag/design-principles#468 (6 comments by @cynthia, @hober, @LeaVerou, @martinthomson)
-
Add info to 9.1 ("Use care when exposing identifying information about devices") & change link w3ctag/design-principles#470 (5 comments by @cynthia, @martinthomson, @rhiaro, @torgo)
-
Add principle on use of delta seconds w3ctag/design-principles#467 (3 comments by @cynthia, @LeaVerou, @martinthomson)
-
w3ctag/ethical-web-principles
-
4 issues closed.
-
Protect vs Control w3ctag/ethical-web-principles#80.
-
Not using principles in isolation w3ctag/ethical-web-principles#76.
-
The claimed history is inaccurate (and "rose-coloured") w3ctag/ethical-web-principles#100.
-
document title doesn't need to include the standards body name and group name ("W3C TAG") w3ctag/ethical-web-principles#102.
-
-
1 issue received 1 new comment.
-
The claimed history is inaccurate (and "rose-coloured") w3ctag/ethical-web-principles#100 (1 comment by @torgo)
-
-
4 pull requests opened.
-
Mention interpersonal abuse in 'should not cause harm' for #44 w3ctag/ethical-web-principles#108, by @rhiaro.
-
Protect to control, fixes #80 w3ctag/ethical-web-principles#107, by @rhiaro.
-
Edit intro, fixes #76 w3ctag/ethical-web-principles#106, by @rhiaro.
-
Make principles grammatically consistent as aspirational statements, … w3ctag/ethical-web-principles#105, by @rhiaro.
-
-
4 pull requests merged.
-
Protect to control, fixes #80 w3ctag/ethical-web-principles#107.
-
Edit intro, fixes #76 w3ctag/ethical-web-principles#106.
-
Remove 'W3C TAG' from document title, closes #102 w3ctag/ethical-web-principles#103.
-
Intro editorial w3ctag/ethical-web-principles#104.
-
-
1 pull request received 3 new comments.
-
Mention interpersonal abuse in 'should not cause harm' for #44 w3ctag/ethical-web-principles#108 (3 comments by @hadleybeeman, @martinthomson, @rhiaro)
-
w3ctag/caching-bundling-sustainability
-
7 issues closed.
-
Include security and privacy issues addressed by partitioned caching w3ctag/caching-bundling-sustainability#8.
-
User identifiers in caches w3ctag/caching-bundling-sustainability#7.
-
Mention QUIC? w3ctag/caching-bundling-sustainability#5.
-
Make call to action explicit w3ctag/caching-bundling-sustainability#10.
-
Missing text w3ctag/caching-bundling-sustainability#2.
-
Don't throw the baby out with the bathwater w3ctag/caching-bundling-sustainability#4.
-
Section 3 - bandwidth costs w3ctag/caching-bundling-sustainability#3.
-
-
2 issues received 2 new comments.
-
Don't throw the baby out with the bathwater w3ctag/caching-bundling-sustainability#4 (1 comment by @hober)
-
4 pull requests opened.
-
QUIC, not SenML w3ctag/caching-bundling-sustainability#15, by @martinthomson.
-
Storage partitioning is beneficial to user privacy and security. w3ctag/caching-bundling-sustainability#14, by @hober.
-
Adding unbundling attempts in HTTP/2 w3ctag/caching-bundling-sustainability#13, by @ylafon.
-
Add explicit call to action and experimentation w3ctag/caching-bundling-sustainability#12, by @cynthia.
-
-
4 pull requests merged.
-
QUIC, not SenML w3ctag/caching-bundling-sustainability#15.
-
Add explicit call to action and experimentation w3ctag/caching-bundling-sustainability#12.
-
Storage partitioning is beneficial to user privacy and security. w3ctag/caching-bundling-sustainability#14.
-
Adding unbundling attempts in HTTP/2 w3ctag/caching-bundling-sustainability#13.
-
-
1 pull request closed.
-
Update index.html w3ctag/caching-bundling-sustainability#9.
-
-
5 pull requests received 29 new comments.
-
Storage partitioning is beneficial to user privacy and security. w3ctag/caching-bundling-sustainability#14 (9 comments by @arturjanc, @cynthia, @hober, @michaelkleber, @ylafon)
-
Adding unbundling attempts in HTTP/2 w3ctag/caching-bundling-sustainability#13 (9 comments by @cynthia, @LeaVerou, @torgo)
-
Add explicit call to action and experimentation w3ctag/caching-bundling-sustainability#12 (9 comments by @cynthia, @LeaVerou)
-
w3ctag/tracking-issues
-
1 issue opened.
-
TAG Review Request -- Submitted w3ctag/tracking-issues#77, by @w3cbot.
-