Technical Architecture Group - Activity in 2017
No matches.
GitHub
w3ctag/polyfills
-
1 issue opened.
-
Advice mentions web platform tests but not test262 w3ctag/polyfills#32, by @JakeChampion.
-
w3ctag/design-reviews
-
2 issues opened.
-
Web Share Target API w3ctag/design-reviews#221, by @mgiuca.
-
Img decoding attribute w3ctag/design-reviews#220, by @vmpstr.
-
-
9 issues received 32 new comments.
-
Sensor APIs w3ctag/design-reviews#207 (15 comments by @alexshalamov, @annevk, @anssiko, @dbaron, @raymeskhoury, @tomrittervg)
-
"With Credentials" flag possibly inconsistent with web architecture w3ctag/design-reviews#76 (7 comments by @annevk, @dbaron, @ylafon)
-
`Accept-CH` header is weird w3ctag/design-reviews#206 (4 comments by @mnot, @slightlyoff, @torgo, @triblondon)
-
w3ctag/design-principles
-
1 pull request received 3 new comments.
-
Describe when features should be limited to secure contexts. w3ctag/design-principles#75 (3 comments by @dbaron)
-
TR publications
-
1 document published.
-
CSS Properties and Values API Level 1 published as a Working Draft. History of CSS Properties and Values API Level 1
-
GitHub
w3ctag/design-principles
-
2 issues opened.
-
Add advice on polyfills w3ctag/design-principles#84, by @triblondon.
-
Add principles for registries w3ctag/design-principles#83, by @triblondon.
-
-
1 pull request merged.
-
Improve wording around time vs. timestamps being monotonically increasing. w3ctag/design-principles#71.
-
-
1 pull request received 3 new comments.
-
Describe when features should be limited to secure contexts. w3ctag/design-principles#75 (3 comments by @annevk, @travisleithead)
-
w3ctag/promises-guide
-
1 issue received 2 new comments.
-
Waiting for promises might not work correctly if the page messes with its standard objects w3ctag/promises-guide#45 (2 comments by @bzbarsky, @ricea)
-
w3ctag/design-reviews
-
9 issues opened.
-
CSS Selectors 4 w3ctag/design-reviews#219, by @victoriasu.
-
Media Capabilities w3ctag/design-reviews#218, by @chcunningham.
-
Web Locks API w3ctag/design-reviews#217, by @inexorabletash.
-
Decentralized identifiers (DIDs) w3ctag/design-reviews#216, by @hadleybeeman.
-
Files and Directory Entries API with webkit prefixes! w3ctag/design-reviews#215, by @cynthia.
-
Dusting off Web Speech API? w3ctag/design-reviews#214, by @travisleithead.
-
<link> rel="modulepreload" w3ctag/design-reviews#213, by @irori.
-
TAG review of Web Audio API (round two) w3ctag/design-reviews#212, by @svgeesus.
-
Transform Streams w3ctag/design-reviews#211, by @ricea.
-
-
3 issues closed.
-
WebAssembly Response API / Web Embedding w3ctag/design-reviews#167.
-
Request review for Scroll Boundary Behavior w3ctag/design-reviews#193.
-
Request review for PauseFrame API w3ctag/design-reviews#196.
-
-
22 issues received 57 new comments.
-
Modeling media auto-playing as a permission? w3ctag/design-reviews#203 (9 comments by @dbaron, @foolip, @mounirlamouri, @slightlyoff)
-
Review OffscreenCanvas, including ImageBitmapRenderingContext w3ctag/design-reviews#141 (7 comments by @juj, @junov, @toji)
-
"With Credentials" flag possibly inconsistent with web architecture w3ctag/design-reviews#76 (5 comments by @dbaron, @mnot, @torgo)
-
Decentralized identifiers (DIDs) w3ctag/design-reviews#216 (4 comments by @cynthia, @dmitrizagidulin, @tantek)
-
WebAssembly Response API / Web Embedding w3ctag/design-reviews#167 (3 comments by @jfbastien, @torgo, @travisleithead)
-
saveData attribute in Network Information API w3ctag/design-reviews#204 (3 comments by @dbaron, @torgo)
-
Request review for Scroll Boundary Behavior w3ctag/design-reviews#193 (3 comments by @dbaron, @majido, @plinss)
-
Serialization of natural language in data formats such as JSON [I18N] w3ctag/design-reviews#178 (3 comments by @aphillips, @dbaron)
-
Request for TAG review of Input events level 2 w3ctag/design-reviews#173 (2 comments by @johanneswilm, @travisleithead)
-
Files and Directory Entries API with webkit prefixes! w3ctag/design-reviews#215 (2 comments by @annevk, @inexorabletash)
-
Web Lifecycle for system initiated Discarding & Stopping w3ctag/design-reviews#205 (1 comment by @torgo)
-
Review of signature-based resource loading restrictions. w3ctag/design-reviews#186 (1 comment by @hadleybeeman)
-
-
1 pull request merged.
-
Editorial: change salutation w3ctag/design-reviews#209.
-
-
1 pull request received 2 new comments.
w3ctag/polyfills
-
1 issue opened.
-
This advice is script centric, needs to consider custom elements' role w3ctag/polyfills#31, by @prushforth.
-
-
1 issue reopened.
-
This advice is script centric, needs to consider custom elements' role w3ctag/polyfills#31, by @prushforth.
-
-
1 issue received 5 new comments.
-
This advice is script centric, needs to consider custom elements' role w3ctag/polyfills#31 (5 comments by @bkardell, @prushforth, @triblondon)
-
GitHub
w3ctag/design-reviews
-
6 issues opened.
-
Consider general storage observer that works for cookies w3ctag/design-reviews#210, by @travisleithead.
-
import.meta.url, and import.meta generally w3ctag/design-reviews#208, by @domenic.
-
Sensor APIs w3ctag/design-reviews#207, by @anssiko.
-
`Accept-CH` header is weird w3ctag/design-reviews#206, by @slightlyoff.
-
Web Lifecycle for system initiated Discarding & Stopping w3ctag/design-reviews#205, by @spanicker.
-
saveData attribute in Network Information API w3ctag/design-reviews#204, by @bengreenstein.
-
-
2 issues closed.
-
Review request for IndexedDB Observers w3ctag/design-reviews#189.
-
Review request for Device Memory API w3ctag/design-reviews#190.
-
-
18 issues received 41 new comments.
-
`Accept-CH` header is weird w3ctag/design-reviews#206 (9 comments by @igrigorik, @mnot, @triblondon)
-
Review OffscreenCanvas, including ImageBitmapRenderingContext w3ctag/design-reviews#141 (7 comments by @juj, @junov, @slightlyoff, @toji, @torgo)
-
Review request for IndexedDB Observers w3ctag/design-reviews#189 (3 comments by @dmurph, @travisleithead)
-
Request review for Scroll Boundary Behavior w3ctag/design-reviews#193 (3 comments by @majido, @tantek)
-
Request for TAG review of Input events level 2 w3ctag/design-reviews#173 (2 comments by @johanneswilm, @travisleithead)
-
Serialization of natural language in data formats such as JSON [I18N] w3ctag/design-reviews#178 (2 comments by @aphillips, @dbaron)
-
"With Credentials" flag possibly inconsistent with web architecture w3ctag/design-reviews#76 (1 comment by @dbaron)
-
Web Lifecycle for system initiated Discarding & Stopping w3ctag/design-reviews#205 (1 comment by @cynthia)
-
-
1 pull request opened.
-
Editorial: change salutation w3ctag/design-reviews#209, by @annevk.
-
w3ctag/design-principles
-
1 issue opened.
-
Synchronous events w3ctag/design-principles#81, by @annevk.
-
-
2 issues received 37 new comments.
-
Explain the *Observer pattern, especially when it is and isn't appropriate w3ctag/design-principles#78 (36 comments by @annevk, @atotic, @dmurph, @domenic, @jakearchibald, @ojanvafai, @smaug----, @szager-chromium, @tabatkins)
-
-
3 pull requests opened.
-
Add section on new features being detectable. w3ctag/design-principles#82, by @dbaron.
-
Classes should have constructors whenever possible w3ctag/design-principles#80, by @domenic.
-
Add a section contrasting events and XObservers w3ctag/design-principles#79, by @domenic.
-
-
1 pull request merged.
-
Add section on new features being detectable. w3ctag/design-principles#82.
-
-
3 pull requests received 29 new comments.
-
Describe when features should be limited to secure contexts. w3ctag/design-principles#75 (19 comments by @dbaron, @jonathanKingston, @mikewest, @ojanvafai)
-
Classes should have constructors whenever possible w3ctag/design-principles#80 (7 comments by @annevk, @marcoscaceres)
-
Add section on new features being detectable. w3ctag/design-principles#82 (3 comments by @annevk, @mikewest)
-
w3ctag/evergreen-web
-
1 issue opened.
-
Typo in section 1 w3ctag/evergreen-web#3, by @LPardue.
-
GitHub
w3ctag/design-principles
-
3 issues opened.
-
Explain the *Observer pattern, especially when it is and isn't appropriate w3ctag/design-principles#78, by @domenic.
-
provide advice on designing subclassable apis w3ctag/design-principles#77, by @dbaron.
-
Sequences vs arrays w3ctag/design-principles#76, by @dbaron.
-
-
3 issues received 7 new comments.
-
Explain the *Observer pattern, especially when it is and isn't appropriate w3ctag/design-principles#78 (5 comments by @annevk, @smaug----, @surma, @szager-chromium)
-
-
1 pull request received 7 new comments.
-
Describe when features should be limited to secure contexts. w3ctag/design-principles#75 (7 comments by @cynthia, @martinthomson, @mikewest, @plinss, @triblondon)
-
w3ctag/design-reviews
-
11 issues opened.
-
Modeling media auto-playing as a permission? w3ctag/design-reviews#203, by @slightlyoff.
-
Request for review: Preload w3ctag/design-reviews#202, by @yoavweiss.
-
JavaScript module import() w3ctag/design-reviews#200, by @domenic.
-
Gesture Delegation w3ctag/design-reviews#199, by @mounirlamouri.
-
Trusted Types w3ctag/design-reviews#198, by @mikewest.
-
Intersection Observer review w3ctag/design-reviews#197, by @LJWatson.
-
Request review for PauseFrame API w3ctag/design-reviews#196, by @jkarlin.
-
ReportingObserver w3ctag/design-reviews#195, by @RByers.
-
Request review for Scroll Boundary Behavior w3ctag/design-reviews#193, by @majido.
-
Request review of Keyboard Lock w3ctag/design-reviews#192, by @garykac.
-
-
9 issues closed.
-
Request for review: Preload w3ctag/design-reviews#202.
-
JavaScript module import() w3ctag/design-reviews#200.
-
Review request for Server-Timing w3ctag/design-reviews#188.
-
WICG Shape Detection API w3ctag/design-reviews#176.
-
Consider template change to add link to WPTs for far-along specs w3ctag/design-reviews#181.
-
Custom Paint API to CR w3ctag/design-reviews#140.
-
Media Capture From DOM Element w3ctag/design-reviews#130.
-
Add request for links to WPT tests in issue template w3ctag/design-reviews#191.
-
Cross-spec device identification & association w3ctag/design-reviews#64.
-
-
39 issues received 143 new comments.
-
Review request for Server-Timing w3ctag/design-reviews#188 (12 comments by @cvazac, @hadleybeeman, @igrigorik, @plinss, @triblondon, @yoavweiss)
-
Request to review Image Decode API w3ctag/design-reviews#182 (10 comments by @annevk, @domenic, @torgo, @triblondon, @vmpstr)
-
"With Credentials" flag possibly inconsistent with web architecture w3ctag/design-reviews#76 (9 comments by @annevk, @dbaron, @mikewest, @torgo, @travisleithead)
-
Request for review: Preload w3ctag/design-reviews#202 (8 comments by @cynthia, @igrigorik, @Krinkle, @plinss, @triblondon, @yoavweiss)
-
Review of signature-based resource loading restrictions. w3ctag/design-reviews#186 (8 comments by @cynthia, @hadleybeeman, @mikewest, @otherdaniel, @plinss, @triblondon)
-
Gesture Delegation w3ctag/design-reviews#199 (6 comments by @dbaron, @domenic, @mounirlamouri, @travisleithead)
-
Review request for Device Memory API w3ctag/design-reviews#190 (5 comments by @cynthia, @plinss, @slightlyoff, @spanicker, @travisleithead)
-
Request for TAG review of Input events level 2 w3ctag/design-reviews#173 (5 comments by @cynthia, @hadleybeeman, @johanneswilm, @travisleithead)
-
Request review of Keyboard Lock w3ctag/design-reviews#192 (4 comments by @annevk, @cynthia, @dbaron)
-
Review request for IndexedDB Observers w3ctag/design-reviews#189 (3 comments by @bsittler, @travisleithead)
-
WebAssembly Response API / Web Embedding w3ctag/design-reviews#167 (3 comments by @cynthia, @littledan, @lukewagner)
-
Review OffscreenCanvas, including ImageBitmapRenderingContext w3ctag/design-reviews#141 (3 comments by @junov, @torgo)
-
Add request for links to WPT tests in issue template w3ctag/design-reviews#191 (3 comments by @plinss, @travisleithead)
-
Consider template change to add link to WPTs for far-along specs w3ctag/design-reviews#181 (2 comments by @dbaron, @torgo)
-
Cross-spec device identification & association w3ctag/design-reviews#64 (2 comments by @jan-ivar, @travisleithead)
-
w3ctag/capability-urls
-
1 issue opened.
-
Easier to leak w3ctag/capability-urls#10, by @annevk.
-
-
1 issue closed.
-
Related work w3ctag/capability-urls#1.
-
-
2 issues received 3 new comments.
-
1 pull request merged.
-
Fix typo w3ctag/capability-urls#9.
-
w3ctag/extensible-web-report-card
-
1 issue opened.
-
Show that this is no longer updated w3ctag/extensible-web-report-card#32, by @torgo.
-
-
25 issues closed.
-
Flesh out parts that are pretty sparse w3ctag/extensible-web-report-card#3.
-
Give more background w3ctag/extensible-web-report-card#4.
-
SVG? w3ctag/extensible-web-report-card#7.
-
Web RTC? w3ctag/extensible-web-report-card#8.
-
Restructure report card? w3ctag/extensible-web-report-card#11.
-
New category: expelled from school w3ctag/extensible-web-report-card#12.
-
Make it clear who the audience is w3ctag/extensible-web-report-card#13.
-
make it clear what it is - that it's a review of existing specs w3ctag/extensible-web-report-card#14.
-
mention storage w3ctag/extensible-web-report-card#15.
-
We need broader community involvement in this document w3ctag/extensible-web-report-card#16.
-
Add some idea of trend - what the trend has been w3ctag/extensible-web-report-card#18.
-
Add WebASM w3ctag/extensible-web-report-card#19.
-
Add permissions API w3ctag/extensible-web-report-card#20.
-
Add webappsec specs into this... w3ctag/extensible-web-report-card#21.
-
More detail on things like CSP w3ctag/extensible-web-report-card#22.
-
Needs a design refresh w3ctag/extensible-web-report-card#23.
-
Private state with Weakmaps? w3ctag/extensible-web-report-card#24.
-
focus styling is disruptive in class. w3ctag/extensible-web-report-card#25.
-
Shadow Dom Movement? w3ctag/extensible-web-report-card#26.
-
In General, how can we show positive movement? w3ctag/extensible-web-report-card#27.
-
Better contribution explanation w3ctag/extensible-web-report-card#28.
-
Object.observe mentions? w3ctag/extensible-web-report-card#29.
-
SRI? w3ctag/extensible-web-report-card#30.
-
Time to transition off this? w3ctag/extensible-web-report-card#31.
-
Show that this is no longer updated w3ctag/extensible-web-report-card#32.
-
-
24 issues received 24 new comments.
-
Flesh out parts that are pretty sparse w3ctag/extensible-web-report-card#3 (1 comment by @travisleithead)
-
New category: expelled from school w3ctag/extensible-web-report-card#12 (1 comment by @travisleithead)
-
make it clear what it is - that it's a review of existing specs w3ctag/extensible-web-report-card#14 (1 comment by @travisleithead)
-
We need broader community involvement in this document w3ctag/extensible-web-report-card#16 (1 comment by @travisleithead)
-
Add some idea of trend - what the trend has been w3ctag/extensible-web-report-card#18 (1 comment by @travisleithead)
-
Add webappsec specs into this... w3ctag/extensible-web-report-card#21 (1 comment by @travisleithead)
-
focus styling is disruptive in class. w3ctag/extensible-web-report-card#25 (1 comment by @travisleithead)
-
In General, how can we show positive movement? w3ctag/extensible-web-report-card#27 (1 comment by @travisleithead)
-
Show that this is no longer updated w3ctag/extensible-web-report-card#32 (1 comment by @travisleithead)
-
w3ctag/tag.w3.org
-
1 issue closed.
-
review working mode against tag charter w3ctag/tag.w3.org#6.
-
-
1 issue received 1 new comment.
w3ctag/webarch
-
7 issues closed.
-
JSON w3ctag/webarch#7.
-
Schema languages w3ctag/webarch#8.
-
TLS and security w3ctag/webarch#9.
-
Evergreen web w3ctag/webarch#10.
-
Diff view w3ctag/webarch#5.
-
Section on polyfills and prollyfills w3ctag/webarch#3.
-
References are broken w3ctag/webarch#1.
-
-
7 issues received 9 new comments.
w3ctag/private-mode
-
15 issues closed.
-
References / sources w3ctag/private-mode#1.
-
Password managers w3ctag/private-mode#2.
-
Sessions w3ctag/private-mode#3.
-
Cookie scoping w3ctag/private-mode#4.
-
ETags w3ctag/private-mode#5.
-
Trust and Intermediaries w3ctag/private-mode#6.
-
HTTP request constraints w3ctag/private-mode#7.
-
JavaScript w3ctag/private-mode#8.
-
"log information" w3ctag/private-mode#9.
-
HSTS / pins w3ctag/private-mode#10.
-
Accessing non-private data in private mode w3ctag/private-mode#11.
-
Impact on people who browse private by default w3ctag/private-mode#12.
-
browsing data vs. configuration w3ctag/private-mode#13.
-
Extensions Private Mode w3ctag/private-mode#14.
-
Taken up on 2 Nov w3ctag/private-mode#15.
-
-
15 issues received 15 new comments.
w3ctag/secure-the-web
-
7 issues closed.
-
Collect use cases for "secure http"... w3ctag/secure-the-web#8.
-
Require TLS from privacy-sensitive APIs w3ctag/secure-the-web#7.
-
Mention X-Frame-Options header w3ctag/secure-the-web#6.
-
Talk about sandboxed iframes w3ctag/secure-the-web#5.
-
Threat modeling w3ctag/secure-the-web#3.
-
Add CSP w3ctag/secure-the-web#2.
-
Fingerprinting? w3ctag/secure-the-web#1.
-
-
7 issues received 7 new comments.
w3ctag/promises-guide
-
1 issue received 2 new comments.
TR publications
-
1 document published.
-
CSS Typed OM Level 1 published as a Working Draft. History of CSS Typed OM Level 1
-
GitHub
w3ctag/design-reviews
-
6 issues opened.
-
Add request for links to WPT tests in issue template w3ctag/design-reviews#191, by @slightlyoff.
-
Review request for Device Memory API w3ctag/design-reviews#190, by @spanicker.
-
Review request for IndexedDB Observers w3ctag/design-reviews#189, by @dmurph.
-
Review request for Server-Timing w3ctag/design-reviews#188, by @cvazac.
-
Review request for ResizeObserver w3ctag/design-reviews#187, by @atotic.
-
Review of signature-based resource loading restrictions. w3ctag/design-reviews#186, by @mikewest.
-
-
1 issue closed.
-
MediaStream Recorder w3ctag/design-reviews#131.
-
-
12 issues received 31 new comments.
-
Review request for ResizeObserver w3ctag/design-reviews#187 (7 comments by @atotic, @dbaron, @slightlyoff)
-
Serialization of natural language in data formats such as JSON [I18N] w3ctag/design-reviews#178 (5 comments by @dbaron, @dwsinger, @r12a)
-
Review request for Server-Timing w3ctag/design-reviews#188 (4 comments by @cvazac, @dbaron, @mnot, @slightlyoff)
-
Review request for Device Memory API w3ctag/design-reviews#190 (2 comments by @hadleybeeman, @spanicker)
-
Request for TAG review of Input events level 2 w3ctag/design-reviews#173 (1 comment by @johanneswilm)
-
Review Request for OpenType Variable Fonts Additions to CSS Fonts Module Level 4 w3ctag/design-reviews#183 (1 comment by @svgeesus)
-
w3ctag/design-principles
-
3 issues opened.
-
Call this design guidelines? w3ctag/design-principles#74, by @annevk.
-
Optional arguments w3ctag/design-principles#73, by @annevk.
-
Give guidance on algorithms w3ctag/design-principles#72, by @annevk.
-
-
2 issues received 3 new comments.
-
Best Practices for Registries (including that they should be machine readable) w3ctag/design-principles#68 (2 comments by @marcoscaceres)
-
-
1 pull request opened.
-
Describe when features should be limited to secure contexts. w3ctag/design-principles#75, by @dbaron.
-
-
1 pull request received 12 new comments.
-
Describe when features should be limited to secure contexts. w3ctag/design-principles#75 (12 comments by @annevk, @dbaron, @jonathanKingston, @mikewest, @travisleithead)
-
w3ctag/distributed-content
-
1 pull request opened.
-
Language tweaks w3ctag/distributed-content#5, by @triblondon.
-
-
1 pull request merged.
-
Language tweaks w3ctag/distributed-content#5.
-
-
1 pull request received 1 new comment.
w3ctag/polyfills
-
1 issue closed.
-
Defer vs name squatting confusion w3ctag/polyfills#30.
-
-
1 issue received 1 new comment.
GitHub
w3ctag/design-principles
-
3 issues opened.
-
Improve guidance for using attributes vs methods w3ctag/design-principles#70, by @plinss.
-
Update section on device IDs based on thinking recorded in design reviews issue w3ctag/design-principles#69, by @torgo.
-
Best Practices for Registries (including that they should be machine readable) w3ctag/design-principles#68, by @torgo.
-
-
3 issues closed.
-
JavaScript is growing multiple numeric types w3ctag/design-principles#23.
-
Casing rules are a bit confusing for properties, especially of dictionaries w3ctag/design-principles#54.
-
Don't list me as editor w3ctag/design-principles#63.
-
-
17 issues received 46 new comments.
-
Best Practices for Registries (including that they should be machine readable) w3ctag/design-principles#68 (9 comments by @cynthia, @hadleybeeman, @marcoscaceres, @torgo, @travisleithead)
-
Need guidance on returning error values vs throwing exceptions w3ctag/design-principles#55 (8 comments by @annevk, @dbaron, @timbl, @torgo, @travisleithead)
-
Avoid exotic objects (e.g. named/indexed getters/setters) w3ctag/design-principles#16 (4 comments by @dbaron, @domenic, @torgo)
-
When should [SecureContext] be used and why? w3ctag/design-principles#32 (3 comments by @dbaron, @hadleybeeman, @torgo)
-
Recommend [Constructor] for creation vs. createXXX() methods w3ctag/design-principles#44 (2 comments by @domenic, @slightlyoff)
-
Make it easy to synthesize objects typically created by the UA? w3ctag/design-principles#51 (2 comments by @domenic, @torgo)
-
WebIDL interfaces should only be used when you have both data and behavior w3ctag/design-principles#11 (2 comments by @dbaron, @travisleithead)
-
Guidance on re-using/creating task sources w3ctag/design-principles#38 (2 comments by @annevk, @travisleithead)
-
JavaScript is growing multiple numeric types w3ctag/design-principles#23 (2 comments by @torgo, @travisleithead)
-
Recommend for/against "is" prefix for boolean APIs? w3ctag/design-principles#53 (2 comments by @torgo)
-
Don't call out synchronously to author code if possible w3ctag/design-principles#18 (1 comment by @travisleithead)
-
Consider pulling feedback from CSSWG into this doc regarding shipping experimental features w3ctag/design-principles#21 (1 comment by @travisleithead)
-
should provide advice on when it's good to return the same object again w3ctag/design-principles#46 (1 comment by @dbaron)
-
-
1 pull request opened.
-
Improve wording around time vs. timestamps being monotonically increasing. w3ctag/design-principles#71, by @dbaron.
-
-
2 pull requests merged.
-
Clarify the casing rules a bit more w3ctag/design-principles#65.
-
Clean up header metadata w3ctag/design-principles#64.
-
w3ctag/distributed-content
-
4 pull requests opened.
-
Fixup another historical origin reference w3ctag/distributed-content#4, by @annevk.
-
MOAR EDITS w3ctag/distributed-content#3, by @slightlyoff.
-
Publish and ratify w3ctag/distributed-content#2, by @triblondon.
-
London F2F changes w3ctag/distributed-content#1, by @triblondon.
-
-
3 pull requests merged.
-
Fixup another historical origin reference w3ctag/distributed-content#4.
-
Publish and ratify w3ctag/distributed-content#2.
-
London F2F changes w3ctag/distributed-content#1.
-
-
1 pull request closed.
-
MOAR EDITS w3ctag/distributed-content#3.
-
w3ctag/design-reviews
-
3 issues opened.
-
Review request for WebVR w3ctag/design-reviews#185, by @toji.
-
Review request for Push API w3ctag/design-reviews#184, by @triblondon.
-
Review Request for OpenType Variable Fonts Additions to CSS Fonts Module Level 4 w3ctag/design-reviews#183, by @drott.
-
-
15 issues closed.
-
Review Request for OpenType Variable Fonts Additions to CSS Fonts Module Level 4 w3ctag/design-reviews#183.
-
TAG review for script type=module w3ctag/design-reviews#180.
-
Review request for Push API w3ctag/design-reviews#184.
-
Budget API (especially reserve() method) w3ctag/design-reviews#169.
-
Request for TAG review of Input Events level 1 w3ctag/design-reviews#160.
-
ARIA w3ctag/design-reviews#107.
-
TAG Review of HTML 5.2 (previously 5.1) w3ctag/design-reviews#119.
-
MediaStream Image Capture w3ctag/design-reviews#133.
-
MediaSession w3ctag/design-reviews#149.
-
TV Control API w3ctag/design-reviews#111.
-
Review Screen Orientation spec prior to CR-entry w3ctag/design-reviews#157.
-
Review ARIA in HTML specification (prior to CR transition) w3ctag/design-reviews#156.
-
Writable Streams w3ctag/design-reviews#163.
-
Request to review First Paint Timing w3ctag/design-reviews#177.
-
WebVR w3ctag/design-reviews#106.
-
-
34 issues received 98 new comments.
-
Serialization of natural language in data formats such as JSON [I18N] w3ctag/design-reviews#178 (15 comments by @aphillips, @dbaron, @dwsinger, @hsivonen, @r12a, @tobie, @torgo, @travisleithead)
-
Review request for Push API w3ctag/design-reviews#184 (6 comments by @chaals, @cynthia, @LJWatson, @torgo, @triblondon)
-
WebAssembly Response API / Web Embedding w3ctag/design-reviews#167 (5 comments by @annevk, @lukewagner, @travisleithead)
-
TV-Specific Web Subsetting w3ctag/design-reviews#105 (4 comments by @hadleybeeman, @jpiesing, @torgo)
-
Timed Text Markup Language 2 (TTML2) w3ctag/design-reviews#138 (4 comments by @astearns, @dbaron, @nigelmegitt)
-
A spec style/structure checklist? w3ctag/design-reviews#136 (3 comments by @marcoscaceres, @slightlyoff, @torgo)
-
Request for TAG review of Input events level 2 w3ctag/design-reviews#173 (3 comments by @dbaron, @torgo)
-
Review Request for OpenType Variable Fonts Additions to CSS Fonts Module Level 4 w3ctag/design-reviews#183 (3 comments by @dbaron)
-
TAG review for script type=module w3ctag/design-reviews#180 (3 comments by @domenic, @slightlyoff, @torgo)
-
Review Screen Orientation spec prior to CR-entry w3ctag/design-reviews#157 (2 comments by @cynthia, @LJWatson)
-
Cross-spec device identification & association w3ctag/design-reviews#64 (1 comment by @travisleithead)
-
Review OffscreenCanvas, including ImageBitmapRenderingContext w3ctag/design-reviews#141 (1 comment by @slightlyoff)
-
Review ARIA in HTML specification (prior to CR transition) w3ctag/design-reviews#156 (1 comment by @triblondon)
-
w3ctag/obsoletion
-
1 issue opened.
-
Make previous versions of HTML and XHTML obsolete w3ctag/obsoletion#1, by @LJWatson.
-
-
1 issue received 1 new comment.
GitHub
w3ctag/design-reviews
-
3 issues opened.
-
Request to review Image Decode API w3ctag/design-reviews#182, by @vmpstr.
-
Consider template change to add link to WPTs for far-along specs w3ctag/design-reviews#181, by @slightlyoff.
-
TAG review for script type=module w3ctag/design-reviews#180, by @KenjiBaheux.
-
-
1 issue closed.
-
Web Share API w3ctag/design-reviews#179.
-
-
14 issues received 44 new comments.
-
Serialization of natural language in data formats such as JSON [I18N] w3ctag/design-reviews#178 (8 comments by @aphillips, @cynthia, @dbaron, @r12a, @torgo)
-
Request to review First Paint Timing w3ctag/design-reviews#177 (5 comments by @dbaron, @domenic, @spanicker)
-
TAG review for script type=module w3ctag/design-reviews#180 (3 comments by @dbaron, @domenic, @torgo)
-
Review Screen Orientation spec prior to CR-entry w3ctag/design-reviews#157 (2 comments by @cynthia, @LJWatson)
-
TAG Review of HTML 5.2 (previously 5.1) w3ctag/design-reviews#119 (2 comments by @chaals, @dwsinger)
-
Review OffscreenCanvas, including ImageBitmapRenderingContext w3ctag/design-reviews#141 (2 comments by @junov, @travisleithead)
-
Consider template change to add link to WPTs for far-along specs w3ctag/design-reviews#181 (1 comment by @torgo)
-
Request for TAG review of Input Events level 1 w3ctag/design-reviews#160 (1 comment by @johanneswilm)
w3ctag/capability-urls
w3ctag/promises-guide
-
1 issue received 4 new comments.
-
Promise-manipulation shorthands have underdefined behavior w3ctag/promises-guide#52 (4 comments by @bzbarsky, @domenic)
-
w3ctag/design-principles
-
1 issue opened.
-
Guidance on wrapper specs w3ctag/design-principles#67, by @cynthia.
-
GitHub
w3ctag/design-reviews
-
4 issues opened.
-
Web Share API w3ctag/design-reviews#179, by @owencm.
-
Serialization of natural language in data formats such as JSON [I18N] w3ctag/design-reviews#178, by @aphillips.
-
Request to review First Paint Timing w3ctag/design-reviews#177, by @spanicker.
-
WICG Shape Detection API w3ctag/design-reviews#176, by @yell0wd0g.
-
-
4 issues closed.
-
Review origin policy. w3ctag/design-reviews#127.
-
SharedArrayBuffer + Atomics w3ctag/design-reviews#165.
-
Review request for Feature Policy w3ctag/design-reviews#159.
-
ViewportAPI naming Re-review w3ctag/design-reviews#172.
-
-
19 issues received 59 new comments.
-
TAG Review of HTML 5.2 (previously 5.1) w3ctag/design-reviews#119 (10 comments by @chaals, @dbaron, @domenic, @plinss)
-
Cross-spec device identification & association w3ctag/design-reviews#64 (5 comments by @kenchris, @travisleithead)
-
WebAssembly Response API / Web Embedding w3ctag/design-reviews#167 (5 comments by @cynthia, @flagxor, @ghost)
-
SharedArrayBuffer + Atomics w3ctag/design-reviews#165 (5 comments by @annevk, @binji, @dbaron, @lars-t-hansen)
-
Serialization of natural language in data formats such as JSON [I18N] w3ctag/design-reviews#178 (3 comments by @aphillips, @domenic, @r12a)
-
Review Screen Orientation spec prior to CR-entry w3ctag/design-reviews#157 (2 comments by @cynthia, @LJWatson)
-
Review OffscreenCanvas, including ImageBitmapRenderingContext w3ctag/design-reviews#141 (1 comment by @dbaron)
-
-
1 pull request opened.
-
README: fix links with spaces to use encoded spaces w3ctag/design-reviews#175, by @odeke-em.
-
-
1 pull request merged.
-
README: fix links with spaces to use encoded spaces w3ctag/design-reviews#175.
-
-
1 pull request received 2 new comments.
-
README: fix links with spaces to use encoded spaces w3ctag/design-reviews#175 (2 comments by @cynthia, @odeke-em)
-
w3ctag/webarch
-
4 issues opened.
-
Evergreen web w3ctag/webarch#10, by @mnot.
-
TLS and security w3ctag/webarch#9, by @mnot.
-
Schema languages w3ctag/webarch#8, by @mnot.
-
w3ctag/design-principles
-
1 issue received 2 new comments.
-
3 pull requests opened.
-
Switch to container-based virtualization for Travis CI. w3ctag/design-principles#66, by @dbaron.
-
Clarify the casing rules a bit more w3ctag/design-principles#65, by @domenic.
-
Clean up header metadata w3ctag/design-principles#64, by @domenic.
-
-
2 pull requests merged.
-
Switch to container-based virtualization for Travis CI. w3ctag/design-principles#66.
-
Suggest use of promises, and point to promises-guide. w3ctag/design-principles#62.
-
-
2 pull requests received 6 new comments.
-
Suggest use of promises, and point to promises-guide. w3ctag/design-principles#62 (5 comments by @dbaron, @domenic)
-
Switch to container-based virtualization for Travis CI. w3ctag/design-principles#66 (1 comment by @dbaron)
-
GitHub
w3ctag/design-reviews
-
10 issues opened.
-
HTML General Review w3ctag/design-reviews#174, by @torgo.
-
Request for TAG review of Input events level 2 w3ctag/design-reviews#173, by @triblondon.
-
ViewportAPI naming Re-review w3ctag/design-reviews#172, by @bokand.
-
Storage persistence and estimation APIs w3ctag/design-reviews#171, by @inexorabletash.
-
Web Share API w3ctag/design-reviews#170, by @owencm.
-
Budget API (especially reserve() method) w3ctag/design-reviews#169, by @owencm.
-
Repo should be renamed (and templates updated) to reflect consulting role of the TAG w3ctag/design-reviews#168, by @slightlyoff.
-
WebAssembly Response API / Web Embedding w3ctag/design-reviews#167, by @flagxor.
-
Navigation Preload for Service Worker w3ctag/design-reviews#166, by @KenjiBaheux.
-
SharedArrayBuffer + Atomics w3ctag/design-reviews#165, by @flagxor.
-
-
16 issues closed.
-
Web Payments Working Group Specifications w3ctag/design-reviews#152.
-
Navigation Preload for Service Worker w3ctag/design-reviews#166.
-
Extensibility of Accessibility w3ctag/design-reviews#63.
-
Performance APIs, Security and Privacy w3ctag/design-reviews#120.
-
ReadableStreams (specs: Streams, Fetch) w3ctag/design-reviews#121.
-
Audio Output Device APIs w3ctag/design-reviews#132.
-
PaymentRequest.canMakeActivePayment() w3ctag/design-reviews#146.
-
Long Task API w3ctag/design-reviews#150.
-
WASM JS API review w3ctag/design-reviews#151.
-
Request for TAG review of CSS Timing Functions spec w3ctag/design-reviews#161.
-
ReadableStream pipeTo() and pipeThrough() w3ctag/design-reviews#164.
-
Web Share API w3ctag/design-reviews#170.
-
Repo should be renamed (and templates updated) to reflect consulting role of the TAG w3ctag/design-reviews#168.
-
Storage persistence and estimation APIs w3ctag/design-reviews#171.
-
KeyBoardEvent 'code' and 'key' spec reviews wanted w3ctag/design-reviews#155.
-
Remote Playback API w3ctag/design-reviews#145.
-
-
49 issues received 148 new comments.
-
Web Payments Working Group Specifications w3ctag/design-reviews#152 (14 comments by @dbaron, @domenic, @ianbjacobs, @travisleithead, @zkoch)
-
Review origin policy. w3ctag/design-reviews#127 (9 comments by @annevk, @dbaron, @domenic, @torgo, @triblondon)
-
Writable Streams w3ctag/design-reviews#163 (9 comments by @dbaron, @domenic, @ricea, @travisleithead, @triblondon)
-
Web payment method manifest w3ctag/design-reviews#162 (7 comments by @dbaron, @RByers, @rsolomakhin, @torgo)
-
Review request for Feature Policy w3ctag/design-reviews#159 (7 comments by @clelland, @dbaron, @ojanvafai, @slightlyoff, @torgo, @triblondon)
-
Repo should be renamed (and templates updated) to reflect consulting role of the TAG w3ctag/design-reviews#168 (6 comments by @bkardell, @mnot, @torgo, @triblondon)
-
SharedArrayBuffer + Atomics w3ctag/design-reviews#165 (5 comments by @annevk, @cynthia, @dbaron, @travisleithead)
-
Request for TAG review of Input Events level 1 w3ctag/design-reviews#160 (5 comments by @cynthia, @johanneswilm, @slightlyoff, @triblondon)
-
Review ARIA in HTML specification (prior to CR transition) w3ctag/design-reviews#156 (5 comments by @cynthia, @dbaron, @slightlyoff, @stevefaulkner)
-
Budget API (especially reserve() method) w3ctag/design-reviews#169 (5 comments by @foolip, @owencm, @slightlyoff, @torgo)
-
TAG Review of HTML 5.2 (previously 5.1) w3ctag/design-reviews#119 (5 comments by @dbaron, @torgo, @travisleithead, @triblondon)
-
Timed Text Markup Language 2 (TTML2) w3ctag/design-reviews#138 (5 comments by @dbaron, @palemieux, @torgo)
-
WebAssembly Response API / Web Embedding w3ctag/design-reviews#167 (3 comments by @cynthia, @torgo, @travisleithead)
-
Navigation Preload for Service Worker w3ctag/design-reviews#166 (3 comments by @jakearchibald, @triblondon)
-
TV-Specific Web Subsetting w3ctag/design-reviews#105 (3 comments by @hadleybeeman, @torgo, @travisleithead)
-
Review Accessibility Object Model w3ctag/design-reviews#134 (3 comments by @dbaron, @LJWatson, @slightlyoff)
-
Review OffscreenCanvas, including ImageBitmapRenderingContext w3ctag/design-reviews#141 (2 comments by @dbaron, @travisleithead)
-
PaymentRequest.canMakeActivePayment() w3ctag/design-reviews#146 (2 comments by @dbaron, @triblondon)
-
Request for TAG review of CSS Timing Functions spec w3ctag/design-reviews#161 (2 comments by @dbaron)
-
ReadableStream pipeTo() and pipeThrough() w3ctag/design-reviews#164 (2 comments by @dbaron, @triblondon)
-
KeyBoardEvent 'code' and 'key' spec reviews wanted w3ctag/design-reviews#155 (2 comments by @torgo, @travisleithead)
-
"With Credentials" flag possibly inconsistent with web architecture w3ctag/design-reviews#76 (1 comment by @annevk)
-
w3ctag/design-principles
-
4 issues opened.
-
Don't list me as editor w3ctag/design-principles#63, by @domenic.
-
Guidelines for binary stream-likes should be added w3ctag/design-principles#56, by @cynthia.
-
Need guidance on returning error values vs throwing exceptions w3ctag/design-principles#55, by @plinss.
-
Casing rules are a bit confusing for properties, especially of dictionaries w3ctag/design-principles#54, by @domenic.
-
-
3 issues closed.
-
Events should be used for notification of actions, not actions themselves w3ctag/design-principles#12.
-
Add accessibility to section 5 w3ctag/design-principles#49.
-
recommend that DOMError should go away, and DOMException can be used as a property w3ctag/design-principles#27.
-
-
1 issue received 1 new comment.
-
6 pull requests opened.
-
Suggest use of promises, and point to promises-guide. w3ctag/design-principles#62, by @dbaron.
-
Add link to advice on internationalization. w3ctag/design-principles#61, by @dbaron.
-
Add links to advice on related topic of specification writing. w3ctag/design-principles#60, by @dbaron.
-
Fix#49 Add link to helpful accessibility checklist w3ctag/design-principles#59, by @travisleithead.
-
Add advice for event design. w3ctag/design-principles#58, by @slightlyoff.
-
Add section on error types, initially about avoiding DOMError, but with a drop more than that. w3ctag/design-principles#57, by @dbaron.
-
-
5 pull requests merged.
-
Add advice for event design. w3ctag/design-principles#58.
-
Add links to advice on related topic of specification writing. w3ctag/design-principles#60.
-
Add link to advice on internationalization. w3ctag/design-principles#61.
-
Fix#49 Add link to helpful accessibility checklist w3ctag/design-principles#59.
-
Add section on error types, initially about avoiding DOMError, but with a drop more than that. w3ctag/design-principles#57.
-
-
2 pull requests received 15 new comments.
-
Add advice for event design. w3ctag/design-principles#58 (14 comments by @annevk, @dbaron, @slightlyoff, @travisleithead)
-
Add links to advice on related topic of specification writing. w3ctag/design-principles#60 (1 comment by @dbaron)
-
w3ctag/meetings
-
1 issue closed.
-
Figure out logistics and setup for a developer meetup in Tokyo w3ctag/meetings#21.
-
-
1 issue received 2 new comments.
-
Figure out logistics and setup for a developer meetup in Tokyo w3ctag/meetings#21 (2 comments by @cynthia)
-
-
1 pull request opened.
-
Add some notes about EME and DMCA w3ctag/meetings#22, by @marcoscaceres.
-
-
1 pull request merged.
-
Add some notes about EME and DMCA w3ctag/meetings#22.
-
GitHub
w3ctag/design-reviews
-
10 issues opened.
-
ReadableStream pipeTo() and pipeThrough() w3ctag/design-reviews#164, by @domenic.
-
Writable Streams w3ctag/design-reviews#163, by @domenic.
-
Web payment method manifest w3ctag/design-reviews#162, by @rsolomakhin.
-
Request for TAG review of CSS Timing Functions spec w3ctag/design-reviews#161, by @suzyh.
-
Request for TAG review of Input Events level 1 w3ctag/design-reviews#160, by @johanneswilm.
-
Review request for Feature Policy w3ctag/design-reviews#159, by @clelland.
-
Android payment app manifest w3ctag/design-reviews#158, by @rsolomakhin.
-
Review Screen Orientation spec prior to CR-entry w3ctag/design-reviews#157, by @travisleithead.
-
Review ARIA in HTML specification (prior to CR transition) w3ctag/design-reviews#156, by @travisleithead.
-
KeyBoardEvent 'code' and 'key' spec reviews wanted w3ctag/design-reviews#155, by @travisleithead.
-
-
2 issues closed.
-
Android payment app manifest w3ctag/design-reviews#158.
-
allow-top-navigation-by-user-activation w3ctag/design-reviews#154.
-
-
10 issues received 19 new comments.
-
Performance APIs, Security and Privacy w3ctag/design-reviews#120 (6 comments by @igrigorik, @plinss, @travisleithead)
-
KeyBoardEvent 'code' and 'key' spec reviews wanted w3ctag/design-reviews#155 (1 comment by @travisleithead)
-
w3ctag/design-principles
-
3 issues opened.
-
Recommend for/against "is" prefix for boolean APIs? w3ctag/design-principles#53, by @domenic.
-
Create launching point into the Performance APIs overview doc w3ctag/design-principles#52, by @travisleithead.
-
Make it easy to synthesize objects typically created by the UA? w3ctag/design-principles#51, by @RByers.
-
-
2 issues received 4 new comments.
-
Make it easy to synthesize objects typically created by the UA? w3ctag/design-principles#51 (3 comments by @domenic, @RByers)
-
Create launching point into the Performance APIs overview doc w3ctag/design-principles#52 (1 comment by @igrigorik)
-
w3ctag/meetings
-
1 issue opened.
-
Figure out logistics and setup for a developer meetup in Tokyo w3ctag/meetings#21, by @cynthia.
-
w3ctag/promises-guide
-
1 issue opened.
-
Updating deploy script w3ctag/promises-guide#54, by @domenic.
-
GitHub
w3ctag/design-reviews
-
5 issues opened.
-
allow-top-navigation-by-user-activation w3ctag/design-reviews#154, by @domenic.
-
IndexedDB 2.0 features review w3ctag/design-reviews#153, by @pwnall.
-
Web Payments Working Group Specifications w3ctag/design-reviews#152, by @ianbjacobs.
-
WASM JS API review w3ctag/design-reviews#151, by @slightlyoff.
-
Long Task API w3ctag/design-reviews#150, by @spanicker.
-
-
11 issues closed.
-
IndexedDB 2.0 features review w3ctag/design-reviews#153.
-
Notifications API w3ctag/design-reviews#94.
-
IFrame support in web payments w3ctag/design-reviews#147.
-
Review of WakeLock API and suitability for overall platform requested by 31 August 2016 w3ctag/design-reviews#126.
-
Review request for Scroll Anchoring w3ctag/design-reviews#142.
-
Ambient Light Sensor API w3ctag/design-reviews#115.
-
Data on the Web Best Practices w3ctag/design-reviews#135.
-
Review OffscreenCanvas w3ctag/design-reviews#144.
-
Browser Fingerprinting Document w3ctag/design-reviews#38.
-
Security Questionnaire w3ctag/design-reviews#77.
-
Geofencing FPWD w3ctag/design-reviews#89.
-
-
31 issues received 67 new comments.
-
IndexedDB 2.0 features review w3ctag/design-reviews#153 (6 comments by @cynthia, @inexorabletash, @pwnall, @slightlyoff)
-
Review of WakeLock API and suitability for overall platform requested by 31 August 2016 w3ctag/design-reviews#126 (6 comments by @andrey-logvinov, @hadleybeeman, @tobie, @triblondon)
-
Review origin policy. w3ctag/design-reviews#127 (4 comments by @hadleybeeman, @mikewest, @mnot, @triblondon)
-
Performance APIs, Security and Privacy w3ctag/design-reviews#120 (4 comments by @hadleybeeman, @igrigorik, @travisleithead)
-
IFrame support in web payments w3ctag/design-reviews#147 (4 comments by @domenic, @travisleithead, @triblondon)
-
A spec style/structure checklist? w3ctag/design-reviews#136 (4 comments by @dbaron, @marcoscaceres, @tobie)
-
Review Accessibility Object Model w3ctag/design-reviews#134 (2 comments by @marcoscaceres, @triblondon)
-
"With Credentials" flag possibly inconsistent with web architecture w3ctag/design-reviews#76 (1 comment by @triblondon)
-
Review OffscreenCanvas, including ImageBitmapRenderingContext w3ctag/design-reviews#141 (1 comment by @dbaron)
-
w3ctag/design-principles
-
6 issues opened.
-
give advice on read-only lists w3ctag/design-principles#50, by @dbaron.
-
Add accessibility to section 5 w3ctag/design-principles#49, by @LJWatson.
-
Editorial: autolink to all cited interfaces/etc. w3ctag/design-principles#48, by @domenic.
-
should provide advice on when it's good to return the same object again w3ctag/design-principles#46, by @dbaron.
-
Recommend [Constructor] for creation vs. createXXX() methods w3ctag/design-principles#44, by @travisleithead.
-
Document when to use allow- attributes vs. extend the sandbox attribute value set for iframes w3ctag/design-principles#41, by @travisleithead.
-
-
7 issues closed.
-
should discuss reasons to provide live vs. static objects w3ctag/design-principles#34.
-
Clarify if event handler attributes need definition (and if so, under what conditions) w3ctag/design-principles#29.
-
Prefer dictionary over a boolean parameter w3ctag/design-principles#28.
-
Grammars vs. parsers w3ctag/design-principles#19.
-
Triage issues that should block a first publication w3ctag/design-principles#26.
-
Add Privacy/permissions related guidance w3ctag/design-principles#37.
-
Web APIs are not in fact just for JavaScript w3ctag/design-principles#22.
-
-
1 issue reopened.
-
When should [SecureContext] be used and why? w3ctag/design-principles#32, by @travisleithead.
-
-
8 issues received 16 new comments.
-
Web APIs are not in fact just for JavaScript w3ctag/design-principles#22 (4 comments by @bzbarsky, @domenic, @slightlyoff, @travisleithead)
-
When should [SecureContext] be used and why? w3ctag/design-principles#32 (3 comments by @annevk, @travisleithead)
-
Add Privacy/permissions related guidance w3ctag/design-principles#37 (2 comments by @torgo, @travisleithead)
-
should provide advice on when it's good to return the same object again w3ctag/design-principles#46 (1 comment by @domenic)
-
Document when to use allow- attributes vs. extend the sandbox attribute value set for iframes w3ctag/design-principles#41 (1 comment by @domenic)
-
Recommend [Constructor] for creation vs. createXXX() methods w3ctag/design-principles#44 (1 comment by @domenic)
-
Triage issues that should block a first publication w3ctag/design-principles#26 (1 comment by @torgo)
-
-
4 pull requests opened.
-
Describe tradeoffs between live and static objects. w3ctag/design-principles#47, by @dbaron.
-
Use bikeshed's syntax highlighting throughout. w3ctag/design-principles#45, by @dbaron.
-
Add advice for event handler attributes. Fix #29 w3ctag/design-principles#43, by @travisleithead.
-
Prefer dictionary to boolean parameters, and other advice related to booleans and dictionaries. w3ctag/design-principles#42, by @dbaron.
-
-
4 pull requests merged.
-
Describe tradeoffs between live and static objects. w3ctag/design-principles#47.
-
Use bikeshed's syntax highlighting throughout. w3ctag/design-principles#45.
-
Add advice for event handler attributes. Fix #29 w3ctag/design-principles#43.
-
Prefer dictionary to boolean parameters, and other advice related to booleans and dictionaries. w3ctag/design-principles#42.
-
-
4 pull requests received 29 new comments.
-
Describe tradeoffs between live and static objects. w3ctag/design-principles#47 (16 comments by @annevk, @bzbarsky, @dbaron, @domenic, @travisleithead)
-
Add advice for event handler attributes. Fix #29 w3ctag/design-principles#43 (6 comments by @domenic, @travisleithead)
-
Prefer dictionary to boolean parameters, and other advice related to booleans and dictionaries. w3ctag/design-principles#42 (4 comments by @dbaron, @domenic)
-
Use bikeshed's syntax highlighting throughout. w3ctag/design-principles#45 (3 comments by @dbaron, @domenic)
-
w3ctag/polyfills
-
5 issues opened.
-
Defer vs name squatting confusion w3ctag/polyfills#30, by @triblondon.
-
About Collecting data w3ctag/polyfills#24, by @torgo.
-
Security Concerns w3ctag/polyfills#23, by @torgo.
-
Risks of premature polyfilling w3ctag/polyfills#22, by @torgo.
-
-
17 issues closed.
-
Encourage use of the script@crossorigin="anonymous" attribute w3ctag/polyfills#15.
-
Encourage subresource integrity for distributors and web devs w3ctag/polyfills#14.
-
Encourage script@defer w3ctag/polyfills#12.
-
A Disappointing Document w3ctag/polyfills#8.
-
On defering to native implementations w3ctag/polyfills#2.
-
add more detail to mootools and createShadowRoot examples w3ctag/polyfills#16.
-
About rAF w3ctag/polyfills#25.
-
About Collecting data w3ctag/polyfills#24.
-
Security Concerns w3ctag/polyfills#23.
-
Risks of premature polyfilling w3ctag/polyfills#22.
-
Console warning for polyfills which have a native implementation necessary? w3ctag/polyfills#7.
-
Discussion on "Do not serve polyfills that are not required by the user" w3ctag/polyfills#9.
-
Discussion on "Don't create globals with common names for speculative polyfills" w3ctag/polyfills#13.
-
Talk about caching w3ctag/polyfills#10.
-
Library example w3ctag/polyfills#3.
-
Advice for library authors who use polyfills? w3ctag/polyfills#6.
-
Naming for speculative polyfills vs prollyfills w3ctag/polyfills#1.
-
-
15 issues received 54 new comments.
-
On defering to native implementations w3ctag/polyfills#2 (22 comments by @annevk, @bkardell, @domenic, @mathiasbynens, @slightlyoff, @triblondon)
-
add more detail to mootools and createShadowRoot examples w3ctag/polyfills#16 (6 comments by @bzbarsky, @dbaron, @dglazkov, @triblondon)
-
Advice for library authors who use polyfills? w3ctag/polyfills#6 (4 comments by @jacobangel, @nolanlawson, @triblondon)
-
Console warning for polyfills which have a native implementation necessary? w3ctag/polyfills#7 (3 comments by @cynthia, @triblondon)
-
Encourage subresource integrity for distributors and web devs w3ctag/polyfills#14 (3 comments by @triblondon)
-
Discussion on "Do not serve polyfills that are not required by the user" w3ctag/polyfills#9 (3 comments by @DavidBruant, @triblondon)
-
Encourage use of the script@crossorigin="anonymous" attribute w3ctag/polyfills#15 (2 comments by @triblondon)
-
Discussion on "Don't create globals with common names for speculative polyfills" w3ctag/polyfills#13 (1 comment by @triblondon)
-
-
7 pull requests opened.
-
Approve finding w3ctag/polyfills#29, by @triblondon.
-
Add advice for spec editors w3ctag/polyfills#28, by @triblondon.
-
Add some detail to initial examples, fixes #16 w3ctag/polyfills#27, by @triblondon.
-
Feature detection wordsmithing, example w3ctag/polyfills#26, by @triblondon.
-
Caching w3ctag/polyfills#21, by @triblondon.
-
First pass at advice for library authors, fixes #6 w3ctag/polyfills#20, by @triblondon.
-
Add an example of using a speculative polyfill in private scope, closes #3 w3ctag/polyfills#19, by @triblondon.
-
-
8 pull requests merged.
-
Approve finding w3ctag/polyfills#29.
-
Add advice for spec editors w3ctag/polyfills#28.
-
Add some detail to initial examples, fixes #16 w3ctag/polyfills#27.
-
Add an example of using a speculative polyfill in private scope, closes #3 w3ctag/polyfills#19.
-
Feature detection wordsmithing, example w3ctag/polyfills#26.
-
Caching w3ctag/polyfills#21.
-
First pass at advice for library authors, fixes #6 w3ctag/polyfills#20.
-
Rework nomenclature, fixes #1 w3ctag/polyfills#18.
-
-
5 pull requests received 6 new comments.
-
First pass at advice for library authors, fixes #6 w3ctag/polyfills#20 (2 comments by @nolanlawson, @triblondon)
-
Add an example of using a speculative polyfill in private scope, closes #3 w3ctag/polyfills#19 (1 comment by @triblondon)
-
w3ctag/evergreen-web
-
1 issue opened.
-
Ship the Evergreen Web Finding w3ctag/evergreen-web#1, by @travisleithead.
-
-
1 issue closed.
-
Ship the Evergreen Web Finding w3ctag/evergreen-web#1.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Make finding official w3ctag/evergreen-web#2, by @dbaron.
-
-
1 pull request merged.
-
Make finding official w3ctag/evergreen-web#2.
-
w3ctag/tag.w3.org
-
2 pull requests opened.
-
Update tagcodeofconduct.md w3ctag/tag.w3.org#10, by @triblondon.
-
spelling and editorial w3ctag/tag.w3.org#9, by @wseltzer.
-
-
1 pull request merged.
-
Update tagcodeofconduct.md w3ctag/tag.w3.org#10.
-
-
1 pull request closed.
-
spelling and editorial w3ctag/tag.w3.org#9.
-
-
1 pull request received 1 new comment.
GitHub
w3ctag/polyfills
-
11 issues opened.
-
add more detail to mootools and createShadowRoot examples w3ctag/polyfills#16, by @dbaron.
-
Encourage use of the script@crossorigin="anonymous" attribute w3ctag/polyfills#15, by @DavidBruant.
-
Encourage subresource integrity for distributors and web devs w3ctag/polyfills#14, by @DavidBruant.
-
Discussion on "Don't create globals with common names for speculative polyfills" w3ctag/polyfills#13, by @DavidBruant.
-
Encourage script@defer w3ctag/polyfills#12, by @DavidBruant.
-
Provide a definition of a polyfill w3ctag/polyfills#11, by @DavidBruant.
-
Talk about caching w3ctag/polyfills#10, by @DavidBruant.
-
Discussion on "Do not serve polyfills that are not required by the user" w3ctag/polyfills#9, by @DavidBruant.
-
A Disappointing Document w3ctag/polyfills#8, by @WebReflection.
-
Console warning for polyfills which have a native implementation necessary? w3ctag/polyfills#7, by @cynthia.
-
Advice for library authors who use polyfills? w3ctag/polyfills#6, by @nolanlawson.
-
-
3 issues closed.
-
Discourage UA sniffing w3ctag/polyfills#4.
-
Provide a definition of a polyfill w3ctag/polyfills#11.
-
Suggest a non-JS experience w3ctag/polyfills#5.
-
-
13 issues received 82 new comments.
-
Advice for library authors who use polyfills? w3ctag/polyfills#6 (38 comments by @dmethvin, @Draggha, @fregante, @georgezzhang, @hzoo, @Jessidhia, @nolanlawson, @palmerj3, @reconbot, @Rich-Harris, @sokra, @TheLarkInn, @tomccabe, @triblondon)
-
On defering to native implementations w3ctag/polyfills#2 (23 comments by @annevk, @dbaron, @domenic, @mathiasbynens, @tobie, @triblondon)
-
Encourage subresource integrity for distributors and web devs w3ctag/polyfills#14 (4 comments by @DavidBruant, @dbaron, @JakeChampion, @triblondon)
-
Discussion on "Don't create globals with common names for speculative polyfills" w3ctag/polyfills#13 (1 comment by @triblondon)
-
Discussion on "Do not serve polyfills that are not required by the user" w3ctag/polyfills#9 (1 comment by @triblondon)
-
Console warning for polyfills which have a native implementation necessary? w3ctag/polyfills#7 (1 comment by @triblondon)
-
-
2 pull requests opened.
-
Rework nomenclature, fixes #1 w3ctag/polyfills#18, by @triblondon.
-
Rework naming w3ctag/polyfills#17, by @triblondon.
-
-
1 pull request closed.
-
Rework naming w3ctag/polyfills#17.
-
-
2 pull requests received 3 new comments.
w3ctag/capability-urls
w3ctag/design-principles
-
2 issues opened.
-
Be sure the document recommends feature-detection w3ctag/design-principles#40, by @travisleithead.
-
Non privacy related design notes on device APIs w3ctag/design-principles#39, by @cynthia.
-
-
5 issues closed.
-
Tracking, privacy, fingerprinting and user consent w3ctag/design-principles#13.
-
Naming things… w3ctag/design-principles#14.
-
Socially-Motivated Web Design Principles w3ctag/design-principles#8.
-
Can we change the title to say "web API"? w3ctag/design-principles#20.
-
Clarify the scope so that it's clear that this is "JavaScript" APIs (vs. Network-based APIs) w3ctag/design-principles#33.
-
-
9 issues received 25 new comments.
-
When should [SecureContext] be used and why? w3ctag/design-principles#32 (8 comments by @annevk, @mikewest, @sleevi, @slightlyoff)
-
Web APIs are not in fact just for JavaScript w3ctag/design-principles#22 (6 comments by @annevk, @bzbarsky, @slightlyoff, @torgo)
-
Tracking, privacy, fingerprinting and user consent w3ctag/design-principles#13 (2 comments by @torgo)
-
JavaScript is growing multiple numeric types w3ctag/design-principles#23 (1 comment by @travisleithead)
-
Clarify the scope so that it's clear that this is "JavaScript" APIs (vs. Network-based APIs) w3ctag/design-principles#33 (1 comment by @travisleithead)
-
w3ctag/design-reviews
-
1 issue opened.
-
MediaSession w3ctag/design-reviews#149, by @xxyzzzq.
-
-
2 issues received 2 new comments.
-
Review of WakeLock API and suitability for overall platform requested by 31 August 2016 w3ctag/design-reviews#126 (1 comment by @dontcallmedom)
-
w3ctag/promises-guide
-
1 pull request merged.
-
Update some links w3ctag/promises-guide#53.
-