Technical Architecture Group - Activity in 2023
No matches.
Past meetings
GitHub
w3ctag/design-reviews
-
5 issues opened.
-
New attribute to control UA-provided writing assistance w3ctag/design-reviews#924, by @sanketj.
-
Adding a close event to MessagePort API w3ctag/design-reviews#923, by @nononokam.
-
BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures w3ctag/design-reviews#922, by @Wind4Greg.
-
Navigation Activation Info w3ctag/design-reviews#921, by @noamr.
-
Invokers API w3ctag/design-reviews#920, by @keithamus.
-
-
8 issues closed.
-
Extending the PointerEvent with Unique DeviceId Attribute w3ctag/design-reviews#880.
-
Relative Color Syntax (RCS) w3ctag/design-reviews#894.
-
navigateEvent.sourceElement w3ctag/design-reviews#867.
-
The CSS `word-break: auto-phrase` property w3ctag/design-reviews#891.
-
Soft Navigations w3ctag/design-reviews#879.
-
Intersection Observer Scroll Margin w3ctag/design-reviews#905.
-
@page margin boxes w3ctag/design-reviews#918.
-
WebCodecs support for AV1 screen content coding tools w3ctag/design-reviews#912.
-
-
23 issues received 46 new comments.
-
Verifiable Credentials Data Model v2.0 w3ctag/design-reviews#860 (3 comments by @awoie, @msporny, @rhiaro)
-
Extending the PointerEvent with Unique DeviceId Attribute w3ctag/design-reviews#880 (3 comments by @LeaVerou, @sahirv)
-
Permissions Policy Reporting and Report-Only mode w3ctag/design-reviews#909 (2 comments by @clelland, @torgo)
-
Extending Storage Access API (SAA) to non-cookie storage w3ctag/design-reviews#906 (2 comments by @arichiv, @torgo)
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (2 comments by @alancutter, @torgo)
-
confidence reporting for PerformanceNavigationTiming w3ctag/design-reviews#878 (2 comments by @hadleybeeman, @mwjacksonmsft)
-
BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures w3ctag/design-reviews#922 (2 comments by @martinthomson, @msporny)
-
Intersection Observer Scroll Margin w3ctag/design-reviews#905 (2 comments by @atanassov, @tcaptan-cr)
-
WebCodecs support for AV1 screen content coding tools w3ctag/design-reviews#912 (1 comment by @fippo)
w3ctag/process
-
2 issues opened.
-
Scaling design reviews w3ctag/process#34, by @LeaVerou.
-
Lowercase the web w3ctag/process#33, by @rhiaro.
-
-
1 issue received 3 new comments.
w3ctag/privacy-principles
-
2 issues opened.
-
Revisit 2.4 Sensitive Information section w3ctag/privacy-principles#388, by @pes10k.
-
resource minimization and control may be a privacy-relevant issue w3ctag/privacy-principles#386, by @npdoty.
-
-
10 issues closed.
-
Motivation and/or threat model for data minimization w3ctag/privacy-principles#370.
-
Making undesirable information hard to access w3ctag/privacy-principles#280.
-
What information access is being removed? w3ctag/privacy-principles#279.
-
Calrifications on the "should not reveal any personal data" principle w3ctag/privacy-principles#378.
-
Turning off ancillary APIs that provide new information is privacy-harmful w3ctag/privacy-principles#377.
-
Tweak "disabling privacy APIs with new information" w3ctag/privacy-principles#372.
-
"processing time or bandwidth" seem unrelated to privacy w3ctag/privacy-principles#376.
-
Improve definition of automation asymmetry w3ctag/privacy-principles#346.
-
Copy edit material before section 1 w3ctag/privacy-principles#297.
-
Copy edit section A, Common Concepts w3ctag/privacy-principles#317.
-
-
5 issues received 7 new comments.
-
Motivation and/or threat model for data minimization w3ctag/privacy-principles#370 (2 comments by @jyasskin, @npdoty)
-
Turning off ancillary APIs that provide new information is privacy-harmful w3ctag/privacy-principles#377 (2 comments by @jyasskin)
-
Calrifications on the "should not reveal any personal data" principle w3ctag/privacy-principles#378 (1 comment by @torgo)
-
Consider removing the definition of "vulnerable people". w3ctag/privacy-principles#373 (1 comment by @npdoty)
-
-
7 pull requests opened.
-
Status: TAG consensus w3ctag/privacy-principles#391, by @rhiaro.
-
The Notifications section already mentions autonomy, so remove the issue about it. w3ctag/privacy-principles#390, by @jyasskin.
-
Remove inline issue about payment, we'll write it later w3ctag/privacy-principles#389, by @darobin.
-
lowercase the web w3ctag/privacy-principles#387, by @jyasskin.
-
Avoid implying that ancillary APIs w/ new information should default to enabled. w3ctag/privacy-principles#385, by @jyasskin.
-
Remove mention of processing time and bandwidth. w3ctag/privacy-principles#384, by @jyasskin.
-
Create 2023-11-29-minutes.md w3ctag/privacy-principles#383, by @torgo.
-
-
10 pull requests merged.
-
Remove inline issue about payment, we'll write it later w3ctag/privacy-principles#389.
-
lowercase the web w3ctag/privacy-principles#387.
-
Avoid implying that ancillary APIs w/ new information should default to enabled. w3ctag/privacy-principles#385.
-
Remove mention of processing time and bandwidth. w3ctag/privacy-principles#384.
-
Make the minimization text more precise, and merge in the UA principle. w3ctag/privacy-principles#382.
-
Clarify the web API minimization principle. w3ctag/privacy-principles#381.
-
Improve definition of automation asymetry and simplify integration with global opt out, fix #346 w3ctag/privacy-principles#380.
-
Before section 1 editorial+reference tweaking, fixes #297 w3ctag/privacy-principles#379.
-
Copy-edit the Common Concepts section, except for the Recognition sub-section. w3ctag/privacy-principles#369.
-
Create 2023-11-29-minutes.md w3ctag/privacy-principles#383.
-
-
5 pull requests received 13 new comments.
-
Before section 1 editorial+reference tweaking, fixes #297 w3ctag/privacy-principles#379 (7 comments by @darobin, @jyasskin, @rhiaro)
-
Make the minimization text more precise, and merge in the UA principle. w3ctag/privacy-principles#382 (2 comments by @jyasskin)
-
Improve definition of automation asymetry and simplify integration with global opt out, fix #346 w3ctag/privacy-principles#380 (2 comments by @jyasskin)
-
Remove mention of processing time and bandwidth. w3ctag/privacy-principles#384 (1 comment by @npdoty)
-
w3ctag/caching-bundling-sustainability
-
2 issues opened.
-
add reference to brotli work w3ctag/caching-bundling-sustainability#11, by @torgo.
-
Make call to action explicit w3ctag/caching-bundling-sustainability#10, by @LeaVerou.
-
-
1 issue closed.
-
When cache partitioning was introduced w3ctag/caching-bundling-sustainability#1.
-
-
1 pull request opened.
-
Update index.html w3ctag/caching-bundling-sustainability#9, by @cynthia.
-
-
1 pull request merged.
-
Fix github links w3ctag/caching-bundling-sustainability#6.
-
w3ctag/design-principles
-
1 issue closed.
-
Duplicate section? w3ctag/design-principles#458.
-
-
3 issues received 5 new comments.
-
"while a JavaScript event loop is running." is probably not intended w3ctag/design-principles#456 (2 comments by @jakearchibald, @torgo)
-
I18N string best practices vs. design-principles w3ctag/design-principles#454 (2 comments by @aphillips, @torgo)
-
-
1 pull request opened.
-
Revert #262. Fixes #458. w3ctag/design-principles#461, by @hober.
-
-
1 pull request merged.
-
Revert #262. Fixes #458. w3ctag/design-principles#461.
-
-
1 pull request received 2 new comments.
w3ctag/ethical-web-principles
-
1 issue closed.
-
URL not rendering; missing 'to'? w3ctag/ethical-web-principles#98.
-
-
2 issues received 2 new comments.
-
The claimed history is inaccurate (and "rose-coloured") w3ctag/ethical-web-principles#100 (1 comment by @torgo)
-
2 pull requests opened.
-
Intro editorial w3ctag/ethical-web-principles#104, by @rhiaro.
-
Remove 'W3C TAG' from document title, closes #102 w3ctag/ethical-web-principles#103, by @rhiaro.
-
TR publications
-
1 document published.
-
W3C TAG Ethical Web Principles published as a Draft Note. History of W3C TAG Ethical Web Principles
-
GitHub
w3ctag/design-reviews
-
7 issues opened.
-
TAG spec review of Storage Access Heuristics w3ctag/design-reviews#919, by @amaliev.
-
@page margin boxes w3ctag/design-reviews#918, by @mstensho.
-
Adding support for High Dynamic Range (HDR) imagery to HTML Canvas w3ctag/design-reviews#917, by @palemieux.
-
Early Design Review: Opener Protections w3ctag/design-reviews#916, by @arichiv.
-
Animating font-palette w3ctag/design-reviews#915, by @tursunova.
-
CSS ::selection Inheritance Model w3ctag/design-reviews#914, by @schenney-chromium.
-
CSS Spelling and Grammar Customization w3ctag/design-reviews#913, by @schenney-chromium.
-
-
7 issues closed.
-
Specification review request for Verifiable Credential Data Integrity w3ctag/design-reviews#850.
-
VC JSON Schema w3ctag/design-reviews#859.
-
Animating font-palette w3ctag/design-reviews#915.
-
CSS Spelling and Grammar Customization w3ctag/design-reviews#913.
-
CSS `text-spacing` property and its longhands w3ctag/design-reviews#907.
-
Web Printing API w3ctag/design-reviews#910.
-
Tag review request for the "Dubbing and Audio description Profiles of TTML2" w3ctag/design-reviews#897.
-
-
1 issue reopened.
-
VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport w3ctag/design-reviews#768, by @plinss.
-
-
28 issues received 58 new comments.
-
WebCodecs support for AV1 screen content coding tools w3ctag/design-reviews#912 (7 comments by @cynthia, @Djuffin, @fippo)
-
Early Design Review: Opener Protections w3ctag/design-reviews#916 (5 comments by @arichiv, @hadleybeeman, @torgo)
-
Tag review request for the "Dubbing and Audio description Profiles of TTML2" w3ctag/design-reviews#897 (3 comments by @nigelmegitt, @rhiaro)
-
CSS Spelling and Grammar Customization w3ctag/design-reviews#913 (2 comments by @schenney-chromium, @torgo)
-
Extending Storage Access API (SAA) to non-cookie storage w3ctag/design-reviews#906 (2 comments by @arichiv, @torgo)
-
VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport w3ctag/design-reviews#768 (1 comment by @tguild)
-
Specification review request for Verifiable Credential Data Integrity w3ctag/design-reviews#850 (1 comment by @hadleybeeman)
-
Permissions Policy Reporting and Report-Only mode w3ctag/design-reviews#909 (1 comment by @hadleybeeman)
w3ctag/privacy-principles
-
9 issues opened.
-
Calrifications on the "should not reveal any personal data" principle w3ctag/privacy-principles#378, by @yoavweiss.
-
Turning off ancillary APIs that provide new information is privacy-harmful w3ctag/privacy-principles#377, by @yoavweiss.
-
"processing time or bandwidth" seem unrelated to privacy w3ctag/privacy-principles#376, by @yoavweiss.
-
Simplify the "processing" definition. w3ctag/privacy-principles#375, by @jyasskin.
-
Make the definition of "identifier" consistent with the list of identifiers w3ctag/privacy-principles#374, by @jyasskin.
-
Consider removing the definition of "vulnerable people". w3ctag/privacy-principles#373, by @jyasskin.
-
Tweak "disabling privacy APIs with new information" w3ctag/privacy-principles#372, by @torgo.
-
Be consistent/intentional on "must" vs "should" and RFC 2119 language w3ctag/privacy-principles#371, by @npdoty.
-
Motivation and/or threat model for data minimization w3ctag/privacy-principles#370, by @yoavweiss.
-
-
6 issues closed.
-
Remove or revise examples of signals browsers should use to prevent "privacy labor" in ancillary data w3ctag/privacy-principles#220.
-
Separate device owner and user agent owner w3ctag/privacy-principles#353.
-
Remove vulnerability principle and move the section into (1) w3ctag/privacy-principles#345.
-
Copy edit section 2.5, Data Rights w3ctag/privacy-principles#306.
-
Copy edit section 2.7, Collective Privacy w3ctag/privacy-principles#308.
-
More general principle mentioned in section 1.4? w3ctag/privacy-principles#329.
-
-
1 issue reopened.
-
"should best" and collective privacy w3ctag/privacy-principles#351, by @jyasskin.
-
-
9 issues received 11 new comments.
-
Motivation and/or threat model for data minimization w3ctag/privacy-principles#370 (3 comments by @dmarti, @jyasskin, @yoavweiss)
-
Making undesirable information hard to access w3ctag/privacy-principles#280 (1 comment by @jyasskin)
-
Tweak "disabling privacy APIs with new information" w3ctag/privacy-principles#372 (1 comment by @yoavweiss)
-
Consider removing the definition of "vulnerable people". w3ctag/privacy-principles#373 (1 comment by @pes10k)
-
-
9 pull requests opened.
-
Make the minimization text more precise, and merge in the UA principle. w3ctag/privacy-principles#382, by @jyasskin.
-
Clarify the web API minimization principle. w3ctag/privacy-principles#381, by @jyasskin.
-
Improve definition of automation asymetry and simplify integration with global opt out, fix #346 w3ctag/privacy-principles#380, by @darobin.
-
Before section 1 editorial+reference tweaking, fixes #297 w3ctag/privacy-principles#379, by @darobin.
-
Copy-edit the Common Concepts section, except for the Recognition sub-section. w3ctag/privacy-principles#369, by @jyasskin.
-
Separate device administrators from UA administrators. w3ctag/privacy-principles#368, by @jyasskin.
-
Remove the vulnerability principle, and move the section to Section 1. w3ctag/privacy-principles#367, by @jyasskin.
-
purpose limitation section initial draft w3ctag/privacy-principles#366, by @npdoty.
-
Copy-edit the Collective Privacy section. w3ctag/privacy-principles#365, by @jyasskin.
-
-
8 pull requests merged.
-
Rewrite ancillary uses to focus on 2 kinds of ancillary APIs rather than ancillary data. w3ctag/privacy-principles#361.
-
Separate device administrators from UA administrators. w3ctag/privacy-principles#368.
-
Remove the vulnerability principle, and move the section to Section 1. w3ctag/privacy-principles#367.
-
Copy-edit the Collective Privacy section. w3ctag/privacy-principles#365.
-
Don't say collective decision-making is strictly superior to engagement with individuals. w3ctag/privacy-principles#363.
-
Create 2023-09-06-minutes.md w3ctag/privacy-principles#356.
-
Edit section 2.5 w3ctag/privacy-principles#364.
-
purpose limitation section initial draft w3ctag/privacy-principles#366.
-
-
1 pull request closed.
-
remove list of privacy labor suggestions around ancillary data w3ctag/privacy-principles#221.
-
-
7 pull requests received 55 new comments.
-
Rewrite ancillary uses to focus on 2 kinds of ancillary APIs rather than ancillary data. w3ctag/privacy-principles#361 (16 comments by @jyasskin, @pes10k)
-
Copy-edit the Collective Privacy section. w3ctag/privacy-principles#365 (6 comments by @darobin, @jyasskin, @npdoty)
-
Separate device administrators from UA administrators. w3ctag/privacy-principles#368 (3 comments by @jyasskin, @reillyeon)
-
Don't say collective decision-making is strictly superior to engagement with individuals. w3ctag/privacy-principles#363 (3 comments by @darobin, @martinthomson, @npdoty)
-
remove list of privacy labor suggestions around ancillary data w3ctag/privacy-principles#221 (1 comment by @torgo)
w3ctag/design-principles
-
4 issues opened.
-
Duplicate section? w3ctag/design-principles#458, by @jakearchibald.
-
Use of "attribute" confusing/ambiguous w3ctag/design-principles#457, by @jakearchibald.
-
"while a JavaScript event loop is running." is probably not intended w3ctag/design-principles#456, by @jakearchibald.
-
New principle: When introducing heuristics or "magic", also include a way to override them w3ctag/design-principles#455, by @LeaVerou.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
More detail on why events should fire before promises w3ctag/design-principles#460, by @jakearchibald.
-
Fix typo w3ctag/design-principles#459, by @jakearchibald.
-
-
1 pull request merged.
-
Fix typo w3ctag/design-principles#459.
-
-
1 pull request received 3 new comments.
-
More detail on why events should fire before promises w3ctag/design-principles#460 (3 comments by @annevk, @jakearchibald)
-
w3ctag/ethical-web-principles
-
1 issue opened.
-
document title doesn't need to include the standards body name and group name ("W3C TAG") w3ctag/ethical-web-principles#102, by @npdoty.
-
-
1 issue received 1 new comment.
-
The claimed history is inaccurate (and "rose-coloured") w3ctag/ethical-web-principles#100 (1 comment by @masinter)
-
-
1 pull request opened.
-
Purpose: update note about actionable guidance for #37 w3ctag/ethical-web-principles#101, by @rhiaro.
-
-
2 pull requests merged.
-
Purpose: update note about actionable guidance for #37 w3ctag/ethical-web-principles#101.
-
Security & Privacy: make principle imperative, for #75 w3ctag/ethical-web-principles#85.
-
-
1 pull request closed.
-
Purpose: Note link with Design Principles, for #37 w3ctag/ethical-web-principles#84.
-
GitHub
w3ctag/privacy-principles
-
1 issue opened.
-
"respect data rights" principle should apply to API designers too w3ctag/privacy-principles#362, by @pes10k.
-
-
8 issues closed.
-
Concrete examples re: features for responsive design w3ctag/privacy-principles#352.
-
Breadth of consultation w3ctag/privacy-principles#357.
-
Copy edit section B, High-Level Threats w3ctag/privacy-principles#318.
-
Copy edit C-F w3ctag/privacy-principles#319.
-
Header enrichment? w3ctag/privacy-principles#277.
-
Does this really need to talk about supercookies? w3ctag/privacy-principles#276.
-
Document why opt-out/preference registries are a bad idea w3ctag/privacy-principles#272.
-
Wide Review w3ctag/privacy-principles#217.
-
-
13 issues received 13 new comments.
-
Remove vulnerability principle and move the section into (1) w3ctag/privacy-principles#345 (1 comment by @jyasskin)
-
Does this really need to talk about supercookies? w3ctag/privacy-principles#276 (1 comment by @darobin)
-
Document why opt-out/preference registries are a bad idea w3ctag/privacy-principles#272 (1 comment by @darobin)
-
Concrete examples re: features for responsive design w3ctag/privacy-principles#352 (1 comment by @npdoty)
-
More general principle mentioned in section 1.4? w3ctag/privacy-principles#329 (1 comment by @npdoty)
-
Improve comprehensibility of section 1.1.2 Privacy labour w3ctag/privacy-principles#331 (1 comment by @npdoty)
-
"respect data rights" principle should apply to API designers too w3ctag/privacy-principles#362 (1 comment by @jyasskin)
-
3 pull requests opened.
-
Edit section 2.5 w3ctag/privacy-principles#364, by @dmarti.
-
Don't say collective decision-making is strictly superior to engagement with individuals. w3ctag/privacy-principles#363, by @jyasskin.
-
Rewrite ancillary uses to focus on 2 kinds of ancillary APIs rather than ancillary data. w3ctag/privacy-principles#361, by @jyasskin.
-
-
1 pull request merged.
-
Record a target audience for each principle. w3ctag/privacy-principles#355.
-
-
2 pull requests closed.
-
Preview: all copy edits together w3ctag/privacy-principles#321.
-
Rewrite the ancillary data section. w3ctag/privacy-principles#359.
-
-
4 pull requests received 30 new comments.
-
Rewrite ancillary uses to focus on 2 kinds of ancillary APIs rather than ancillary data. w3ctag/privacy-principles#361 (24 comments by @jyasskin, @npdoty, @pes10k, @yoavweiss)
-
Rewrite the ancillary data section. w3ctag/privacy-principles#359 (3 comments by @jyasskin, @pes10k, @yoavweiss)
-
Record a target audience for each principle. w3ctag/privacy-principles#355 (2 comments by @jyasskin)
-
w3ctag/design-reviews
-
7 issues opened.
-
WebCodecs support for AV1 screen content coding tools w3ctag/design-reviews#912, by @fippo.
-
Long Animation Frame API (LoAF) w3ctag/design-reviews#911, by @noamr.
-
Web Printing API w3ctag/design-reviews#910, by @GrapeGreen.
-
Permissions Policy Reporting and Report-Only mode w3ctag/design-reviews#909, by @clelland.
-
View Transitions: list of types w3ctag/design-reviews#908, by @vmpstr.
-
CSS `text-spacing` property and its longhands w3ctag/design-reviews#907, by @kojiishi.
-
Extending Storage Access API (SAA) to non-cookie storage w3ctag/design-reviews#906, by @arichiv.
-
-
16 issues closed.
-
VC-JWT w3ctag/design-reviews#857.
-
RDF Canonicalization w3ctag/design-reviews#855.
-
CSS State Container Queries w3ctag/design-reviews#885.
-
EditContext API w3ctag/design-reviews#416.
-
Standardizing Security Semantics of Cross-Site Cookies w3ctag/design-reviews#904.
-
Shared Storage API w3ctag/design-reviews#747.
-
Borderless mode w3ctag/design-reviews#852.
-
FedCM API extension: Error API, AccountAutoSelectedFlag, HostedDomain and Revocation API w3ctag/design-reviews#893.
-
Specification Review: FetchLater API w3ctag/design-reviews#887.
-
API for capturing all screens w3ctag/design-reviews#856.
-
Multiple Readers and Writers in File System Access API w3ctag/design-reviews#845.
-
Web of Things (WoT) Profile - Review Requested w3ctag/design-reviews#818.
-
ServiceWorker static routing API w3ctag/design-reviews#863.
-
`inverted-colors` CSS Media Query w3ctag/design-reviews#883.
-
`prefers-reduced-transparency` CSS Media Query w3ctag/design-reviews#881.
-
Bluetooth RFCOMM in Web Serial API w3ctag/design-reviews#854.
-
-
1 issue reopened.
-
FedCM multi IDP support w3ctag/design-reviews#803, by @plinss.
-
-
35 issues received 77 new comments.
-
HTMLSelectElement showPicker() w3ctag/design-reviews#900 (7 comments by @cynthia, @LeaVerou, @lukewarlow)
-
CSS `text-spacing` property and its longhands w3ctag/design-reviews#907 (5 comments by @frivoal, @kojiishi, @torgo)
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (5 comments by @alancutter, @LuHuangMSFT, @ylafon)
-
The CSS `word-break: auto-phrase` property w3ctag/design-reviews#891 (5 comments by @frivoal, @kojiishi, @rhiaro, @torgo)
-
Feature detection for supported clipboard formats w3ctag/design-reviews#901 (4 comments by @LeaVerou, @snianu)
-
Web Audio API: User-Selectable Render Quantum Size w3ctag/design-reviews#895 (4 comments by @hoch, @maxpassion, @padenot)
-
Standardizing Security Semantics of Cross-Site Cookies w3ctag/design-reviews#904 (4 comments by @johannhof, @mikewest, @torgo)
-
Spec review for CSS Nesting w3ctag/design-reviews#791 (4 comments by @jensimmons, @plinss, @rhiaro, @tabatkins)
-
Verifiable Credential Status List 2021 w3ctag/design-reviews#874 (3 comments by @cynthia, @hadleybeeman, @mkhraisha)
-
Extending the PointerEvent with Unique DeviceId Attribute w3ctag/design-reviews#880 (2 comments by @sahirv, @torgo)
-
FedCM API extension: Error API, AccountAutoSelectedFlag, HostedDomain and Revocation API w3ctag/design-reviews#893 (2 comments by @hadleybeeman, @yi-gu)
-
`prefers-reduced-transparency` CSS Media Query w3ctag/design-reviews#881 (2 comments by @cookiecrook, @LeaVerou)
-
Tag review request for the "Dubbing and Audio description Profiles of TTML2" w3ctag/design-reviews#897 (1 comment by @ruoxiran)
-
confidence reporting for PerformanceNavigationTiming w3ctag/design-reviews#878 (1 comment by @plinss)
-
Early design review of modal close signals/ModalCloseWatcher w3ctag/design-reviews#594 (1 comment by @slightlyoff)
-
Multiple Readers and Writers in File System Access API w3ctag/design-reviews#845 (1 comment by @cynthia)
-
w3ctag/tracking-issues
-
1 issue opened.
-
CSS `text-spacing` property and its longhands w3ctag/tracking-issues#76, by @w3cbot.
-
w3ctag/design-principles
-
1 issue opened.
-
I18N string best practices vs. design-principles w3ctag/design-principles#454, by @aphillips.
-
-
1 issue closed.
-
Discourage overloading w3ctag/design-principles#131.
-
-
6 issues received 14 new comments.
-
New principle: Discourage polyglot formats w3ctag/design-principles#239 (8 comments by @csarven, @hober, @OR13, @pchampin)
-
I18N string best practices vs. design-principles w3ctag/design-principles#454 (2 comments by @annevk, @LeaVerou)
-
New principle: Text-based syntaxes should be designed to be usable by humans w3ctag/design-principles#453 (1 comment by @aphillips)
-
HTML: Receive complex data via JS or element subtrees? w3ctag/design-principles#348 (1 comment by @LeaVerou)
-
-
2 pull requests closed.
-
Editorial tweaks w3ctag/design-principles#409.
-
Make HTML attribute sections consecutive w3ctag/design-principles#412.
-
-
6 pull requests received 11 new comments.
-
Make 6.1 more inclusive of non-Web JS APIs w3ctag/design-principles#435 (4 comments by @bathos, @cynthia, @LeaVerou)
-
First pass on backwards compatibility principle w3ctag/design-principles#354 (3 comments by @LeaVerou)
-
w3ctag/ethical-web-principles
-
1 issue closed.
-
Add an acknowledgements section w3ctag/ethical-web-principles#96.
-
-
1 pull request merged.
-
Adding Acknowledgement Section w3ctag/ethical-web-principles#99.
-
TR publications
-
3 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
-
W3C TAG Ethical Web Principles published as a Draft Note. History of W3C TAG Ethical Web Principles
-
Past meetings
GitHub
w3ctag/design-reviews
-
15 issues opened.
-
Intersection Observer Scroll Margin w3ctag/design-reviews#905, by @tcaptan-cr.
-
Standardizing Security Semantics of Cross-Site Cookies w3ctag/design-reviews#904, by @johannhof.
-
Side Panel w3ctag/design-reviews#903, by @benjycui.
-
Observable API w3ctag/design-reviews#902, by @domfarolino.
-
Feature detection for supported clipboard formats w3ctag/design-reviews#901, by @snianu.
-
HTMLSelectElement showPicker() w3ctag/design-reviews#900, by @lukewarlow.
-
Securing Verifiable Credentials using JOSE and COSE w3ctag/design-reviews#899, by @awoie.
-
Tag review request for the "Dubbing and Audio description Profiles of TTML2" w3ctag/design-reviews#897, by @cconcolato.
-
Partitioning :visited links history w3ctag/design-reviews#896, by @kyraseevers.
-
Web Audio API: User-Selectable Render Quantum Size w3ctag/design-reviews#895, by @hoch.
-
Relative Color Syntax (RCS) w3ctag/design-reviews#894, by @mysteryDate.
-
FedCM API extension: Error API, AccountAutoSelectedFlag, HostedDomain and Revocation API w3ctag/design-reviews#893, by @yi-gu.
-
DisplayMediaStreamOptions monitorTypeSurfaces w3ctag/design-reviews#892, by @beaufortfrancois.
-
The CSS `word-break: auto-phrase` property w3ctag/design-reviews#891, by @kojiishi.
-
`field-sizing` CSS property w3ctag/design-reviews#890, by @tkent-google.
-
-
2 issues closed.
-
Tag review for Compression Dictionary Transport w3ctag/design-reviews#877.
-
WebRTC Codec selection API w3ctag/design-reviews#836.
-
-
1 issue reopened.
-
HTML Modules w3ctag/design-reviews#334, by @cynthia.
-
-
26 issues received 69 new comments.
-
Relative Color Syntax (RCS) w3ctag/design-reviews#894 (13 comments by @LeaVerou, @miketaylr, @myakura, @mysteryDate, @svgeesus, @ZoeBijl)
-
Specification Review: FetchLater API w3ctag/design-reviews#887 (5 comments by @cynthia, @mingyc, @noamr)
-
Incremental Font Transfer: Patch Subset w3ctag/design-reviews#849 (4 comments by @mnot, @torgo, @vlevantovsky)
-
ServiceWorker static routing API w3ctag/design-reviews#863 (4 comments by @domenic, @kenchris, @torgo)
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875 (3 comments by @alancutter, @LuHuangMSFT, @torgo)
-
Tag review for Compression Dictionary Transport w3ctag/design-reviews#877 (3 comments by @pmeenan, @ylafon)
-
TAG review request for the IDP signin status API w3ctag/design-reviews#884 (3 comments by @cbiesinger, @torgo)
-
HTMLSelectElement showPicker() w3ctag/design-reviews#900 (3 comments by @LeaVerou, @lukewarlow, @miketaylr)
-
Web Authentication: Large Blob extension w3ctag/design-reviews#820 (2 comments by @miketaylr, @spencercap)
-
confidence reporting for PerformanceNavigationTiming w3ctag/design-reviews#878 (2 comments by @mwjacksonmsft, @plinss)
-
-
1 pull request opened.
-
Suggest linking to standards positions w3ctag/design-reviews#898, by @jyasskin.
-
w3ctag/privacy-principles
-
10 issues opened.
-
Copy edit Transparency section w3ctag/privacy-principles#360, by @jyasskin.
-
Movement for an Open Web (MOW) review w3ctag/privacy-principles#358, by @M4AOW.
-
Breadth of consultation w3ctag/privacy-principles#357, by @M4AOW.
-
Draft "website maintainers guide" w3ctag/privacy-principles#354, by @dmarti.
-
Separate device owner and user agent owner w3ctag/privacy-principles#353, by @reillyeon.
-
Concrete examples re: features for responsive design w3ctag/privacy-principles#352, by @eeeps.
-
"should best" and collective privacy w3ctag/privacy-principles#351, by @martinthomson.
-
Compress FIP discussion to half the size w3ctag/privacy-principles#347, by @darobin.
-
Improve definition of automation asymmetry w3ctag/privacy-principles#346, by @darobin.
-
Remove vulnerability principle and move the section into (1) w3ctag/privacy-principles#345, by @jyasskin.
-
-
6 issues closed.
-
principle and additional context on transparency w3ctag/privacy-principles#263.
-
Movement for an Open Web (MOW) review w3ctag/privacy-principles#358.
-
Copy edit beginning of section 1 through 1.1.2 w3ctag/privacy-principles#298.
-
Clarify uses of "self-governing" w3ctag/privacy-principles#233.
-
Copy edit section 2.3, Information Access w3ctag/privacy-principles#304.
-
Copy edit section 2.2, Data Minimization w3ctag/privacy-principles#303.
-
-
2 issues received 2 new comments.
-
7 pull requests opened.
-
Rewrite the ancillary data section. w3ctag/privacy-principles#359, by @jyasskin.
-
Create 2023-09-06-minutes.md w3ctag/privacy-principles#356, by @torgo.
-
Record a target audience for each principle. w3ctag/privacy-principles#355, by @jyasskin.
-
highlight from me w3ctag/privacy-principles#350, by @dmarti.
-
Fave bit from Robin w3ctag/privacy-principles#349, by @darobin.
-
Add breakout slides for people's favorite sections. w3ctag/privacy-principles#348, by @jyasskin.
-
Add TPAC AC meeting slides. w3ctag/privacy-principles#344, by @jyasskin.
-
-
8 pull requests merged.
-
transparency section w3ctag/privacy-principles#288.
-
Add breakout slides for people's favorite sections. w3ctag/privacy-principles#348.
-
highlight from me w3ctag/privacy-principles#350.
-
Fave bit from Robin w3ctag/privacy-principles#349.
-
Add TPAC AC meeting slides. w3ctag/privacy-principles#344.
-
Editorial pass, 1. to 1.1.2 (fixes #298) w3ctag/privacy-principles#334.
-
Editorial: Information Access, fixes #304 w3ctag/privacy-principles#325.
-
Editorial: data minimization, fixes #303. w3ctag/privacy-principles#324.
-
-
6 pull requests received 31 new comments.
-
Editorial pass, 1. to 1.1.2 (fixes #298) w3ctag/privacy-principles#334 (11 comments by @darobin, @jyasskin)
-
Rewrite the ancillary data section. w3ctag/privacy-principles#359 (4 comments by @jyasskin, @npdoty)
-
Editorial: data minimization, fixes #303. w3ctag/privacy-principles#324 (2 comments by @jyasskin, @npdoty)
-
w3ctag/ethical-web-principles
-
1 issue opened.
-
The claimed history is inaccurate (and "rose-coloured") w3ctag/ethical-web-principles#100, by @chaals.
-
-
1 pull request opened.
-
Adding Acknowledgement Section w3ctag/ethical-web-principles#99, by @torgo.
-
w3ctag/design-principles
-
1 issue opened.
-
New principle: Text-based syntaxes should be designed to be usable by humans w3ctag/design-principles#453, 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 @LeaVerou)
-
-
1 pull request opened.
-
fix caps in reference w3ctag/design-principles#452, by @ylafon.
-
-
1 pull request merged.
-
Use consistent casing for payment-request reference. w3ctag/design-principles#449.
-
-
1 pull request closed.
-
fix caps in reference w3ctag/design-principles#452.
-
-
1 pull request received 1 new comment.
GitHub
w3ctag/design-reviews
-
8 issues opened.
-
Allow transferring ArrayBuffer into WebCodecs object constructors w3ctag/design-reviews#889, by @Djuffin.
-
Web Install API - Same Origin w3ctag/design-reviews#888, by @diekus.
-
Specification Review: FetchLater API w3ctag/design-reviews#887, by @mingyc.
-
Document Render-Blocking w3ctag/design-reviews#886, by @khushalsagar.
-
CSS State Container Queries w3ctag/design-reviews#885, by @lilles.
-
TAG review request for the IDP signin status API w3ctag/design-reviews#884, by @cbiesinger.
-
`inverted-colors` CSS Media Query w3ctag/design-reviews#883, by @lukewarlow.
-
`prefers-reduced-transparency` CSS Media Query w3ctag/design-reviews#881, by @lukewarlow.
-
-
15 issues closed.
-
content-visibility: auto forces contain-intrinsic-size: auto w3ctag/design-reviews#876.
-
Moving local files with the File System Access API w3ctag/design-reviews#805.
-
HTTPS Upgrades w3ctag/design-reviews#853.
-
Web Authentication: Large Blob extension w3ctag/design-reviews#820.
-
Compute Pressure Specification Review w3ctag/design-reviews#795.
-
TAG spec review of Bounce Tracking Mitigations w3ctag/design-reviews#862.
-
[FYI] Clear Client Hints via Clear-Site-Data header w3ctag/design-reviews#871.
-
Disabling UA transitions for same-document navigations w3ctag/design-reviews#835.
-
Cross-document View Transitions API w3ctag/design-reviews#851.
-
Exclusive accordion (<details name="">) w3ctag/design-reviews#866.
-
Portable Network Graphics (PNG), Third Edition. w3ctag/design-reviews#873.
-
Early design review: scheduler.yield() w3ctag/design-reviews#827.
-
Early design review: Subresource loading with Web Bundles w3ctag/design-reviews#616.
-
WebDriver BiDi w3ctag/design-reviews#869.
-
WebUSB exclusionFilters option in requestDevice() w3ctag/design-reviews#865.
-
-
1 issue reopened.
-
WebRTC Codec selection API w3ctag/design-reviews#836, by @torgo.
-
-
46 issues received 123 new comments.
-
Incremental Font Transfer: Patch Subset w3ctag/design-reviews#849 (12 comments by @garretrieger, @hober, @litherum, @mnot, @svgeesus, @vlevantovsky)
-
Early design review for the Topics API w3ctag/design-reviews#726 (10 comments by @chrisvls, @dmarti, @hadleybeeman, @jkarlin, @jyasskin, @shivanigithub, @siliconvoodoo)
-
Bluetooth RFCOMM in Web Serial API w3ctag/design-reviews#854 (5 comments by @cynthia, @maxpassion, @scheib, @tomayac)
-
Review request for Protected Audience w3ctag/design-reviews#723 (5 comments by @JensenPaul, @miketaylr, @shivanigithub, @torgo)
-
Web Authentication: Large Blob extension w3ctag/design-reviews#820 (4 comments by @agl, @nsatragno, @plinss, @rhiaro)
-
TAG spec review of Bounce Tracking Mitigations w3ctag/design-reviews#862 (4 comments by @hadleybeeman, @rhiaro, @wanderview)
-
ServiceWorker static routing API w3ctag/design-reviews#863 (3 comments by @domenic, @maxpassion, @yoshisatoyanagisawa)
-
Specification review for fenced frames w3ctag/design-reviews#838 (3 comments by @hadleybeeman, @shivanigithub)
-
Review Request for Attribution Reporting API w3ctag/design-reviews#724 (3 comments by @csharrison, @shivanigithub, @torgo)
-
Multiple Readers and Writers in File System Access API w3ctag/design-reviews#845 (3 comments by @cynthia, @nathanmemmott)
-
deliveryType (Resource Timing) w3ctag/design-reviews#858 (3 comments by @atanassov, @hober, @jeremyroman)
-
Exclusive accordion (<details name="">) w3ctag/design-reviews#866 (3 comments by @atanassov, @hober, @plinss)
-
Web of Things (WoT) Profile - Review Requested w3ctag/design-reviews#818 (3 comments by @mmccool, @rhiaro, @sebastiankb)
-
Moving local files with the File System Access API w3ctag/design-reviews#805 (2 comments by @a-sully, @torgo)
-
Specification review request for Verifiable Credential Data Integrity w3ctag/design-reviews#850 (2 comments by @hadleybeeman, @msporny)
-
Related Website Sets (formerly First-Party Sets) w3ctag/design-reviews#342 (2 comments by @hadleybeeman, @krgovind)
-
content-visibility: auto forces contain-intrinsic-size: auto w3ctag/design-reviews#876 (1 comment by @torgo)
-
TAG review request for the IDP signin status API w3ctag/design-reviews#884 (1 comment by @cbiesinger)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (1 comment by @steimelchrome)
-
Disabling UA transitions for same-document navigations w3ctag/design-reviews#835 (1 comment by @torgo)
-
Early design review: Subresource loading with Web Bundles w3ctag/design-reviews#616 (1 comment by @torgo)
-
w3ctag/design-principles
-
2 issues opened.
-
New principle: The value of HTML boolean attributes doesn't matter w3ctag/design-principles#451, by @LeaVerou.
-
New principle: Consider many & diverse use cases to avoid overfitting w3ctag/design-principles#450, by @LeaVerou.
-
-
1 issue closed.
-
How do we balance concerns between interoperability and implementability? w3ctag/design-principles#142.
-
-
3 issues received 6 new comments.
-
New principle: The value of HTML boolean attributes doesn't matter w3ctag/design-principles#451 (4 comments by @alice, @annevk, @LeaVerou)
-
Several core architectural features of the Web Platform may allow heuristic detectability of assistive technology w3ctag/design-principles#293 (1 comment by @cookiecrook)
-
Advice on JS passing points-in-time or offsets-from-now w3ctag/design-principles#425 (1 comment by @ayuishii)
-
-
1 pull request opened.
-
Use consistent casing for payment-request reference. w3ctag/design-principles#449, by @hober.
-
-
1 pull request merged.
-
New text re: balancing concerns between interoperability and implementability w3ctag/design-principles#290.
-
-
1 pull request received 6 new comments.
-
New text re: balancing concerns between interoperability and implementability w3ctag/design-principles#290 (6 comments by @hober, @torgo)
-
w3ctag/privacy-principles
-
2 issues opened.
-
Match principles with the document's audiences/conformance classes w3ctag/privacy-principles#343, by @jyasskin.
-
Remove High-Level threats appendix w3ctag/privacy-principles#341, by @pes10k.
-
-
5 issues closed.
-
Copy edit section 2.4, Sensitive Information w3ctag/privacy-principles#305.
-
Copy edit section 2.11, Vulnerability w3ctag/privacy-principles#312.
-
Copy edit section 2.10, Unwanted Information w3ctag/privacy-principles#311.
-
Copy edit section 2.9, Harassment w3ctag/privacy-principles#310.
-
"low-enough granularity" geolocation is naive w3ctag/privacy-principles#281.
-
-
1 issue received 1 new comment.
-
"low-enough granularity" geolocation is naive w3ctag/privacy-principles#281 (1 comment by @jyasskin)
-
-
3 pull requests opened.
-
Add TPAC breakout information. w3ctag/privacy-principles#342, by @jyasskin.
-
move list of recognition techniques to a new doc w3ctag/privacy-principles#340, by @pes10k.
-
Cite RFC6772 w3ctag/privacy-principles#339, by @npdoty.
-
-
5 pull requests merged.
-
Add TPAC breakout information. w3ctag/privacy-principles#342.
-
Editorial for Sensitive Information and Vulnerability w3ctag/privacy-principles#326.
-
Harrasment, for #310 and #311 w3ctag/privacy-principles#328.
-
move list of recognition techniques to a new doc w3ctag/privacy-principles#340.
-
Cite RFC6772 w3ctag/privacy-principles#339.
-
-
7 pull requests received 46 new comments.
-
Editorial: data minimization, fixes #303. w3ctag/privacy-principles#324 (3 comments by @npdoty, @torgo)
-
Editorial for Sensitive Information and Vulnerability w3ctag/privacy-principles#326 (1 comment by @jyasskin)
-
move list of recognition techniques to a new doc w3ctag/privacy-principles#340 (1 comment by @pes10k)
w3ctag/process
-
2 issues opened.
-
Add "terms of art?" question to the issue template w3ctag/process#32, by @torgo.
-
Maybe deprecate "leaving issues in other repos" from our design review template w3ctag/process#31, by @torgo.
-
-
1 issue received 2 new comments.
-
Maybe deprecate "leaving issues in other repos" from our design review template w3ctag/process#31 (2 comments by @LeaVerou, @torgo)
-
w3ctag/ethical-web-principles
-
2 issues opened.
-
URL not rendering; missing 'to'? w3ctag/ethical-web-principles#98, by @jbradleychen.
-
How we use "source" w3ctag/ethical-web-principles#97, by @hadleybeeman.
-
-
3 issues closed.
-
How we use "source" w3ctag/ethical-web-principles#97.
-
clarify status of document w3ctag/ethical-web-principles#57.
-
Strengthen transparency principle? w3ctag/ethical-web-principles#60.
-
-
2 issues received 9 new comments.
-
Document should discourage features that'd lead to a more centralized web w3ctag/ethical-web-principles#94 (8 comments by @hadleybeeman, @mnot, @pes10k)
-
-
1 pull request merged.
-
Revise information integrity goals w3ctag/ethical-web-principles#93.
-
-
1 pull request closed.
-
add centralization-is-bad section w3ctag/ethical-web-principles#95.
-
-
4 pull requests received 19 new comments.
-
Revise information integrity goals w3ctag/ethical-web-principles#93 (16 comments by @hadleybeeman, @jyasskin, @rhiaro, @torgo)
-
Security & Privacy: make principle imperative, for #75 w3ctag/ethical-web-principles#85 (1 comment by @rhiaro)
-
Purpose: Note link with Design Principles, for #37 w3ctag/ethical-web-principles#84 (1 comment by @torgo)
-
w3ctag/explainer-explainer
-
1 issue opened.
-
Explainer template needs to make it clear you don't need to fill out everything for every review w3ctag/explainer-explainer#12, by @torgo.
-
w3ctag/caching-bundling-sustainability
-
6 issues opened.
-
Include security and privacy issues addressed by partitioned caching w3ctag/caching-bundling-sustainability#8, by @arturjanc.
-
User identifiers in caches w3ctag/caching-bundling-sustainability#7, by @michaelkleber.
-
Mention QUIC? w3ctag/caching-bundling-sustainability#5, by @plinss.
-
Don't throw the baby out with the bathwater w3ctag/caching-bundling-sustainability#4, by @plinss.
-
Section 3 - bandwidth costs w3ctag/caching-bundling-sustainability#3, by @plinss.
-
Missing text w3ctag/caching-bundling-sustainability#2, by @hober.
-
-
2 issues received 2 new comments.
-
When cache partitioning was introduced w3ctag/caching-bundling-sustainability#1 (1 comment by @miketaylr)
-
-
1 pull request opened.
-
Fix github links w3ctag/caching-bundling-sustainability#6, by @michaelkleber.
-
w3ctag/bfcache-guide
-
1 pull request received 1 new comment.
GitHub
w3ctag/caching-bundling-sustainability
-
1 issue opened.
-
When cache partitioning was introduced w3ctag/caching-bundling-sustainability#1, by @hober.
-
w3ctag/design-reviews
-
12 issues opened.
-
Extending the PointerEvent with Unique DeviceId Attribute w3ctag/design-reviews#880, by @sahirv.
-
Soft Navigations w3ctag/design-reviews#879, by @yoavweiss.
-
confidence reporting for PerformanceNavigationTiming w3ctag/design-reviews#878, by @mwjacksonmsft.
-
Tag review for Compression Dictionary Transport w3ctag/design-reviews#877, by @pmeenan.
-
content-visibility: auto forces contain-intrinsic-size: auto w3ctag/design-reviews#876, by @vmpstr.
-
TAG review for web app `scope_extensions` w3ctag/design-reviews#875, by @diekus.
-
Verifiable Credential Status List 2021 w3ctag/design-reviews#874, by @mkhraisha.
-
Portable Network Graphics (PNG), Third Edition. w3ctag/design-reviews#873, by @svgeesus.
-
Captured Mouse Events w3ctag/design-reviews#872, by @eladalon1983.
-
[FYI] Clear Client Hints via Clear-Site-Data header w3ctag/design-reviews#871, by @arichiv.
-
WebDriver BiDi w3ctag/design-reviews#869, by @mathiasbynens.
-
-
4 issues closed.
-
Detect UA Transitions on Same-Document Navigations w3ctag/design-reviews#834.
-
WebRTC-SVC (Scalable Video Coding) w3ctag/design-reviews#837.
-
oi w3ctag/design-reviews#870.
-
Sync Methods for FileSystemSyncAccessHandle in File System Access API w3ctag/design-reviews#772.
-
-
27 issues received 84 new comments.
-
Cross-document View Transitions API w3ctag/design-reviews#851 (8 comments by @khushalsagar, @LeaVerou, @noamr)
-
Specification review for fenced frames w3ctag/design-reviews#838 (8 comments by @domfarolino, @rhiaro, @torgo)
-
Eligibility for autofill w3ctag/design-reviews#831 (7 comments by @ianbjacobs, @stephenmcgruer, @torgo)
-
Specification review for CSS Anchor Positioning w3ctag/design-reviews#848 (6 comments by @LeaVerou, @plinss, @tabatkins)
-
navigateEvent.sourceElement w3ctag/design-reviews#867 (6 comments by @domenic, @LeaVerou, @letitz, @natechapin, @torgo)
-
Moving local files with the File System Access API w3ctag/design-reviews#805 (4 comments by @a-sully, @torgo)
-
WebRTC-SVC (Scalable Video Coding) w3ctag/design-reviews#837 (4 comments by @dontcallmedom, @hober, @torgo)
-
[FYI] Clear Client Hints via Clear-Site-Data header w3ctag/design-reviews#871 (3 comments by @arichiv, @torgo)
-
early design review: Permissions-Policy: unload w3ctag/design-reviews#738 (3 comments by @cynthia, @fergald, @torgo)
-
early design review: bfcache/prerendering eviction APIs w3ctag/design-reviews#786 (2 comments by @cynthia, @torgo)
-
Early design review: Subresource loading with Web Bundles w3ctag/design-reviews#616 (2 comments by @KenjiBaheux, @torgo)
-
Detect UA Transitions on Same-Document Navigations w3ctag/design-reviews#834 (2 comments by @hober, @torgo)
-
Disabling UA transitions for same-document navigations w3ctag/design-reviews#835 (2 comments by @khushalsagar, @torgo)
-
Extending the PointerEvent with Unique DeviceId Attribute w3ctag/design-reviews#880 (1 comment by @sahirv)
-
VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport w3ctag/design-reviews#768 (1 comment by @torgo)
-
Sync Methods for FileSystemSyncAccessHandle in File System Access API w3ctag/design-reviews#772 (1 comment by @plinss)
-
w3ctag/design-principles
-
1 issue closed.
-
"Cheat sheet" for reference during design reviews? w3ctag/design-principles#154.
-
-
3 issues received 5 new comments.
-
"Cheat sheet" for reference during design reviews? w3ctag/design-principles#154 (1 comment by @plinss)
-
New principle: Document whether to add things to Document, Navigator, Window, or SomeOtherInterface w3ctag/design-principles#448 (1 comment by @LeaVerou)
w3ctag/bfcache-guide
-
1 pull request received 1 new comment.
w3ctag/ethical-web-principles
-
1 issue opened.
-
Add an acknowledgements section w3ctag/ethical-web-principles#96, by @torgo.
-
-
1 pull request received 5 new comments.
w3ctag/privacy-principles
-
6 issues opened.
-
Editors should make sure we are consistent in marking up examples as such w3ctag/privacy-principles#335, by @darobin.
-
Explain more about collective governance of privacy (GKC) w3ctag/privacy-principles#333, by @darobin.
-
Explain more about why privacy is essentially contested w3ctag/privacy-principles#332, by @darobin.
-
Improve comprehensibility of section 1.1.2 Privacy labour w3ctag/privacy-principles#331, by @polcak.
-
Add a definition for "abuse" w3ctag/privacy-principles#330, by @rhiaro.
-
More general principle mentioned in section 1.4? w3ctag/privacy-principles#329, by @tidoust.
-
-
10 issues closed.
-
What are "k-anonymity attacks"? w3ctag/privacy-principles#284.
-
De-identification is no good w3ctag/privacy-principles#285.
-
Why does sensitive data not include identifiers? w3ctag/privacy-principles#282.
-
How can information be "revoked"? w3ctag/privacy-principles#283.
-
Is it "e.g." or "eg."? w3ctag/privacy-principles#278.
-
Don't claim general actions override specific ones w3ctag/privacy-principles#231.
-
refined example about privacy of small groups w3ctag/privacy-principles#251.
-
Copy edit section 2.8 Device Owners and Administrators w3ctag/privacy-principles#309.
-
Copy edit beginning of section 2 through 2.1 w3ctag/privacy-principles#302.
-
Don't ask for fake consent, even if real consent is not required w3ctag/privacy-principles#192.
-
-
5 issues received 8 new comments.
-
Try using the privacy principles to analyze the Environment Integrity API proposal w3ctag/privacy-principles#271 (3 comments by @domfarolino, @jyasskin)
-
-
13 pull requests opened.
-
Add identifiers to sensitive data list w3ctag/privacy-principles#338, by @torgo.
-
Remove ", notably against timing or k-anonymity attacks." text, fixes issue #285 w3ctag/privacy-principles#337, by @pes10k.
-
Remove unclear point about revoking information w3ctag/privacy-principles#336, by @darobin.
-
Editorial pass, 1. to 1.1.2 (fixes #298) w3ctag/privacy-principles#334, by @darobin.
-
Harrasment, for #310 and #311 w3ctag/privacy-principles#328, by @rhiaro.
-
Editorial: Device Owners and Administrators, fixes #309. w3ctag/privacy-principles#327, by @rhiaro.
-
Editorial for Sensitive Information and Vulnerability w3ctag/privacy-principles#326, by @rhiaro.
-
Editorial: Information Access, fixes #304 w3ctag/privacy-principles#325, by @rhiaro.
-
Editorial: data minimization, fixes #303. w3ctag/privacy-principles#324, by @rhiaro.
-
302 edit identity w3ctag/privacy-principles#323, by @rhiaro.
-
Copy edit Section 2 intro, fixes #302. w3ctag/privacy-principles#322, by @rhiaro.
-
Preview: all copy edits together w3ctag/privacy-principles#321, by @rhiaro.
-
Adjust "bp-summary" title in table of contents too w3ctag/privacy-principles#320, by @tidoust.
-
-
10 pull requests merged.
-
Remove ", notably against timing or k-anonymity attacks." text, fixes issue #285 w3ctag/privacy-principles#337.
-
Add identifiers to sensitive data list w3ctag/privacy-principles#338.
-
Remove unclear point about revoking information w3ctag/privacy-principles#336.
-
Revisit global opt out, fix #231 w3ctag/privacy-principles#296.
-
potential small group privacy examples w3ctag/privacy-principles#289.
-
Editorial: Device Owners and Administrators, fixes #309. w3ctag/privacy-principles#327.
-
302 edit identity w3ctag/privacy-principles#323.
-
Copy edit Section 2 intro, fixes #302. w3ctag/privacy-principles#322.
-
Principle on fake consent w3ctag/privacy-principles#290.
-
Adjust "bp-summary" title in table of contents too w3ctag/privacy-principles#320.
-
-
2 pull requests closed.
-
change wording around self-governing w3ctag/privacy-principles#291.
-
Remove the statement about a general opt-out overriding a specific opt-in. w3ctag/privacy-principles#238.
-
-
12 pull requests received 115 new comments.
-
Editorial: Information Access, fixes #304 w3ctag/privacy-principles#325 (30 comments by @chrisn, @hober, @jyasskin, @npdoty, @rhiaro, @yoavweiss)
-
Harrasment, for #310 and #311 w3ctag/privacy-principles#328 (16 comments by @jyasskin, @npdoty, @rhiaro, @tidoust)
-
Editorial: Device Owners and Administrators, fixes #309. w3ctag/privacy-principles#327 (5 comments by @hober)
-
Copy edit Section 2 intro, fixes #302. w3ctag/privacy-principles#322 (4 comments by @jyasskin, @rhiaro)
-
Remove the statement about a general opt-out overriding a specific opt-in. w3ctag/privacy-principles#238 (1 comment by @jyasskin)
-
Adjust "bp-summary" title in table of contents too w3ctag/privacy-principles#320 (1 comment by @darobin)
-
w3ctag/tag.w3.org
-
2 pull requests opened.
-
Ask people to list non-consensus dependencies in their explainers. w3ctag/tag.w3.org#40, by @jyasskin.
-
Revision to explainer explainer w3ctag/tag.w3.org#39, by @torgo.
-
-
2 pull requests received 27 new comments.
-
Revision to explainer explainer w3ctag/tag.w3.org#39 (20 comments by @alice, @chrishtr, @LeaVerou, @torgo)
-
Ask people to list non-consensus dependencies in their explainers. w3ctag/tag.w3.org#40 (7 comments by @cynthia, @hober, @jyasskin, @LeaVerou)
-
w3ctag/tracking-issues
-
2 issues opened.
-
remove securing json w3ctag/tracking-issues#75, by @w3cbot.
-
Add an explainer w3ctag/tracking-issues#74, by @w3cbot.
-
w3ctag/explainer-explainer
-
1 issue received 1 new comment.
GitHub
w3ctag/privacy-principles
-
33 issues opened.
-
Copy edit C-F w3ctag/privacy-principles#319, by @dmarti.
-
Copy edit section B, High-Level Threats w3ctag/privacy-principles#318, by @dmarti.
-
Copy edit section A, Common Concepts w3ctag/privacy-principles#317, by @dmarti.
-
Copy edit section 2.15, Support Choosing Which Information to Present w3ctag/privacy-principles#316, by @dmarti.
-
Copy edit section 2.14, Non-Retaliation w3ctag/privacy-principles#315, by @dmarti.
-
Copy edit section 2.13, Notifications and Interruptions w3ctag/privacy-principles#314, by @dmarti.
-
Copy edit section 2.12, Consent, Withdrawal of Consent, Opt-Outs, and Objections w3ctag/privacy-principles#313, by @dmarti.
-
Copy edit section 2.11, Vulnerability w3ctag/privacy-principles#312, by @dmarti.
-
Copy edit section 2.10, Unwanted Information w3ctag/privacy-principles#311, by @dmarti.
-
Copy edit section 2.9, Harassment w3ctag/privacy-principles#310, by @dmarti.
-
Copy edit section 2.8 Device Owners and Administrators w3ctag/privacy-principles#309, by @dmarti.
-
Copy edit section 2.7, Collective Privacy w3ctag/privacy-principles#308, by @dmarti.
-
Copy edit section 2.6, De-identified Data w3ctag/privacy-principles#307, by @dmarti.
-
Copy edit section 2.5, Data Rights w3ctag/privacy-principles#306, by @dmarti.
-
Copy edit section 2.4, Sensitive Information w3ctag/privacy-principles#305, by @dmarti.
-
Copy edit section 2.3, Information Access w3ctag/privacy-principles#304, by @dmarti.
-
Copy edit section 2.2, Data Minimization w3ctag/privacy-principles#303, by @dmarti.
-
Copy edit beginning of section 2 through 2.1 w3ctag/privacy-principles#302, by @dmarti.
-
Copy edit section 1.4, Incorporating Different Privacy Principles w3ctag/privacy-principles#301, by @dmarti.
-
Copy edit section 1.3, User Agents w3ctag/privacy-principles#300, by @dmarti.
-
Copy edit section 1.2, Collective Governance w3ctag/privacy-principles#299, by @dmarti.
-
Copy edit beginning of section 1 through 1.1.2 w3ctag/privacy-principles#298, by @dmarti.
-
Copy edit material before section 1 w3ctag/privacy-principles#297, by @dmarti.
-
De-identification is no good w3ctag/privacy-principles#285, by @martinthomson.
-
What are "k-anonymity attacks"? w3ctag/privacy-principles#284, by @martinthomson.
-
How can information be "revoked"? w3ctag/privacy-principles#283, by @martinthomson.
-
Why does sensitive data not include identifiers? w3ctag/privacy-principles#282, by @martinthomson.
-
"low-enough granularity" geolocation is naive w3ctag/privacy-principles#281, by @martinthomson.
-
Making undesirable information hard to access w3ctag/privacy-principles#280, by @martinthomson.
-
What information access is being removed? w3ctag/privacy-principles#279, by @martinthomson.
-
Is it "e.g." or "eg."? w3ctag/privacy-principles#278, by @martinthomson.
-
Header enrichment? w3ctag/privacy-principles#277, by @martinthomson.
-
Does this really need to talk about supercookies? w3ctag/privacy-principles#276, by @martinthomson.
-
-
4 issues closed.
-
Discuss multi-party consent w3ctag/privacy-principles#24.
-
privacy principles related to purpose-specific APIs w3ctag/privacy-principles#175.
-
Be more explicit about PII-based joins across contexts being bad. w3ctag/privacy-principles#194.
-
Clarify "party that controls this origin or site" to cover the control of data w3ctag/privacy-principles#152.
-
-
10 issues received 14 new comments.
-
privacy principles related to purpose-specific APIs w3ctag/privacy-principles#175 (2 comments by @npdoty, @torgo)
-
Clarify "party that controls this origin or site" to cover the control of data w3ctag/privacy-principles#152 (2 comments by @jyasskin, @torgo)
-
"low-enough granularity" geolocation is naive w3ctag/privacy-principles#281 (1 comment by @jyasskin)
-
Centralization risks of noise as a mitigation tool w3ctag/privacy-principles#261 (1 comment by @npdoty)
-
Don't ask for fake consent, even if real consent is not required w3ctag/privacy-principles#192 (1 comment by @jyasskin)
-
Be more explicit about PII-based joins across contexts being bad. w3ctag/privacy-principles#194 (1 comment by @torgo)
-
13 pull requests opened.
-
Revisit global opt out, fix #231 w3ctag/privacy-principles#296, by @darobin.
-
Encourage purpose-built APIs, fix #175 w3ctag/privacy-principles#295, by @darobin.
-
Registries are bad, fix #272 w3ctag/privacy-principles#294, by @darobin.
-
Add centralization section, addresses #261 w3ctag/privacy-principles#293, by @pes10k.
-
Exemplify good style, fix #278 w3ctag/privacy-principles#292, by @darobin.
-
change wording around self-governing w3ctag/privacy-principles#291, by @torgo.
-
Principle on fake consent w3ctag/privacy-principles#290, by @dmarti.
-
potential small group privacy examples w3ctag/privacy-principles#289, by @npdoty.
-
transparency section w3ctag/privacy-principles#288, by @npdoty.
-
principle for non-user privacy, to be able to access and remove data uploaded by others w3ctag/privacy-principles#287, by @npdoty.
-
Grammar fix w3ctag/privacy-principles#286, by @martinthomson.
-
No excuses for fingerprinting w3ctag/privacy-principles#275, by @martinthomson.
-
Fingerprinting requires that attributes be aggregated w3ctag/privacy-principles#274, by @martinthomson.
-
-
7 pull requests merged.
-
principle for non-user privacy, to be able to access and remove data uploaded by others w3ctag/privacy-principles#287.
-
Encourage purpose-built APIs, fix #175 w3ctag/privacy-principles#295.
-
Registries are bad, fix #272 w3ctag/privacy-principles#294.
-
Exemplify good style, fix #278 w3ctag/privacy-principles#292.
-
Fingerprinting requires that attributes be aggregated w3ctag/privacy-principles#274.
-
No excuses for fingerprinting w3ctag/privacy-principles#275.
-
Grammar fix w3ctag/privacy-principles#286.
-
-
1 pull request closed.
-
Add centralization section, addresses #261 w3ctag/privacy-principles#293.
-
-
7 pull requests received 21 new comments.
-
principle for non-user privacy, to be able to access and remove data uploaded by others w3ctag/privacy-principles#287 (5 comments by @darobin)
-
Revisit global opt out, fix #231 w3ctag/privacy-principles#296 (4 comments by @darobin, @michaelkleber)
-
No excuses for fingerprinting w3ctag/privacy-principles#275 (3 comments by @jyasskin, @martinthomson, @npdoty)
-
w3ctag/design-reviews
-
16 issues opened.
-
The `FileSystemObserver` interface w3ctag/design-reviews#868, by @a-sully.
-
navigateEvent.sourceElement w3ctag/design-reviews#867, by @natechapin.
-
Exclusive accordion (<details name="">) w3ctag/design-reviews#866, by @dbaron.
-
WebUSB exclusionFilters option in requestDevice() w3ctag/design-reviews#865, by @beaufortfrancois.
-
text-wrap: pretty w3ctag/design-reviews#864, by @kojiishi.
-
ServiceWorker static routing API w3ctag/design-reviews#863, by @yoshisatoyanagisawa.
-
TAG spec review of Bounce Tracking Mitigations w3ctag/design-reviews#862, by @amaliev.
-
Verifiable Credentials Data Model v2.0 w3ctag/design-reviews#860, by @awoie.
-
VC JSON Schema w3ctag/design-reviews#859, by @thereisnogabe.
-
deliveryType (Resource Timing) w3ctag/design-reviews#858, by @jeremyroman.
-
API for capturing all screens w3ctag/design-reviews#856, by @shangl.
-
RDF Canonicalization w3ctag/design-reviews#855, by @philarcher.
-
Bluetooth RFCOMM in Web Serial API w3ctag/design-reviews#854, by @nondebug.
-
HTTPS Upgrades w3ctag/design-reviews#853, by @christhompson.
-
Borderless mode w3ctag/design-reviews#852, by @sonkkeli.
-
-
4 issues closed.
-
FedCM Auto Re-authentication API w3ctag/design-reviews#813.
-
WebAssembly Garbage Collection extensions w3ctag/design-reviews#814.
-
[FYI] Report Critical-CH caused restart in NavigationTiming w3ctag/design-reviews#833.
-
Review of DPUB-ARIA 1.1 and DPUB-AAM 1.1 w3ctag/design-reviews#821.
-
-
1 issue reopened.
-
EditContext API w3ctag/design-reviews#416, by @chrishtr.
-
-
21 issues received 45 new comments.
-
Early design review for the Topics API w3ctag/design-reviews#726 (9 comments by @atanassov, @cynthia, @jkarlin, @martinthomson, @michaelkleber, @nightpool, @plinss, @RByers)
-
Entry and Exit Animations w3ctag/design-reviews#829 (6 comments by @flackr, @LeaVerou, @lilles, @nt1m)
-
Review of DPUB-ARIA 1.1 and DPUB-AAM 1.1 w3ctag/design-reviews#821 (4 comments by @daniel-montalvo, @mattgarrish, @rhiaro)
-
early design review: Permissions-Policy: unload w3ctag/design-reviews#738 (3 comments by @fergald, @torgo)
-
Moving local files with the File System Access API w3ctag/design-reviews#805 (2 comments by @a-sully)
-
[FYI] Report Critical-CH caused restart in NavigationTiming w3ctag/design-reviews#833 (1 comment by @cynthia)
-
Multiple Readers and Writers in File System Access API w3ctag/design-reviews#845 (1 comment by @fergald)
-
w3ctag/ethical-web-principles
-
1 issue opened.
-
Document should discourage features that'd lead to a more centralized web w3ctag/ethical-web-principles#94, by @pes10k.
-
-
1 pull request opened.
-
add centralization-is-bad section w3ctag/ethical-web-principles#95, by @pes10k.
-
-
1 pull request received 5 new comments.
-
add centralization-is-bad section w3ctag/ethical-web-principles#95 (5 comments by @chrisn, @jyasskin, @mnot)
-
w3ctag/design-principles
-
2 issues opened.
-
New principle: Document whether to add things to Document, Navigator, Window, or SomeOtherInterface w3ctag/design-principles#448, by @jyasskin.
-
New principle: CSS color functions should always accept `<number>` as well for each numerical component w3ctag/design-principles#447, by @LeaVerou.
-
-
1 issue closed.
-
Request for design principle clarification: Warn explicitly against getters throwing exceptions w3ctag/design-principles#400.
-
-
4 issues received 14 new comments.
-
WebIDL interfaces should only be used when you have both data and behavior w3ctag/design-principles#11 (7 comments by @bathos, @domenic, @LeaVerou, @ljharb)
-
New principle: Avoid adding (non-constructor) functions to the global scope w3ctag/design-principles#426 (4 comments by @annevk, @bathos, @LeaVerou, @ljharb)
-
Is `partial` a long term maintainability problem? If so, how do we fix it? w3ctag/design-principles#99 (2 comments by @alvestrand, @annevk)
-
New principle: Document whether to add things to Document, Navigator, Window, or SomeOtherInterface w3ctag/design-principles#448 (1 comment by @bathos)
-
-
3 pull requests merged.
-
Give more guidance about how to monkeypatch well. w3ctag/design-principles#441.
-
Warn against getter throwing exception since it is a side effect w3ctag/design-principles#408.
-
Fix link to live-vs-static w3ctag/design-principles#439.
-
-
1 pull request closed.
-
First pass at #11, lots of TBDs w3ctag/design-principles#403.
-
-
4 pull requests received 8 new comments.
-
Give more guidance about how to monkeypatch well. w3ctag/design-principles#441 (5 comments by @bathos, @jyasskin, @LeaVerou)
-
New text re: balancing concerns between interoperability and implementability w3ctag/design-principles#290 (1 comment by @hober)
-
w3ctag/societal-impact-questionnaire
-
2 issues opened.
-
centralization w3ctag/societal-impact-questionnaire#11, by @torgo.
-
Make it clear this does not assume context of a web browser somehow w3ctag/societal-impact-questionnaire#10, by @torgo.
-
-
1 issue closed.
-
Consider encouraging investment in evidence over speculation w3ctag/societal-impact-questionnaire#7.
-
-
2 issues received 2 new comments.
-
Consider encouraging investment in evidence over speculation w3ctag/societal-impact-questionnaire#7 (1 comment by @torgo)
w3ctag/tracking-issues
-
3 issues opened.
-
remove securing json w3ctag/tracking-issues#73, by @w3cbot.
-
Add an explainer w3ctag/tracking-issues#72, by @w3cbot.
-
Privacy Working Group w3ctag/tracking-issues#71, by @w3cbot.
-
GitHub
w3ctag/design-reviews
-
10 issues opened.
-
Cross-document View Transitions API w3ctag/design-reviews#851, by @noamr.
-
Specification review request for Verifiable Credential Data Integrity w3ctag/design-reviews#850, by @msporny.
-
Incremental Font Transfer: Patch Subset w3ctag/design-reviews#849, by @svgeesus.
-
Specification review for CSS Anchor Positioning w3ctag/design-reviews#848, by @xiaochengh.
-
Private Aggregation API w3ctag/design-reviews#846, by @alexmturner.
-
Multiple Readers and Writers in File System Access API w3ctag/design-reviews#845, by @dslee414.
-
Web Audio API: RenderCapacity API w3ctag/design-reviews#843, by @hoch.
-
Isolated Web Apps w3ctag/design-reviews#842, by @reillyeon.
-
Tabbed web apps w3ctag/design-reviews#841, by @loubrett.
-
Fullscreen Popup Windows w3ctag/design-reviews#840, by @bradtriebwasser.
-
-
4 issues closed.
-
Element.checkVisibility review w3ctag/design-reviews#734.
-
Spec review for Scroll-driven Animations w3ctag/design-reviews#828.
-
Design Review: Speculation Rules (Prefetch) w3ctag/design-reviews#721.
-
Review of IMSC-HRM w3ctag/design-reviews#788.
-
-
22 issues received 32 new comments.
-
Web of Things (WoT) Profile - Review Requested w3ctag/design-reviews#818 (3 comments by @benfrancis, @hadleybeeman, @plinss)
-
Incremental Font Transfer: Patch Subset w3ctag/design-reviews#849 (2 comments by @garretrieger, @mnot)
-
WebAssembly Garbage Collection extensions w3ctag/design-reviews#814 (2 comments by @ajklein, @torgo)
-
Sync Methods for FileSystemSyncAccessHandle in File System Access API w3ctag/design-reviews#772 (2 comments by @a-sully, @hober)
-
Design Review: Speculation Rules (Prefetch) w3ctag/design-reviews#721 (2 comments by @atanassov, @LeaVerou)
-
VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport w3ctag/design-reviews#768 (1 comment by @hadleybeeman)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (1 comment by @steimelchrome)
-
1 pull request opened.
-
Add examples of stakeholders to issue template w3ctag/design-reviews#844, by @torgo.
-
w3ctag/design-principles
-
4 issues opened.
-
New principle: When dictionary members should be nullable w3ctag/design-principles#446, by @jyasskin.
-
Should conceptually ordered enums still be strings? w3ctag/design-principles#443, by @LeaVerou.
-
New principle: Distance between data w3ctag/design-principles#442, by @plinss.
-
New principle: separating fast code paths from safe ones w3ctag/design-principles#438, by @DerekNonGeneric.
-
-
6 issues received 8 new comments.
-
Time unit recommendations and the TC39 Temporal proposal w3ctag/design-principles#101 (2 comments by @jyasskin, @ptomato)
-
New principle: separating fast code paths from safe ones w3ctag/design-principles#438 (2 comments by @annevk, @DerekNonGeneric)
-
New principle: When dictionary members should be nullable w3ctag/design-principles#446 (1 comment by @annevk)
-
New principle: Avoid exposing API that result in synchronous flushing of CSS or layout w3ctag/design-principles#388 (1 comment by @plinss)
-
Should conceptually ordered enums still be strings? w3ctag/design-principles#443 (1 comment by @annevk)
-
-
3 pull requests opened.
-
Give more guidance about how to monkeypatch well. w3ctag/design-principles#441, by @jyasskin.
-
Remove trailing whitespace. w3ctag/design-principles#440, by @jyasskin.
-
Fix link to live-vs-static w3ctag/design-principles#439, by @jan-ivar.
-
-
1 pull request merged.
-
Remove trailing whitespace. w3ctag/design-principles#440.
-
-
2 pull requests received 29 new comments.
-
Give more guidance about how to monkeypatch well. w3ctag/design-principles#441 (28 comments by @annevk, @dbaron, @domenic, @fantasai, @jyasskin, @LeaVerou, @littledan, @ljharb)
-
w3ctag/privacy-principles
-
4 issues opened.
-
Discuss privacy-labor in the processing section w3ctag/privacy-principles#273, by @pes10k.
-
Document why opt-out/preference registries are a bad idea w3ctag/privacy-principles#272, by @darobin.
-
Try using the privacy principles to analyze the Environment Integrity API proposal w3ctag/privacy-principles#271, by @jyasskin.
-
principle and additional context on transparency w3ctag/privacy-principles#263, by @npdoty.
-
-
7 issues closed.
-
Sharing identity and reading history aren't purposes w3ctag/privacy-principles#229.
-
Separating identity from identifiers or information linked with identifiers w3ctag/privacy-principles#226.
-
Align our Duty of Loyalty with Richards/Hartzog's w3ctag/privacy-principles#241.
-
We <dfn> "principle" with a different meaning than we're using in the title of the document w3ctag/privacy-principles#260.
-
People's Agents w3ctag/privacy-principles#255.
-
Feedback on section 1.4 "Incorporating Different Privacy Principles" w3ctag/privacy-principles#256.
-
Suggestions on Introduction w3ctag/privacy-principles#253.
-
-
6 issues received 8 new comments.
-
Feedback on section 1.4 "Incorporating Different Privacy Principles" w3ctag/privacy-principles#256 (3 comments by @chrisn, @jyasskin, @torgo)
-
Sharing identity and reading history aren't purposes w3ctag/privacy-principles#229 (1 comment by @jyasskin)
-
Separating identity from identifiers or information linked with identifiers w3ctag/privacy-principles#226 (1 comment by @darobin)
-
Centralization risks of noise as a mitigation tool w3ctag/privacy-principles#261 (1 comment by @npdoty)
-
-
7 pull requests opened.
-
Clarifying identity vs legal identity w3ctag/privacy-principles#270, by @darobin.
-
Make it clearer that disloyalty must be detrimental to people w3ctag/privacy-principles#269, by @darobin.
-
Simplify "To facilitate site understanding of user preferences" w3ctag/privacy-principles#268, by @jyasskin.
-
chrisn's tweaks to the introduction w3ctag/privacy-principles#267, by @jyasskin.
-
Tweaks to the Incorporating section w3ctag/privacy-principles#266, by @jyasskin.
-
s/People's Agents/User Agents/, and tweak a sentence in that section. w3ctag/privacy-principles#265, by @jyasskin.
-
Avoid defining "principles" with a different meaning than in the title of the document. w3ctag/privacy-principles#264, by @jyasskin.
-
-
9 pull requests merged.
-
Clarifying identity vs legal identity w3ctag/privacy-principles#270.
-
Make it clearer that disloyalty must be detrimental to people w3ctag/privacy-principles#269.
-
Processing is sensitive, not purposes w3ctag/privacy-principles#242.
-
Avoid defining "principles" with a different meaning than in the title of the document. w3ctag/privacy-principles#264.
-
s/People's Agents/User Agents/, and tweak a sentence in that section. w3ctag/privacy-principles#265.
-
Tweaks to the Incorporating section w3ctag/privacy-principles#266.
-
chrisn's tweaks to the introduction w3ctag/privacy-principles#267.
-
Simplify "To facilitate site understanding of user preferences" w3ctag/privacy-principles#268.
-
Restructure introduction sections w3ctag/privacy-principles#262.
-
-
1 pull request closed.
-
Start making the opt in/out section consistently talk about purposes. w3ctag/privacy-principles#236.
-
-
7 pull requests received 33 new comments.
-
Clarifying identity vs legal identity w3ctag/privacy-principles#270 (8 comments by @darobin, @jyasskin, @torgo)
-
Make it clearer that disloyalty must be detrimental to people w3ctag/privacy-principles#269 (7 comments by @darobin, @jyasskin, @wseltzer)
-
Processing is sensitive, not purposes w3ctag/privacy-principles#242 (7 comments by @jyasskin, @torgo)
-
remove list of privacy labor suggestions around ancillary data w3ctag/privacy-principles#221 (6 comments by @chrisn, @jyasskin, @pes10k, @samuelweiler)
-
Tweaks to the Incorporating section w3ctag/privacy-principles#266 (3 comments by @chrisn, @jyasskin, @wseltzer)
-
Start making the opt in/out section consistently talk about purposes. w3ctag/privacy-principles#236 (1 comment by @jyasskin)
-
Remove the statement about a general opt-out overriding a specific opt-in. w3ctag/privacy-principles#238 (1 comment by @jyasskin)
-
w3ctag/ethical-web-principles
-
1 issue received 1 new comment.
w3ctag/accessibility-screener
-
1 issue opened.
-
Synergy with i18n short checklist? w3ctag/accessibility-screener#3, by @r12a.
-
-
1 issue received 1 new comment.
w3ctag/web-without-3p-cookies
-
2 issues opened.
-
One more potential ref w3ctag/web-without-3p-cookies#20, by @mnot.
-
Movement for an Open Web (MOW) comments on W3C TAG Draft Finding w3ctag/web-without-3p-cookies#19, by @Tim-Cowen.
-
-
2 issues closed.
-
One more potential ref w3ctag/web-without-3p-cookies#20.
-
Movement for an Open Web (MOW) comments on W3C TAG Draft Finding w3ctag/web-without-3p-cookies#19.
-
-
2 issues received 2 new comments.
-
Movement for an Open Web (MOW) comments on W3C TAG Draft Finding w3ctag/web-without-3p-cookies#19 (1 comment by @plinss)
Privacy Principles Task Force
Participants
-
3 participants joined the Privacy Principles Task Force.
-
Theresa O'Connor joined.
-
Amy Guy joined.
-
Daniel Appelquist joined.
-
TR publications
-
1 document published.
-
Web Platform Design Principles published as a Note. History of Web Platform Design Principles
-
GitHub
w3ctag/design-reviews
-
9 issues opened.
-
FedCM: LoginHint, UserInfo, and RPContext w3ctag/design-reviews#839, by @npm1.
-
Specification review for fenced frames w3ctag/design-reviews#838, by @domfarolino.
-
WebRTC-SVC (Scalable Video Coding) w3ctag/design-reviews#837, by @dontcallmedom.
-
WebRTC Codec selection API w3ctag/design-reviews#836, by @Orphis.
-
Disabling UA transitions for same-document navigations w3ctag/design-reviews#835, by @khushalsagar.
-
Detect UA Transitions on Same-Document Navigations w3ctag/design-reviews#834, by @khushalsagar.
-
[FYI] Report Critical-CH caused restart in NavigationTiming w3ctag/design-reviews#833, by @arichiv.
-
TAG review of the proposal to use the RegExp `v` flag instead of `u` for the HTML `pattern` attribute w3ctag/design-reviews#832, by @mathiasbynens.
-
Eligibility for autofill w3ctag/design-reviews#831, by @schwering.
-
-
6 issues closed.
-
Wildcards in Permissions Policy Origins w3ctag/design-reviews#765.
-
Web Bluetooth exclusionFilters option in requestDevice() w3ctag/design-reviews#830.
-
TAG review of the proposal to use the RegExp `v` flag instead of `u` for the HTML `pattern` attribute w3ctag/design-reviews#832.
-
Pre-CR review: HTML Review Draft — Published 18 January 2021 w3ctag/design-reviews#657.
-
The web platform needs a service discovery mechanism w3ctag/design-reviews#240.
-
Background Blur API w3ctag/design-reviews#826.
-
-
30 issues received 72 new comments.
-
Early Design Review: Pending Beacon API w3ctag/design-reviews#776 (9 comments by @fergald, @hober, @miketaylr, @mingyc, @npdoty, @ylafon)
-
Compute Pressure Specification Review w3ctag/design-reviews#795 (5 comments by @anssiko, @cynthia, @hober, @kenchris)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (5 comments by @liberato-at-chromium, @tomayac, @torgo, @ylafon)
-
Early design review for the Topics API w3ctag/design-reviews#726 (5 comments by @dmarti, @jkarlin, @martinthomson, @michaelkleber)
-
WebRTC-SVC (Scalable Video Coding) w3ctag/design-reviews#837 (4 comments by @aboba, @dontcallmedom, @johnathan79717, @Orphis)
-
Eligibility for autofill w3ctag/design-reviews#831 (4 comments by @cynthia, @hober, @schwering, @torgo)
-
TAG review of the proposal to use the RegExp `v` flag instead of `u` for the HTML `pattern` attribute w3ctag/design-reviews#832 (4 comments by @LeaVerou, @mathiasbynens)
-
Early design review request: IPA w3ctag/design-reviews#823 (3 comments by @benjaminsavage, @martinthomson, @ShivanKaul)
-
WebAssembly Garbage Collection extensions w3ctag/design-reviews#814 (3 comments by @ajklein, @rossberg, @ylafon)
-
Design Review: Speculation Rules (Prefetch) w3ctag/design-reviews#721 (3 comments by @cynthia, @hober, @jeremyroman)
-
Moving local files with the File System Access API w3ctag/design-reviews#805 (2 comments by @a-sully)
-
Related Website Sets (formerly First-Party Sets) w3ctag/design-reviews#342 (2 comments by @slightlyoff, @torgo)
-
Two changes to Secure Payment Confirmation prior to CR w3ctag/design-reviews#802 (1 comment by @ianbjacobs)
-
early design review: bfcache/prerendering eviction APIs w3ctag/design-reviews#786 (1 comment by @fergald)
-
Web Bluetooth exclusionFilters option in requestDevice() w3ctag/design-reviews#830 (1 comment by @plinss)
-
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 @hober)
-
The web platform needs a service discovery mechanism w3ctag/design-reviews#240 (1 comment by @plinss)
-
[FYI] Report Critical-CH caused restart in NavigationTiming w3ctag/design-reviews#833 (1 comment by @slightlyoff)
-
w3ctag/privacy-principles
-
9 issues opened.
-
Centralization risks of noise as a mitigation tool w3ctag/privacy-principles#261, by @dmarti.
-
We <dfn> "principle" with a different meaning than we're using in the title of the document w3ctag/privacy-principles#260, by @jyasskin.
-
Add link to "site" definition under "Cross-site recognition" w3ctag/privacy-principles#257, by @chrisn.
-
Feedback on section 1.4 "Incorporating Different Privacy Principles" w3ctag/privacy-principles#256, by @chrisn.
-
People's Agents w3ctag/privacy-principles#255, by @chrisn.
-
Collective Governance w3ctag/privacy-principles#254, by @chrisn.
-
Suggestions on Introduction w3ctag/privacy-principles#253, by @chrisn.
-
Mention limitations on data rights w3ctag/privacy-principles#252, by @jyasskin.
-
refined example about privacy of small groups w3ctag/privacy-principles#251, by @npdoty.
-
-
8 issues closed.
-
Mention limitations on data rights w3ctag/privacy-principles#252.
-
Add link to "site" definition under "Cross-site recognition" w3ctag/privacy-principles#257.
-
Avoid endorsing cookie banners and other sharing indicators that encourage users to ignore them w3ctag/privacy-principles#230.
-
Is all print advertising a violation of collective privacy? w3ctag/privacy-principles#235.
-
Don't imply the GPC has specific effects under the GPDR. w3ctag/privacy-principles#232.
-
Need a better source for "fiduciary" term w3ctag/privacy-principles#240.
-
Privacy risks should be taken in context: Who is processing data and how? w3ctag/privacy-principles#225.
-
Need matching documents for other kinds of principles w3ctag/privacy-principles#228.
-
-
12 issues received 20 new comments.
-
Collective Governance w3ctag/privacy-principles#254 (4 comments by @chrisn, @jyasskin, @npdoty, @torgo)
-
Is all print advertising a violation of collective privacy? w3ctag/privacy-principles#235 (4 comments by @dmarti, @jyasskin, @michaelkleber, @wseltzer)
-
Suggestions on Introduction w3ctag/privacy-principles#253 (3 comments by @chrisn, @jyasskin, @torgo)
-
Add link to "site" definition under "Cross-site recognition" w3ctag/privacy-principles#257 (1 comment by @jyasskin)
-
Privacy risks should be taken in context: Who is processing data and how? w3ctag/privacy-principles#225 (1 comment by @torgo)
-
Need matching documents for other kinds of principles w3ctag/privacy-principles#228 (1 comment by @torgo)
-
Avoid endorsing cookie banners and other sharing indicators that encourage users to ignore them w3ctag/privacy-principles#230 (1 comment by @dmarti)
-
Sharing identity and reading history aren't purposes w3ctag/privacy-principles#229 (1 comment by @lknik)
-
-
9 pull requests opened.
-
Restructure introduction sections w3ctag/privacy-principles#262, by @chrisn.
-
Fix capitalisation of JavaScript w3ctag/privacy-principles#259, by @chrisn.
-
Add link to 'site' definition w3ctag/privacy-principles#258, by @chrisn.
-
Better references for fiduciaries, fixes #240 w3ctag/privacy-principles#250, by @darobin.
-
Avoid saying that safety systems have to describe how to exploit them. w3ctag/privacy-principles#249, by @jyasskin.
-
Identify what makes print less likely to violate group privacy than the web. w3ctag/privacy-principles#248, by @jyasskin.
-
Try to improve the wording around consent indicators. w3ctag/privacy-principles#246, by @jyasskin.
-
Replace the reference for "fiduciary". w3ctag/privacy-principles#245, by @jyasskin.
-
Create 03-29-minutes.md w3ctag/privacy-principles#244, by @torgo.
-
-
7 pull requests merged.
-
Fix capitalisation of JavaScript w3ctag/privacy-principles#259.
-
Add link to 'site' definition w3ctag/privacy-principles#258.
-
Try to improve the wording around consent indicators. w3ctag/privacy-principles#246.
-
Avoid saying that safety systems have to describe how to exploit them. w3ctag/privacy-principles#249.
-
Identify what makes print less likely to violate group privacy than the web. w3ctag/privacy-principles#248.
-
Make it clear that this is a general statement, not about the GDPR w3ctag/privacy-principles#243.
-
Better references for fiduciaries, fixes #240 w3ctag/privacy-principles#250.
-
-
2 pull requests closed.
-
Replace the reference for "fiduciary". w3ctag/privacy-principles#245.
-
Create 03-29-minutes.md w3ctag/privacy-principles#244.
-
-
7 pull requests received 16 new comments.
-
Avoid saying that safety systems have to describe how to exploit them. w3ctag/privacy-principles#249 (6 comments by @darobin, @jbradleychen, @jyasskin, @npdoty)
-
Make it clear that this is a general statement, not about the GDPR w3ctag/privacy-principles#243 (3 comments by @darobin, @dmarti, @jyasskin)
-
Replace the reference for "fiduciary". w3ctag/privacy-principles#245 (2 comments by @darobin, @jyasskin)
-
Identify what makes print less likely to violate group privacy than the web. w3ctag/privacy-principles#248 (2 comments by @darobin, @jyasskin)
-
Try to improve the wording around consent indicators. w3ctag/privacy-principles#246 (1 comment by @Mwilson7583)
-
w3ctag/ethical-web-principles
-
1 pull request opened.
-
Revise information integrity goals w3ctag/ethical-web-principles#93, by @jbradleychen.
-
w3ctag/design-principles
-
4 issues opened.
-
"Make method arguments optional if possible" section has bad advice w3ctag/design-principles#437, by @bakkot.
-
Make our principles more inclusive of non-Web JS APIs w3ctag/design-principles#436, by @LeaVerou.
-
Examples for "overloading" principle w3ctag/design-principles#431, by @torgo.
-
Example for features "temporarily available" w3ctag/design-principles#428, by @torgo.
-
-
3 issues closed.
-
New principle: When to use client hints w3ctag/design-principles#307.
-
New principle: Guidance on User Activation w3ctag/design-principles#314.
-
Typo "firint" in section 7.6. Guard against potential recursion w3ctag/design-principles#421.
-
-
9 issues received 20 new comments.
-
Advice on JS passing points-in-time or offsets-from-now w3ctag/design-principles#425 (4 comments by @bakkot, @jyasskin, @LeaVerou)
-
WebIDL interfaces should only be used when you have both data and behavior w3ctag/design-principles#11 (4 comments by @bathos, @LeaVerou, @ljharb, @ptomato)
-
"Make method arguments optional if possible" section has bad advice w3ctag/design-principles#437 (3 comments by @bakkot, @bathos)
-
New principle: Guidance on options dictionaries and default values w3ctag/design-principles#391 (3 comments by @bakkot, @LeaVerou)
-
Make our principles more inclusive of non-Web JS APIs w3ctag/design-principles#436 (1 comment by @cynthia)
-
New principle: New features should not break existing ones w3ctag/design-principles#297 (1 comment by @torgo)
-
[Meta] Tackling design problems earlier than design review / A Q&A section for API design w3ctag/design-principles#319 (1 comment by @atanassov)
-
-
6 pull requests opened.
-
Make 6.1 more inclusive of non-Web JS APIs w3ctag/design-principles#435, by @LeaVerou.
-
Adding principle for client hints, fixes #307 w3ctag/design-principles#434, by @torgo.
-
Remove unnecessary bit in heading w3ctag/design-principles#433, by @cynthia.
-
fix the build w3ctag/design-principles#432, by @hober.
-
Ignore build/ in .gitignore. w3ctag/design-principles#430, by @hober.
-
-
9 pull requests merged.
-
Adding principle for client hints, fixes #307 w3ctag/design-principles#434.
-
Remove unnecessary bit in heading w3ctag/design-principles#433.
-
fix the build w3ctag/design-principles#432.
-
Guidance about serialization w3ctag/design-principles#367.
-
New principle: on overloading, for #131 w3ctag/design-principles#372.
-
Ignore build/ in .gitignore. w3ctag/design-principles#430.
-
Fix typo. w3ctag/design-principles#429.
-
Fixing markup w3ctag/design-principles#405.
-
Describe what to do when a feature is temporarily only available on some platforms. w3ctag/design-principles#357.
-
-
13 pull requests received 88 new comments.
-
New text re: balancing concerns between interoperability and implementability w3ctag/design-principles#290 (19 comments by @hober, @torgo)
-
New principle: on overloading, for #131 w3ctag/design-principles#372 (13 comments by @hober, @torgo)
-
Warn against getter throwing exception since it is a side effect w3ctag/design-principles#408 (8 comments by @cynthia, @hober)
-
Adding principle for client hints, fixes #307 w3ctag/design-principles#434 (7 comments by @cynthia, @hober, @LeaVerou)
-
Make 6.1 more inclusive of non-Web JS APIs w3ctag/design-principles#435 (5 comments by @cynthia, @hober, @LeaVerou, @plinss)
-
First pass on backwards compatibility principle w3ctag/design-principles#354 (4 comments by @plinss, @torgo)
-
Make HTML attribute sections consecutive w3ctag/design-principles#412 (2 comments by @cynthia, @LeaVerou)
-
Describe what to do when a feature is temporarily only available on some platforms. w3ctag/design-principles#357 (2 comments by @torgo)
-
w3ctag/web-without-3p-cookies
-
7 issues opened.
-
Better name for third-party cookies: Cross-site cookies w3ctag/web-without-3p-cookies#14, by @johnwilander.
-
warn against combined harms, but not against parallel development and testing w3ctag/web-without-3p-cookies#13, by @npdoty.
-
Do we really want to discourage more general replacements entirely? w3ctag/web-without-3p-cookies#7, by @LeaVerou.
-
Recommendation to deprecate 3rd party cookies before alternatives are standardized is not pragmatic w3ctag/web-without-3p-cookies#5, by @LeaVerou.
-
list of CGs where relevant incubations are occurring should include the Privacy CG w3ctag/web-without-3p-cookies#3, by @hober.
-
Centralization risks of cookie alternatives? w3ctag/web-without-3p-cookies#2, by @dmarti.
-
Link to the EWP instead of Unsanctioned Tracking? w3ctag/web-without-3p-cookies#1, by @torgo.
-
-
7 issues closed.
-
Centralization risks of cookie alternatives? w3ctag/web-without-3p-cookies#2.
-
warn against combined harms, but not against parallel development and testing w3ctag/web-without-3p-cookies#13.
-
Better name for third-party cookies: Cross-site cookies w3ctag/web-without-3p-cookies#14.
-
Do we really want to discourage more general replacements entirely? w3ctag/web-without-3p-cookies#7.
-
Recommendation to deprecate 3rd party cookies before alternatives are standardized is not pragmatic w3ctag/web-without-3p-cookies#5.
-
list of CGs where relevant incubations are occurring should include the Privacy CG w3ctag/web-without-3p-cookies#3.
-
Link to the EWP instead of Unsanctioned Tracking? w3ctag/web-without-3p-cookies#1.
-
-
1 issue reopened.
-
warn against combined harms, but not against parallel development and testing w3ctag/web-without-3p-cookies#13, by @cynthia.
-
-
5 issues received 11 new comments.
-
Do we really want to discourage more general replacements entirely? w3ctag/web-without-3p-cookies#7 (4 comments by @hober, @LeaVerou, @plinss, @torgo)
-
Recommendation to deprecate 3rd party cookies before alternatives are standardized is not pragmatic w3ctag/web-without-3p-cookies#5 (3 comments by @cynthia, @hober)
-
Link to the EWP instead of Unsanctioned Tracking? w3ctag/web-without-3p-cookies#1 (2 comments by @torgo)
-
Centralization risks of cookie alternatives? w3ctag/web-without-3p-cookies#2 (1 comment by @hadleybeeman)
-
Better name for third-party cookies: Cross-site cookies w3ctag/web-without-3p-cookies#14 (1 comment by @hadleybeeman)
-
-
11 pull requests opened.
-
Remove SSO mention on w3ctag/web-without-3p-cookies#18, by @cynthia.
-
Reword general replacement text w3ctag/web-without-3p-cookies#17, by @plinss.
-
Warn against combined harms, but not development w3ctag/web-without-3p-cookies#16, by @cynthia.
-
Add a parenthetical at first use of 'third-party cookies' to clarify that we mean cross-site cookies. w3ctag/web-without-3p-cookies#15, by @hober.
-
Hadley's rework of section 4 w3ctag/web-without-3p-cookies#12, by @torgo.
-
us spelling w3ctag/web-without-3p-cookies#11, by @torgo.
-
Reword unrealistic recommendation w3ctag/web-without-3p-cookies#10, by @cynthia.
-
Reword unrealistic recommendation w3ctag/web-without-3p-cookies#9, by @cynthia.
-
Adding link to Chrome's blog post w3ctag/web-without-3p-cookies#8, by @torgo.
-
changing the paragraph defining cookies and 3rd party cookies to make it scan better w3ctag/web-without-3p-cookies#6, by @torgo.
-
Add Privacy CG to the list of CGs in which relevant incubations are happening. Alphabetize that list of CGs. w3ctag/web-without-3p-cookies#4, by @hober.
-
-
10 pull requests merged.
-
Remove SSO mention on w3ctag/web-without-3p-cookies#18.
-
Warn against combined harms, but not development w3ctag/web-without-3p-cookies#16.
-
Add a parenthetical at first use of 'third-party cookies' to clarify that we mean cross-site cookies. w3ctag/web-without-3p-cookies#15.
-
Reword general replacement text w3ctag/web-without-3p-cookies#17.
-
Reword unrealistic recommendation w3ctag/web-without-3p-cookies#10.
-
Hadley's rework of section 4 w3ctag/web-without-3p-cookies#12.
-
us spelling w3ctag/web-without-3p-cookies#11.
-
changing the paragraph defining cookies and 3rd party cookies to make it scan better w3ctag/web-without-3p-cookies#6.
-
Adding link to Chrome's blog post w3ctag/web-without-3p-cookies#8.
-
Add Privacy CG to the list of CGs in which relevant incubations are happening. Alphabetize that list of CGs. w3ctag/web-without-3p-cookies#4.
-
-
1 pull request closed.
-
Reword unrealistic recommendation w3ctag/web-without-3p-cookies#9.
-
-
6 pull requests received 11 new comments.
-
Reword unrealistic recommendation w3ctag/web-without-3p-cookies#10 (4 comments by @cynthia, @hober, @plinss)
-
Warn against combined harms, but not development w3ctag/web-without-3p-cookies#16 (2 comments by @hadleybeeman, @npdoty)
-
changing the paragraph defining cookies and 3rd party cookies to make it scan better w3ctag/web-without-3p-cookies#6 (2 comments by @plinss)
-
Add a parenthetical at first use of 'third-party cookies' to clarify that we mean cross-site cookies. w3ctag/web-without-3p-cookies#15 (1 comment by @hober)
-
w3ctag/accessibility-screener
-
1 issue closed.
-
Make it clear that e.g. adding a permission prompt doesn't trigger review w3ctag/accessibility-screener#1.
-
-
1 issue received 1 new comment.
-
Make it clear that e.g. adding a permission prompt doesn't trigger review w3ctag/accessibility-screener#1 (1 comment by @cynthia)
-
-
1 pull request opened.
-
Adding title and 1-sentence explanation w3ctag/accessibility-screener#2, by @torgo.
-
-
1 pull request merged.
-
Adding title and 1-sentence explanation w3ctag/accessibility-screener#2.
-
w3ctag/process
-
1 issue closed.
-
Publications on TR w3ctag/process#21.
-
w3ctag/bfcache-guide
-
1 pull request merged.
-
Add references to steps in HTML spec for fully active state changes w3ctag/bfcache-guide#4.
-
-
1 pull request received 1 new comment.
-
Add references to steps in HTML spec for fully active state changes w3ctag/bfcache-guide#4 (1 comment by @rakina)
-
w3ctag/promises-guide
-
1 issue opened.
-
Can promises be used for one-time events that may never occur? w3ctag/promises-guide#73, by @kainino0x.
-
-
1 issue received 1 new comment.
-
Can promises be used for one-time events that may never occur? w3ctag/promises-guide#73 (1 comment by @domenic)
-
GitHub
w3ctag/design-reviews
-
8 issues opened.
-
Web Bluetooth exclusionFilters option in requestDevice() w3ctag/design-reviews#830, by @beaufortfrancois.
-
Entry and Exit Animations w3ctag/design-reviews#829, by @josepharhar.
-
Spec review for Scroll-driven Animations w3ctag/design-reviews#828, by @flackr.
-
Early design review: scheduler.yield() w3ctag/design-reviews#827, by @shaseley.
-
Background Blur API w3ctag/design-reviews#826, by @riju.
-
Transitions on specified discrete properties w3ctag/design-reviews#825, by @josepharhar.
-
Display and content-visibility animations w3ctag/design-reviews#824, by @josepharhar.
-
Early design review request: IPA w3ctag/design-reviews#823, by @martinthomson.
-
-
10 issues closed.
-
Transitions on specified discrete properties w3ctag/design-reviews#825.
-
Display and content-visibility animations w3ctag/design-reviews#824.
-
Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 w3ctag/design-reviews#811.
-
CR Snapshot Review for EPUB 3.3 w3ctag/design-reviews#816.
-
Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences w3ctag/design-reviews#767.
-
text-wrap: balance w3ctag/design-reviews#822.
-
The Popover API (previously Popup) w3ctag/design-reviews#743.
-
Gamepad Extensions API touch input w3ctag/design-reviews#799.
-
FileSystemHandle.remove() for the File System Access API w3ctag/design-reviews#773.
-
Skip no-op service worker fetch handler w3ctag/design-reviews#815.
-
-
1 issue reopened.
-
The Popover API (previously Popup) w3ctag/design-reviews#743, by @torgo.
-
-
29 issues received 75 new comments.
-
requestStorageAccessFor w3ctag/design-reviews#808 (9 comments by @annevk, @johannhof, @mreichhoff, @plinss, @torgo)
-
Early design review request: IPA w3ctag/design-reviews#823 (7 comments by @eriktaubeneck, @hadleybeeman, @martinthomson, @ShivanKaul)
-
Moving local files with the File System Access API w3ctag/design-reviews#805 (6 comments by @a-sully, @plinss, @torgo)
-
Design Review: Speculation Rules (Prefetch) w3ctag/design-reviews#721 (5 comments by @jeremyroman, @kjmcnee, @LeaVerou, @rhiaro, @toyoshim)
-
COOP: restrict-properties early review w3ctag/design-reviews#760 (4 comments by @hemeryar, @hober, @torgo)
-
The Popover API (previously Popup) w3ctag/design-reviews#743 (4 comments by @atanassov, @mfreed7, @torgo)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (3 comments by @steimelchrome, @torgo)
-
Transitions on specified discrete properties w3ctag/design-reviews#825 (3 comments by @josepharhar, @LeaVerou)
-
Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 w3ctag/design-reviews#811 (2 comments by @torgo)
-
Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences w3ctag/design-reviews#767 (2 comments by @michaelwasserman, @torgo)
-
FileSystemHandle.remove() for the File System Access API w3ctag/design-reviews#773 (1 comment by @rhiaro)
-
w3ctag/bfcache-guide
-
1 pull request opened.
-
Add references to steps in HTML spec for fully active state changes w3ctag/bfcache-guide#4, by @rakina.
-
-
1 pull request received 19 new comments.
w3ctag/design-principles
-
5 issues opened.
-
Clarify which enum the principle 6.11 is talking about w3ctag/design-principles#427, by @saschanaz.
-
New principle: Avoid adding (non-constructor) functions to the global scope w3ctag/design-principles#426, by @LeaVerou.
-
Advice on JS passing points-in-time or offsets-from-now w3ctag/design-principles#425, by @jyasskin.
-
Web platform design principle on attribute <- -> IDL attribute reflection (principle 3.5 Keep attributes in sync) w3ctag/design-principles#424, by @prushforth.
-
Web platform features that augment HTML elements en masse w3ctag/design-principles#423, by @LeaVerou.
-
-
1 issue closed.
-
Web platform design principle on attribute <- -> IDL attribute reflection (principle 3.5 Keep attributes in sync) w3ctag/design-principles#424.
-
-
6 issues received 20 new comments.
-
New principle: Avoid adding (non-constructor) functions to the global scope w3ctag/design-principles#426 (8 comments by @annevk, @bathos, @domenic, @LeaVerou, @leobalter, @syg)
-
Clarify which enum the principle 6.11 is talking about w3ctag/design-principles#427 (4 comments by @annevk, @saschanaz)
-
Advice on JS passing points-in-time or offsets-from-now w3ctag/design-principles#425 (3 comments by @annevk, @jyasskin)
-
Web platform features that augment HTML elements en masse w3ctag/design-principles#423 (2 comments by @annevk, @jeremyroman)
-
What should the casing rules be for headers? w3ctag/design-principles#422 (2 comments by @domenic, @mnot)
-
Web platform design principle on attribute <- -> IDL attribute reflection (principle 3.5 Keep attributes in sync) w3ctag/design-principles#424 (1 comment by @prushforth)
-
w3ctag/privacy-principles
-
13 issues opened.
-
Align our Duty of Loyalty with Richards/Hartzog's w3ctag/privacy-principles#241, by @jyasskin.
-
Need a better source for "fiduciary" term w3ctag/privacy-principles#240, by @jyasskin.
-
Is all print advertising a violation of collective privacy? w3ctag/privacy-principles#235, by @jyasskin.
-
Clarify uses of "self-governing" w3ctag/privacy-principles#233, by @jyasskin.
-
Don't imply the GPC has specific effects under the GPDR. w3ctag/privacy-principles#232, by @jyasskin.
-
Don't claim general actions override specific ones w3ctag/privacy-principles#231, by @jyasskin.
-
Avoid endorsing cookie banners and other sharing indicators that encourage users to ignore them w3ctag/privacy-principles#230, by @jyasskin.
-
Sharing identity and reading history aren't purposes w3ctag/privacy-principles#229, by @jyasskin.
-
Need matching documents for other kinds of principles w3ctag/privacy-principles#228, by @jyasskin.
-
Separating identity from identifiers or information linked with identifiers w3ctag/privacy-principles#226, by @dmarti.
-
Privacy risks should be taken in context: Who is processing data and how? w3ctag/privacy-principles#225, by @dmarti.
-
Using the privacy argument as an excuse to discriminate w3ctag/privacy-principles#224, by @dmarti.
-
[editorial] correct w3cid for editors w3ctag/privacy-principles#223, by @npdoty.
-
-
2 issues closed.
-
Using the privacy argument as an excuse to discriminate w3ctag/privacy-principles#224.
-
[editorial] correct w3cid for editors w3ctag/privacy-principles#223.
-
-
13 issues received 55 new comments.
-
Avoid endorsing cookie banners and other sharing indicators that encourage users to ignore them w3ctag/privacy-principles#230 (9 comments by @darobin, @dmarti, @lknik, @michaelkleber, @npdoty)
-
Sharing identity and reading history aren't purposes w3ctag/privacy-principles#229 (8 comments by @darobin, @jyasskin, @lknik, @michaelkleber)
-
Is all print advertising a violation of collective privacy? w3ctag/privacy-principles#235 (7 comments by @darobin, @dmarti, @jyasskin, @npdoty)
-
Align our Duty of Loyalty with Richards/Hartzog's w3ctag/privacy-principles#241 (6 comments by @darobin, @jyasskin)
-
Need matching documents for other kinds of principles w3ctag/privacy-principles#228 (4 comments by @darobin, @jbradleychen, @jyasskin)
-
Don't claim general actions override specific ones w3ctag/privacy-principles#231 (3 comments by @darobin, @michaelkleber)
-
Privacy risks should be taken in context: Who is processing data and how? w3ctag/privacy-principles#225 (3 comments by @darobin, @dmarti)
-
Need a better source for "fiduciary" term w3ctag/privacy-principles#240 (2 comments by @darobin, @wseltzer)
-
Don't imply the GPC has specific effects under the GPDR. w3ctag/privacy-principles#232 (2 comments by @darobin, @jyasskin)
-
Separating identity from identifiers or information linked with identifiers w3ctag/privacy-principles#226 (1 comment by @darobin)
-
-
8 pull requests opened.
-
Make it clear that this is a general statement, not about the GDPR w3ctag/privacy-principles#243, by @darobin.
-
Processing is sensitive, not purposes w3ctag/privacy-principles#242, by @darobin.
-
Use Infra's definition of "user agent". w3ctag/privacy-principles#239, by @jyasskin.
-
Remove the statement about a general opt-out overriding a specific opt-in. w3ctag/privacy-principles#238, by @jyasskin.
-
Remove "unprecedented": these concentrations of power have precedents. w3ctag/privacy-principles#237, by @jyasskin.
-
Start making the opt in/out section consistently talk about purposes. w3ctag/privacy-principles#236, by @jyasskin.
-
Remove some sarcasm about FIPs. w3ctag/privacy-principles#234, by @jyasskin.
-
Fix #224: Mention harm from partially blocking cross-context recognition. w3ctag/privacy-principles#227, by @jyasskin.
-
-
5 pull requests merged.
-
Use Infra's definition of "user agent". w3ctag/privacy-principles#239.
-
Remove "unprecedented": these concentrations of power have precedents. w3ctag/privacy-principles#237.
-
Remove some sarcasm about FIPs. w3ctag/privacy-principles#234.
-
Fix #224: Mention harm from partially blocking cross-context recognition. w3ctag/privacy-principles#227.
-
Change 'send' to 'expose' in the ancillary data section. w3ctag/privacy-principles#222.
-
-
1 pull request closed.
-
Avoid asking for fake consent w3ctag/privacy-principles#190.
-
-
8 pull requests received 22 new comments.
-
Fix #224: Mention harm from partially blocking cross-context recognition. w3ctag/privacy-principles#227 (9 comments by @darobin, @dmarti, @jyasskin)
-
Make it clear that this is a general statement, not about the GDPR w3ctag/privacy-principles#243 (3 comments by @darobin, @jyasskin, @npdoty)
-
Remove some sarcasm about FIPs. w3ctag/privacy-principles#234 (3 comments by @chrisn, @darobin, @jyasskin)
-
Processing is sensitive, not purposes w3ctag/privacy-principles#242 (2 comments by @darobin, @jyasskin)
-
Remove "unprecedented": these concentrations of power have precedents. w3ctag/privacy-principles#237 (2 comments by @darobin, @jbradleychen)
-
Remove the statement about a general opt-out overriding a specific opt-in. w3ctag/privacy-principles#238 (1 comment by @darobin)
-
Start making the opt in/out section consistently talk about purposes. w3ctag/privacy-principles#236 (1 comment by @darobin)
-
w3ctag/process
-
1 pull request opened.
-
Add fast track w3ctag/process#30, by @torgo.
-
w3ctag/societal-impact-questionnaire
-
1 pull request received 2 new comments.
w3ctag/ethical-web-principles
-
1 issue received 2 new comments.
-
Discuss macroeconomic impact and equality? w3ctag/ethical-web-principles#92 (2 comments by @darobin, @hober)
-
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
-
Past meetings
-
1 meeting.
GitHub
w3ctag/design-principles
-
5 issues opened.
-
What should the casing rules be for headers? w3ctag/design-principles#422, by @domenic.
-
Typo "firint" in section 7.6. Guard against potential recursion w3ctag/design-principles#421, by @Andrew-Cottrell.
-
Generalize advice about workers w3ctag/design-principles#420, by @hober.
-
Introduce CI and releases w3ctag/design-principles#419, by @cynthia.
-
Attributes vs method section lacks guidance on setters w3ctag/design-principles#415, by @cynthia.
-
-
4 issues closed.
-
New principle: Patterns for x() vs xSync() w3ctag/design-principles#402.
-
Should charters link to the TAG design principles? w3ctag/design-principles#407.
-
New principle: Prefer dictionary arguments for all optional parameters (and non-obvious parameters?) w3ctag/design-principles#366.
-
Guidance in exposing some APIs only off the main thread w3ctag/design-principles#360.
-
-
4 issues received 9 new comments.
-
What should the casing rules be for headers? w3ctag/design-principles#422 (4 comments by @annevk, @domenic, @mnot)
-
Should charters link to the TAG design principles? w3ctag/design-principles#407 (2 comments by @LeaVerou, @svgeesus)
-
Attributes vs method section lacks guidance on setters w3ctag/design-principles#415 (2 comments by @annevk, @LeaVerou)
-
-
3 pull requests opened.
-
Fix more lint issues w3ctag/design-principles#418, by @gibson042.
-
Add new principle for sync() vs async(). w3ctag/design-principles#417, by @cynthia.
-
Change guidance about dictionaries to cover all optional arguments w3ctag/design-principles#416, by @LeaVerou.
-
-
5 pull requests merged.
-
Add new principle for sync() vs async(). w3ctag/design-principles#417.
-
Fix more lint issues w3ctag/design-principles#418.
-
Fix lint issues w3ctag/design-principles#413.
-
Change guidance about dictionaries to cover all optional arguments w3ctag/design-principles#416.
-
New principle: Some APIs should only be exposed to dedicated workers w3ctag/design-principles#404.
-
-
1 pull request closed.
-
Group "don't reveal {assistive tech,private browsing}" under a common heading w3ctag/design-principles#411.
-
-
7 pull requests received 36 new comments.
-
Add new principle for sync() vs async(). w3ctag/design-principles#417 (11 comments by @cynthia, @LeaVerou, @plinss)
-
Warn against getter throwing exception since it is a side effect w3ctag/design-principles#408 (11 comments by @annevk, @atanassov, @cynthia, @LeaVerou)
-
Change guidance about dictionaries to cover all optional arguments w3ctag/design-principles#416 (7 comments by @cynthia, @LeaVerou)
-
Group "don't reveal {assistive tech,private browsing}" under a common heading w3ctag/design-principles#411 (1 comment by @cynthia)
-
w3ctag/privacy-principles
-
1 issue opened.
-
Remove or revise examples of signals browsers should use to prevent "privacy labor" in ancillary data w3ctag/privacy-principles#220, by @pes10k.
-
-
5 issues closed.
-
Reciprocal duty of honesty for publishers w3ctag/privacy-principles#108.
-
Reciprocal Duty of Honesty for ordinary users? w3ctag/privacy-principles#107.
-
2.4 right to know who has data about you w3ctag/privacy-principles#156.
-
when is sharing data for some ancillary purpose consistent with privacy principles? w3ctag/privacy-principles#150.
-
Contributing to an aggregate w3ctag/privacy-principles#165.
-
-
1 issue reopened.
-
when is sharing data for some ancillary purpose consistent with privacy principles? w3ctag/privacy-principles#150, by @npdoty.
-
-
6 issues received 11 new comments.
-
Reciprocal Duty of Honesty for ordinary users? w3ctag/privacy-principles#107 (2 comments by @npdoty)
-
when is sharing data for some ancillary purpose consistent with privacy principles? w3ctag/privacy-principles#150 (2 comments by @npdoty, @torgo)
-
2 pull requests opened.
-
Change 'send' to 'expose' in the ancillary data section. w3ctag/privacy-principles#222, by @jyasskin.
-
remove list of privacy labor suggestions around ancillary data w3ctag/privacy-principles#221, by @pes10k.
-
-
3 pull requests merged.
-
Revisions and concisions around ancillary data use w3ctag/privacy-principles#216.
-
Simplify and remove redundant text in the Identity section. w3ctag/privacy-principles#218.
-
Discovery 156 w3ctag/privacy-principles#219.
-
-
3 pull requests received 27 new comments.
-
Revisions and concisions around ancillary data use w3ctag/privacy-principles#216 (20 comments by @jyasskin, @npdoty, @pes10k)
-
Simplify and remove redundant text in the Identity section. w3ctag/privacy-principles#218 (6 comments by @jyasskin, @npdoty, @rhiaro)
-
Change 'send' to 'expose' in the ancillary data section. w3ctag/privacy-principles#222 (1 comment by @npdoty)
-
w3ctag/design-reviews
-
9 issues opened.
-
text-wrap: balance w3ctag/design-reviews#822, by @kojiishi.
-
Review of DPUB-ARIA 1.1 and DPUB-AAM 1.1 w3ctag/design-reviews#821, by @mattgarrish.
-
Web Authentication: Large Blob extension w3ctag/design-reviews#820, by @nsatragno.
-
Early review for adding a new value to the standard list of `name`s for a meta tag w3ctag/design-reviews#819, by @diekus.
-
Web of Things (WoT) Profile - Review Requested w3ctag/design-reviews#818, by @mmccool.
-
CR Snapshot Review for EPUB 3.3 w3ctag/design-reviews#816, by @wareid.
-
Skip no-op service worker fetch handler w3ctag/design-reviews#815, by @yoshisatoyanagisawa.
-
WebAssembly Garbage Collection extensions w3ctag/design-reviews#814, by @ajklein.
-
FedCM Auto Re-authentication API w3ctag/design-reviews#813, by @yi-gu.
-
-
13 issues closed.
-
Review request on `blocking=render` attribute for scripts and stylesheets w3ctag/design-reviews#727.
-
View Transitions API w3ctag/design-reviews#748.
-
Private State Tokens (formerly Trust Tokens) w3ctag/design-reviews#780.
-
Autoplay Policy Detection API w3ctag/design-reviews#810.
-
Storage Access API w3ctag/design-reviews#807.
-
No-Vary-Search HTTP header w3ctag/design-reviews#797.
-
Pre-CR review: DOM Review Draft — Published 21 June 2021 w3ctag/design-reviews#658.
-
AbortSignal.timeout() w3ctag/design-reviews#711.
-
WebAuthn PRF extension w3ctag/design-reviews#806.
-
Collection of Screensharing-related UX Hints w3ctag/design-reviews#744.
-
Two changes to Secure Payment Confirmation prior to CR w3ctag/design-reviews#802.
-
Early design review for Range API improvements w3ctag/design-reviews#725.
-
FYI - Add optional `submitter` parameter to the `FormData` constructor w3ctag/design-reviews#812.
-
-
35 issues received 63 new comments.
-
early design review: Permissions-Policy: unload w3ctag/design-reviews#738 (5 comments by @cynthia, @fergald)
-
Pre-CR review: DOM Review Draft — Published 21 June 2021 w3ctag/design-reviews#658 (4 comments by @annevk, @LeaVerou, @rhiaro)
-
Early design review for the Topics API w3ctag/design-reviews#726 (3 comments by @michaelkleber, @torgo)
-
FYI - Add optional `submitter` parameter to the `FormData` constructor w3ctag/design-reviews#812 (3 comments by @annevk, @chrishtr, @LeaVerou)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (3 comments by @arnaudbud, @steimelchrome, @tomayac)
-
Review Request for Attribution Reporting API w3ctag/design-reviews#724 (2 comments by @csharrison, @torgo)
-
Design Review: Speculation Rules (Prefetch) w3ctag/design-reviews#721 (2 comments by @kjmcnee, @torgo)
-
The web platform needs a service discovery mechanism w3ctag/design-reviews#240 (2 comments by @hadleybeeman, @plinss)
-
Two changes to Secure Payment Confirmation prior to CR w3ctag/design-reviews#802 (2 comments by @ianbjacobs, @torgo)
-
Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences w3ctag/design-reviews#767 (1 comment by @torgo)
-
Review request on `blocking=render` attribute for scripts and stylesheets w3ctag/design-reviews#727 (1 comment by @plinss)
-
Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 w3ctag/design-reviews#811 (1 comment by @torgo)
-
Pre-CR review: HTML Review Draft — Published 18 January 2021 w3ctag/design-reviews#657 (1 comment by @LeaVerou)
-
VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport w3ctag/design-reviews#768 (1 comment by @rhiaro)
-
w3ctag/bfcache-guide
-
1 issue opened.
-
Missing guidance for handling steps that are run "in parallel" w3ctag/bfcache-guide#2, by @rakina.
-
-
1 issue received 2 new comments.
-
Missing guidance for handling steps that are run "in parallel" w3ctag/bfcache-guide#2 (2 comments by @annevk, @rakina)
-
-
1 pull request opened.
-
Add guide for "in parallel" w3ctag/bfcache-guide#3, by @rakina.
-
-
1 pull request merged.
-
Add "Supporting BFCached Documents" standalone guide w3ctag/bfcache-guide#1.
-
-
2 pull requests received 6 new comments.
-
Add "Supporting BFCached Documents" standalone guide w3ctag/bfcache-guide#1 (3 comments by @annevk, @atanassov, @rakina)
w3ctag/webcomponents-design-guidelines
-
1 issue opened.
-
Naming guidance for parts w3ctag/webcomponents-design-guidelines#10, by @LeaVerou.
-
w3ctag/ethical-web-principles
-
1 issue opened.
-
Discuss macroeconomic impact and equality? w3ctag/ethical-web-principles#92, by @RByers.
-
-
3 issues closed.
-
Complexity as an ethical issue w3ctag/ethical-web-principles#83.
-
Honouring expectations w3ctag/ethical-web-principles#82.
-
Decentralization vs federation w3ctag/ethical-web-principles#54.
-
-
5 issues received 29 new comments.
-
Decentralization vs federation w3ctag/ethical-web-principles#54 (19 comments by @cwilso, @darobin, @dwsinger, @michaelchampion, @torgo)
-
Discuss macroeconomic impact and equality? w3ctag/ethical-web-principles#92 (2 comments by @RByers, @tobie)
-
-
2 pull requests opened.
-
Additions to the web is for all people w3ctag/ethical-web-principles#91, by @rhiaro.
-
First pass of change of purpose w3ctag/ethical-web-principles#90, by @torgo.
-
-
3 pull requests merged.
-
First pass of change of purpose w3ctag/ethical-web-principles#90.
-
Additions to the web is for all people w3ctag/ethical-web-principles#91.
-
Control & power: change decentralized to not centralized for #54 w3ctag/ethical-web-principles#87.
-
-
1 pull request received 4 new comments.
-
First pass of change of purpose w3ctag/ethical-web-principles#90 (4 comments by @mnot, @rhiaro, @torgo)
-
w3ctag/process
-
2 issues opened.
-
Add a "Review: too late" label and corresponding guidance w3ctag/process#29, by @LeaVerou.
-
Introduce editor configs, consistent style across our deliverables w3ctag/process#28, by @cynthia.
-
-
4 issues closed.
-
Document design review lifecycle w3ctag/process#22.
-
www-tag@w3.org list vs Github - suggest updating mailing list blurb w3ctag/process#25.
-
Ensure all specs & standards have published user research? w3ctag/process#26.
-
Look into skynetting the TAG assignment/triage process w3ctag/process#4.
-
-
6 issues received 7 new comments.
-
www-tag@w3.org list vs Github - suggest updating mailing list blurb w3ctag/process#25 (1 comment by @torgo)
w3ctag/tag.w3.org
-
2 pull requests opened.
-
Add Autoplay Policy Detection as an example of a good explainer w3ctag/tag.w3.org#37, by @rhiaro.
-
Added review lifecycle info w3ctag/tag.w3.org#36, by @torgo.
-
-
2 pull requests merged.
-
Added review lifecycle info w3ctag/tag.w3.org#36.
-
Add Autoplay Policy Detection as an example of a good explainer w3ctag/tag.w3.org#37.
-
-
1 pull request reopened.
-
Add Autoplay Policy Detection as an example of a good explainer w3ctag/tag.w3.org#37, by @torgo.
-
-
1 pull request received 6 new comments.
w3ctag/societal-impact-questionnaire
-
1 issue received 1 new comment.
-
Consider encouraging investment in evidence over speculation w3ctag/societal-impact-questionnaire#7 (1 comment by @torgo)
-
-
2 pull requests opened.
-
Question: surveillence (for #3) w3ctag/societal-impact-questionnaire#9, by @rhiaro.
-
Add a paragraph about measurability, for #7 w3ctag/societal-impact-questionnaire#8, by @rhiaro.
-
-
1 pull request merged.
-
Add a paragraph about measurability, for #7 w3ctag/societal-impact-questionnaire#8.
-
-
1 pull request received 1 new comment.
-
Add a paragraph about measurability, for #7 w3ctag/societal-impact-questionnaire#8 (1 comment by @hadleybeeman)
-
GitHub
w3ctag/design-reviews
-
11 issues opened.
-
FYI - Add optional `submitter` parameter to the `FormData` constructor w3ctag/design-reviews#812, by @jenseng.
-
Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 w3ctag/design-reviews#811, by @michael-n-cooper.
-
Autoplay Policy Detection API w3ctag/design-reviews#810, by @alastor0325.
-
WebAssembly JavaScript Promise Integration API w3ctag/design-reviews#809, by @fgmccabe.
-
requestStorageAccessFor w3ctag/design-reviews#808, by @mreichhoff.
-
Storage Access API w3ctag/design-reviews#807, by @johannhof.
-
WebAuthn PRF extension w3ctag/design-reviews#806, by @agl.
-
Moving local files with the File System Access API w3ctag/design-reviews#805, by @a-sully.
-
FedCM multi IDP support w3ctag/design-reviews#803, by @npm1.
-
Two changes to Secure Payment Confirmation prior to CR w3ctag/design-reviews#802, by @ianbjacobs.
-
baseline-source w3ctag/design-reviews#801, by @bfgeek.
-
-
4 issues closed.
-
baseline-source w3ctag/design-reviews#801.
-
UI Events Keyboard Events Key Values review request w3ctag/design-reviews#789.
-
UI Events Keyboard Events Code Values review request w3ctag/design-reviews#790.
-
How should web standards use the new JavaScript Symbol.dispose protocol? w3ctag/design-reviews#794.
-
-
16 issues received 32 new comments.
-
FYI - Add optional `submitter` parameter to the `FormData` constructor w3ctag/design-reviews#812 (5 comments by @annevk, @jenseng, @LeaVerou)
-
Early design review for the Topics API w3ctag/design-reviews#726 (3 comments by @darobin, @rhiaro, @torgo)
-
Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 w3ctag/design-reviews#811 (2 comments by @michael-n-cooper, @torgo)
-
UI Events Keyboard Events Key Values review request w3ctag/design-reviews#789 (2 comments by @LeaVerou, @LJWatson)
-
UI Events Keyboard Events Code Values review request w3ctag/design-reviews#790 (2 comments by @LJWatson, @ylafon)
-
Collection of Screensharing-related UX Hints w3ctag/design-reviews#744 (2 comments by @atanassov, @eladalon1983)
-
Early design review: Document Picture-in-Picture w3ctag/design-reviews#798 (1 comment by @slightlyoff)
-
w3ctag/ethical-web-principles
-
1 issue received 1 new comment.
w3ctag/privacy-principles
-
2 issues opened.
-
Wide Review w3ctag/privacy-principles#217, by @darobin.
-
No need to have both `actors` and `parties` w3ctag/privacy-principles#209, by @darobin.
-
-
12 issues closed.
-
Editorial updates to Identity principle w3ctag/privacy-principles#187.
-
Clarify re-identification through dataset merger w3ctag/privacy-principles#98.
-
How This Document Fits In w3ctag/privacy-principles#168.
-
No need to have both `actors` and `parties` w3ctag/privacy-principles#209.
-
Definitions 2.1 to 2.4 (part) w3ctag/privacy-principles#26.
-
address privacy threat of harassment w3ctag/privacy-principles#188.
-
UAs should support deception principle w3ctag/privacy-principles#174.
-
Clarify audience & how they engage w3ctag/privacy-principles#172.
-
Addition to data minimisation w3ctag/privacy-principles#171.
-
cite finding on unsanctioned tracking w3ctag/privacy-principles#160.
-
distinguishing between sensitive and non-sensitive data w3ctag/privacy-principles#159.
-
Consider adding a section on cross-device tracking w3ctag/privacy-principles#71.
-
-
15 issues received 19 new comments.
-
Be more explicit about PII-based joins across contexts being bad. w3ctag/privacy-principles#194 (2 comments by @jyasskin, @npdoty)
-
Clarify re-identification through dataset merger w3ctag/privacy-principles#98 (2 comments by @darobin, @jyasskin)
-
privacy principles related to purpose-specific APIs w3ctag/privacy-principles#175 (2 comments by @npdoty, @torgo)
-
Don't ask for fake consent, even if real consent is not required w3ctag/privacy-principles#192 (1 comment by @jyasskin)
-
distinguishing between sensitive and non-sensitive data w3ctag/privacy-principles#159 (1 comment by @torgo)
-
when is sharing data for some ancillary purpose consistent with privacy principles? w3ctag/privacy-principles#150 (1 comment by @torgo)
-
Consider adding a section on cross-device tracking w3ctag/privacy-principles#71 (1 comment by @torgo)
-
-
10 pull requests opened.
-
Discovery 156 w3ctag/privacy-principles#219, by @npdoty.
-
Simplify and remove redundant text in the Identity section. w3ctag/privacy-principles#218, by @jyasskin.
-
Revisions and concisions around ancillary data use w3ctag/privacy-principles#216, by @pes10k.
-
Add text on aggregated data w3ctag/privacy-principles#215, by @dmarti.
-
Cite The New Chicago School instead of Code. w3ctag/privacy-principles#214, by @jyasskin.
-
Replace most uses of "party" with "actor", except for 1P, 3P, and 🥳. w3ctag/privacy-principles#213, by @jyasskin.
-
Refine the definition of "context" to avoid re-using "purpose". w3ctag/privacy-principles#212, by @jyasskin.
-
Delete a comment. w3ctag/privacy-principles#211, by @jyasskin.
-
Improve explanation of how this document relates to laws and regulation. w3ctag/privacy-principles#210, by @jyasskin.
-
Welcome to 2023 Editorial Pass w3ctag/privacy-principles#208, by @darobin.
-
-
7 pull requests merged.
-
Cite The New Chicago School instead of Code. w3ctag/privacy-principles#214.
-
Improve explanation of how this document relates to laws and regulation. w3ctag/privacy-principles#210.
-
Replace most uses of "party" with "actor", except for 1P, 3P, and 🥳. w3ctag/privacy-principles#213.
-
Refine the definition of "context" to avoid re-using "purpose". w3ctag/privacy-principles#212.
-
Delete a comment. w3ctag/privacy-principles#211.
-
Tension within anti-profiling designs w3ctag/privacy-principles#158.
-
Welcome to 2023 Editorial Pass w3ctag/privacy-principles#208.
-
-
2 pull requests closed.
-
Add text on aggregated data w3ctag/privacy-principles#215.
-
Allow non-immediate goals in data sharing w3ctag/privacy-principles#162.
-
-
9 pull requests received 73 new comments.
-
Welcome to 2023 Editorial Pass w3ctag/privacy-principles#208 (28 comments by @darobin, @jyasskin, @torgo)
-
Revisions and concisions around ancillary data use w3ctag/privacy-principles#216 (16 comments by @jyasskin, @npdoty, @pes10k, @samuelweiler)
-
Simplify and remove redundant text in the Identity section. w3ctag/privacy-principles#218 (13 comments by @jyasskin, @npdoty)
-
Improve explanation of how this document relates to laws and regulation. w3ctag/privacy-principles#210 (6 comments by @jyasskin, @mnot, @wseltzer)
-
Replace most uses of "party" with "actor", except for 1P, 3P, and 🥳. w3ctag/privacy-principles#213 (1 comment by @darobin)
-
w3ctag/bfcache-guide
-
1 pull request received 9 new comments.
-
Add "Supporting BFCached Documents" standalone guide w3ctag/bfcache-guide#1 (9 comments by @annevk, @rakina)
-
w3ctag/design-principles
-
1 issue received 1 new comment.
-
Should charters link to the TAG design principles? w3ctag/design-principles#407 (1 comment by @svgeesus)
-
-
2 pull requests opened.
-
Clarify that "id" abbreviates "identifier" w3ctag/design-principles#414, by @gibson042.
-
Fix lint issues w3ctag/design-principles#413, by @gibson042.
-
-
1 pull request merged.
-
Clarify that "id" abbreviates "identifier" w3ctag/design-principles#414.
-
-
2 pull requests received 2 new comments.