Web Performance Working Group - Activity in 2020
No matches.
Lifecycle
-
1 charter extension.
-
Charter extended until 28 February 2021.
-
Participants
-
1 chair stepped down.
-
Ilya Grigorik stepped down as a chair.
-
-
1 participant joined.
-
Yanling Feng (Shenzhen University of Information Technology（深圳信息职业技术大学）) joined.
-
-
1 organization joined.
-
Shenzhen University of Information Technology（深圳信息职业技术大学） joined.
-
GitHub
w3c/largest-contentful-paint
-
3 issues opened.
-
Elements that are obscured by other elements shouldn't be considered w3c/largest-contentful-paint#70, by @patrickhulce.
-
How to handle ties? w3c/largest-contentful-paint#69, by @jonsneyers.
-
Reward progressive images w3c/largest-contentful-paint#68, by @jonsneyers.
-
-
1 issue reopened.
-
Reward progressive images w3c/largest-contentful-paint#68, by @jonsneyers.
-
-
3 issues received 59 new comments.
-
Reward progressive images w3c/largest-contentful-paint#68 (57 comments by @addyosmani, @anniesullie, @eeeps, @gunta, @jonsneyers, @jyrkialakuijala, @kornelski, @mo271, @npm1, @vsekhar, @yoavweiss)
-
Elements that are obscured by other elements shouldn't be considered w3c/largest-contentful-paint#70 (1 comment by @npm1)
-
w3c/reporting
-
2 issues opened.
-
Should reports be visible to extensions? w3c/reporting#223, by @clelland.
-
Spec should be clear about requiring extensions to declare observability w3c/reporting#222, by @clelland.
-
-
1 issue closed.
-
Privacy concerns regarding Reporting API w3c/reporting#169.
-
-
2 issues received 26 new comments.
-
Reporting API should be opt-in w3c/reporting#168 (13 comments by @arturjanc, @clelland, @dcreager, @pes10k, @samuelweiler)
-
Privacy concerns regarding Reporting API w3c/reporting#169 (13 comments by @annevk, @clelland, @neilstuartcraig, @pes10k, @yoavweiss)
-
-
1 pull request closed.
-
remove garbage collection. fixes #23 w3c/reporting#38.
-
w3c/server-timing
-
1 issue received 1 new comment.
w3c/resource-timing
-
2 issues opened.
-
Rationalize Resource-Timing opt-ins with CORS/CORP w3c/resource-timing#240, by @yoavweiss.
-
Why not consider to add "fetchStart" event? w3c/resource-timing#239, by @imtaotao.
-
-
2 issues received 9 new comments.
-
transferSize might reveal HttpOnly cookies w3c/resource-timing#238 (5 comments by @annevk, @bdekoz, @nicjansma, @rniwa)
-
Rationalize Resource-Timing opt-ins with CORS/CORP w3c/resource-timing#240 (4 comments by @annevk, @camillelamy, @mikewest)
-
w3c/event-timing
-
1 issue opened.
-
toJSON() shouldn't include target attribute w3c/event-timing#97, by @sefeng211.
-
-
1 issue received 1 new comment.
w3c/performance-timeline
-
1 issue received 1 new comment.
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (1 comment by @bokand)
-
w3c/longtasks
-
1 pull request merged.
-
Change longtask duration granularity w3c/longtasks#90.
-
-
1 pull request received 2 new comments.
w3c/navigation-timing
-
1 issue received 2 new comments.
-
Possibility to get the HTTP status code from the Response Header ? w3c/navigation-timing#126 (2 comments by @clelland, @nicjansma)
-
-
1 pull request received 4 new comments.
Participants
-
2 participants joined.
-
Keiko Itakura (Rakuten Group, Inc.) joined.
-
Lucas Pardue (Cloudflare) joined.
-
-
1 organization joined.
-
Rakuten Group, Inc. joined.
-
GitHub
w3c/navigation-timing
-
1 issue opened.
-
a bit confused with the "Redirect" timing in Time Navigation w3c/navigation-timing#132, by @ThierryMajutec.
-
-
3 issues received 7 new comments.
-
a bit confused with the "Redirect" timing in Time Navigation w3c/navigation-timing#132 (3 comments by @nicjansma, @ThierryMajutec)
-
What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? w3c/navigation-timing#124 (3 comments by @asutherland, @jakearchibald)
-
-
1 pull request received 14 new comments.
-
workerStart and redirects w3c/navigation-timing#131 (14 comments by @nicjansma, @npm1, @toddreifsteck)
-
w3c/longtasks
-
1 issue opened.
-
Generic model for causal attribution (non-sampling based) w3c/longtasks#89, by @patrickhulce.
-
-
1 issue received 2 new comments.
-
Generic model for causal attribution (non-sampling based) w3c/longtasks#89 (2 comments by @npm1, @patrickhulce)
-
-
2 pull requests opened.
-
Use GitHub Actions w3c/longtasks#91, by @npm1.
-
Change longtask duration granularity w3c/longtasks#90, by @npm1.
-
-
1 pull request merged.
-
Use GitHub Actions w3c/longtasks#91.
-
-
2 pull requests received 7 new comments.
w3c/paint-timing
-
1 pull request opened.
-
Use GitHub Actions w3c/paint-timing#88, by @npm1.
-
-
1 pull request merged.
-
Use GitHub Actions w3c/paint-timing#88.
-
-
1 pull request received 2 new comments.
w3c/device-memory
-
2 issues opened.
-
Should define header value as an sf-decimal w3c/device-memory#33, by @clelland.
-
cite client hints i-d w3c/device-memory#32, by @samuelweiler.
-
-
2 issues closed.
-
Should define header value as an sf-decimal w3c/device-memory#33.
-
cite client hints i-d w3c/device-memory#32.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Client Hints and Structured Field Values references w3c/device-memory#34, by @yoavweiss.
-
-
1 pull request merged.
-
Client Hints and Structured Field Values references w3c/device-memory#34.
-
-
1 pull request received 2 new comments.
-
Client Hints and Structured Field Values references w3c/device-memory#34 (2 comments by @clelland, @yoavweiss)
-
w3c/largest-contentful-paint
-
1 issue closed.
-
Investigate element removal w3c/largest-contentful-paint#41.
-
-
3 pull requests opened.
-
Use GitHub Actions w3c/largest-contentful-paint#67, by @npm1.
-
Remove confusing double is w3c/largest-contentful-paint#66, by @npm1.
-
Allow removed content w3c/largest-contentful-paint#65, by @npm1.
-
-
3 pull requests merged.
-
Use GitHub Actions w3c/largest-contentful-paint#67.
-
Remove confusing double is w3c/largest-contentful-paint#66.
-
Allow removed content w3c/largest-contentful-paint#65.
-
-
1 pull request received 3 new comments.
w3c/event-timing
-
1 pull request opened.
-
Uge GitHub Actions w3c/event-timing#96, by @npm1.
-
-
1 pull request merged.
-
Uge GitHub Actions w3c/event-timing#96.
-
w3c/element-timing
-
3 pull requests opened.
-
Use GitHub Actions w3c/element-timing#53, by @npm1.
-
Bail out earlier on non-annotated elements w3c/element-timing#51, by @npm1.
-
-
2 pull requests merged.
-
Use GitHub Actions w3c/element-timing#53.
-
Typo w3c/element-timing#52.
-
-
1 pull request closed.
-
Bail out earlier on non-annotated elements w3c/element-timing#51.
-
-
2 pull requests received 3 new comments.
w3c/resource-timing
-
2 issues opened.
-
transferSize might reveal HttpOnly cookies w3c/resource-timing#238, by @annevk.
-
Are fetchStart, connectStart, redirectStart relative to navigationStart? w3c/resource-timing#237, by @Nithanaroy.
-
-
1 issue closed.
-
Should onresourcetimingbufferfull be called all the time when unhandled? w3c/resource-timing#231.
-
-
3 issues received 14 new comments.
-
Are fetchStart, connectStart, redirectStart relative to navigationStart? w3c/resource-timing#237 (8 comments by @nicjansma, @Nithanaroy, @npm1)
-
transferSize might reveal HttpOnly cookies w3c/resource-timing#238 (5 comments by @marcelduran, @rniwa, @yoavweiss)
-
Should onresourcetimingbufferfull be called all the time when unhandled? w3c/resource-timing#231 (1 comment by @npm1)
-
w3c/network-error-logging
-
1 pull request opened.
-
Update WG ReSpec config w3c/network-error-logging#128, by @clelland.
-
-
1 pull request merged.
-
Update WG ReSpec config w3c/network-error-logging#128.
-
w3c/perf-timing-primer
-
1 issue opened.
-
is this doc normative or not? w3c/perf-timing-primer#21, by @samuelweiler.
-
-
1 issue received 3 new comments.
-
is this doc normative or not? w3c/perf-timing-primer#21 (3 comments by @samuelweiler, @siusin, @yoavweiss)
-
TR publications
-
2 documents published.
-
Resource Hints published as a Working Draft. History of Resource Hints
-
High Resolution Time published as a First Public Working Draft. History of High Resolution Time
-
Participants
-
6 participants joined.
-
Nicolas Dubus (Meta) joined.
-
Matt Falkenhagen (Google LLC) joined.
-
Caio Gondim (The New York Times) joined.
-
Matthew DeLambo (The New York Times) joined.
-
Justin Heideman (The New York Times) joined.
-
Michal Mocny (Google LLC) joined.
-
-
1 organization joined.
-
The New York Times joined.
-
GitHub
w3c/reporting
-
3 issues opened.
-
Can we do anything mechanical about capability URLs? w3c/reporting#221, by @clelland.
-
"Queue a task" needs a task source. w3c/reporting#220, by @clelland.
-
What is the correct media type? w3c/reporting#217, by @hongbo-miao.
-
-
11 issues closed.
-
Are include_subdomains configurations allowed for raw IPs? w3c/reporting#160.
-
Remove "nel" example from standard text w3c/reporting#167.
-
Reporting-Endpoints processing w3c/reporting#199.
-
superdomain match for origin is bogus w3c/reporting#156.
-
Abstract needs updating w3c/reporting#200.
-
Document vs ECMAScript global environment w3c/reporting#205.
-
Remove all references to ECMAScript global environment w3c/reporting#208.
-
Support for CSP Frame Ancestor violation reports w3c/reporting#203.
-
Consider credential-less reporting w3c/reporting#161.
-
What is the correct media type? w3c/reporting#217.
-
7 issues received 13 new comments.
-
Remove all references to ECMAScript global environment w3c/reporting#208 (4 comments by @clelland, @domenic)
-
Clarify input to HTTP-JFV in "Parse reporting endpoint tuples from _value_" w3c/reporting#12 (1 comment by @clelland)
-
-
2 pull requests opened.
-
Clean up subdomain match logic w3c/reporting#219, by @clelland.
-
fix(docs): Content-Type should be application/reports+json w3c/reporting#218, by @hongbo-miao.
-
-
4 pull requests merged.
-
Clean up subdomain match logic w3c/reporting#219.
-
Add support for workers w3c/reporting#206.
-
Disallow credentials from cross-origin reports w3c/reporting#186.
-
fix(docs): Content-Type should be application/reports+json w3c/reporting#218.
-
-
2 pull requests closed.
-
Clean up subdomain match logic w3c/reporting#163.
-
Remove include_subdomains flag and associated machinery w3c/reporting#170.
-
-
6 pull requests received 29 new comments.
-
fix(docs): Content-Type should be application/reports+json w3c/reporting#218 (2 comments by @clelland, @hongbo-miao)
-
Disallow credentials from cross-origin reports w3c/reporting#186 (2 comments by @clelland, @jyasskin)
w3c/largest-contentful-paint
-
1 issue opened.
-
Offscreen elements should be considered once they enter the viewport? w3c/largest-contentful-paint#61, by @patrickhulce.
-
-
2 issues received 4 new comments.
-
Offscreen elements should be considered once they enter the viewport? w3c/largest-contentful-paint#61 (3 comments by @npm1, @patrickhulce)
-
-
3 pull requests opened.
-
Update explainer to include content removal w3c/largest-contentful-paint#64, by @npm1.
-
Revert "Remove redundant "is"" w3c/largest-contentful-paint#63, by @yoavweiss.
-
Remove redundant "is" w3c/largest-contentful-paint#62, by @akanshgulati.
-
-
3 pull requests merged.
-
Update explainer to include content removal w3c/largest-contentful-paint#64.
-
Revert "Remove redundant "is"" w3c/largest-contentful-paint#63.
-
Remove redundant "is" w3c/largest-contentful-paint#62.
-
-
2 pull requests received 8 new comments.
-
Remove redundant "is" w3c/largest-contentful-paint#62 (7 comments by @akanshgulati, @npm1, @yoavweiss)
-
w3c/resource-timing
-
2 issues received 2 new comments.
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119 (1 comment by @marcelduran)
-
w3c/navigation-timing
-
2 issues received 2 new comments.
-
What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? w3c/navigation-timing#124 (1 comment by @makotoshimazu)
-
-
1 pull request received 11 new comments.
-
workerStart and redirects w3c/navigation-timing#131 (11 comments by @mfalken, @nicjansma, @npm1, @toddreifsteck, @wanderview)
-
w3c/hr-time
-
4 issues opened.
-
Add sub-millisecond timer use-cases w3c/hr-time#101, by @yoavweiss.
-
Expose "unsafe now" for internal uses w3c/hr-time#99, by @yoavweiss.
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Add a use cases section w3c/hr-time#103, by @yoavweiss.
-
Upgraded config for automatic publishing w3c/hr-time#98, by @plehegar.
-
-
1 pull request merged.
-
Upgraded config for automatic publishing w3c/hr-time#98.
-
-
3 pull requests received 26 new comments.
-
Limit the timer resolution in non-isolated contexts w3c/hr-time#93 (10 comments by @annevk, @yoavweiss)
w3c/user-timing
-
2 pull requests opened.
-
Explain diff with hr-time w3c/user-timing#77, by @npm1.
-
Explain API usage in README w3c/user-timing#76, by @npm1.
-
-
2 pull requests merged.
-
Explain diff with hr-time w3c/user-timing#77.
-
Explain API usage in README w3c/user-timing#76.
-
-
2 pull requests received 6 new comments.
w3c/element-timing
-
1 issue closed.
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Pass global object to current high res time w3c/element-timing#50, by @npm1.
-
-
1 pull request merged.
-
Pass global object to current high res time w3c/element-timing#50.
-
w3c/longtasks
-
1 issue opened.
-
Should LongTasks from same-origin same-event-loop tabs be reported? w3c/longtasks#88, by @yoavweiss.
-
-
1 issue closed.
-
Privacy & Security mitigations should not be in an external document w3c/longtasks#85.
-
-
1 pull request merged.
-
Add security/privacy considerations from doc w3c/longtasks#87.
-
-
1 pull request received 26 new comments.
TR publications
-
1 document published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
1 Team contact appointed.
-
Carine Bournez became a Team contact.
-
-
2 Team contacts stepped down.
-
Philippe Le Hegaret stepped down as a Team contact.
-
Xiaoqian Wu stepped down as a Team contact.
-
-
4 participants joined.
-
Bhavin Patel (Meta) joined.
-
Noah Lemen (Meta) joined.
-
Mark Hahnenberg (Meta) joined.
-
Peter Perlepes (W3C Invited Experts) joined.
-
-
1 participant left.
-
Pan Deng (Intel Corporation) left.
-
-
1 organization joined.
-
China Mobile Communications Corporation joined.
-
GitHub
w3c/performance-timeline
-
1 issue opened.
-
Hard to feature-detect observe() parameters w3c/performance-timeline#176, by @npm1.
-
-
1 issue closed.
-
Define buffering behaviors & hooks for queued (PerformanceObserver) entries w3c/performance-timeline#81.
-
-
3 issues received 5 new comments.
-
Fire Paint Timing events for soft navigations w3c/performance-timeline#168 (3 comments by @npm1, @wycats, @yoavweiss)
-
Define buffering behaviors & hooks for queued (PerformanceObserver) entries w3c/performance-timeline#81 (1 comment by @npm1)
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (1 comment by @npm1)
-
-
1 pull request opened.
-
Add dfn to performance timeline task source w3c/performance-timeline#175, by @npm1.
-
-
1 pull request merged.
-
Add dfn to performance timeline task source w3c/performance-timeline#175.
-
w3c/hr-time
-
1 issue opened.
-
Comments on "Define 'relative high resolution time'" w3c/hr-time#96, by @annevk.
-
-
1 issue closed.
-
1 issue reopened.
-
Comments on "Define 'relative high resolution time'" w3c/hr-time#96, by @yoavweiss.
-
-
3 issues received 12 new comments.
-
Comments on "Define 'relative high resolution time'" w3c/hr-time#96 (10 comments by @annevk, @igneel64, @npm1, @yoavweiss)
-
Provide hook for getting a high resolution time between time origin and a "time" w3c/hr-time#87 (1 comment by @igneel64)
-
-
4 pull requests opened.
-
Define 'relative high resolution time' w3c/hr-time#95, by @igneel64.
-
Add a <dfn> for "high resolution time" w3c/hr-time#94, by @mmocny.
-
Limit the timer resolution in non-isolated contexts w3c/hr-time#93, by @yoavweiss.
-
2 pull requests merged.
-
Define 'relative high resolution time' w3c/hr-time#95.
-
1 pull request closed.
-
Add a <dfn> for "high resolution time" w3c/hr-time#94.
-
-
1 pull request reopened.
-
Limit the timer resolution in non-isolated contexts w3c/hr-time#93, by @yoavweiss.
-
-
4 pull requests received 48 new comments.
-
Define 'relative high resolution time' w3c/hr-time#95 (15 comments by @igneel64, @mmocny, @yoavweiss)
-
Limit the timer resolution in non-isolated contexts w3c/hr-time#93 (14 comments by @annevk, @domenic, @npm1, @yoavweiss, @yutakahirano)
-
Correct algorithm definition & 'current high resolution time' reform - Fixes #96 w3c/hr-time#97 (10 comments by @annevk, @igneel64, @yoavweiss)
-
w3c/longtasks
-
1 issue closed.
-
1 issue received 1 new comment.
-
Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? w3c/longtasks#41 (1 comment by @npm1)
-
-
2 pull requests opened.
-
Add security/privacy considerations from doc w3c/longtasks#87, by @npm1.
-
Add dfn for event loop and browsing context w3c/longtasks#86, by @npm1.
-
-
1 pull request merged.
-
Add dfn for event loop and browsing context w3c/longtasks#86.
-
-
1 pull request received 7 new comments.
w3c/navigation-timing
-
2 issues closed.
-
Definition of "back_forward" navigation type does not make sense w3c/navigation-timing#115.
-
Can hitting enter on address bar to same URL be considered a navigation of type 'reload'? w3c/navigation-timing#116.
-
-
4 issues received 5 new comments.
-
Definition of "back_forward" navigation type does not make sense w3c/navigation-timing#115 (2 comments by @npm1, @yoavweiss)
-
workerStart should be clearly defined as applicable to the last SW w3c/navigation-timing#100 (1 comment by @nicjansma)
-
-
3 pull requests opened.
-
workerStart and redirects w3c/navigation-timing#131, by @nicjansma.
-
Use PP2017 w3c/navigation-timing#130, by @plehegar.
-
Point navigation type values to HTML spec's new history handling w3c/navigation-timing#129, by @gi11es.
-
-
2 pull requests merged.
-
Use PP2017 w3c/navigation-timing#130.
-
Point navigation type values to HTML spec's new history handling w3c/navigation-timing#129.
-
-
1 pull request reopened.
-
workerStart and redirects w3c/navigation-timing#131, by @npm1.
-
-
1 pull request received 13 new comments.
-
workerStart and redirects w3c/navigation-timing#131 (13 comments by @nicjansma, @npm1, @toddreifsteck)
-
w3c/resource-timing
-
3 issues opened.
-
Point "current time" definition to hr-time "current high resolution time" algorithm w3c/resource-timing#235, by @igneel64.
-
ResourceTiming Test Triage 9/2020 w3c/resource-timing#233, by @nicjansma.
-
Should onresourcetimingbufferfull be called all the time when unhandled? w3c/resource-timing#231, by @npm1.
-
-
1 issue closed.
-
The step to queue a task to run fire a buffer full event should specify its source w3c/resource-timing#215.
-
-
5 issues received 11 new comments.
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119 (5 comments by @jakearchibald, @makotoshimazu, @mfalken, @yoavweiss)
-
Provide a TAO-bypass for Navigation timing w3c/resource-timing#220 (3 comments by @caribouW3, @yoavweiss)
-
The step to queue a task to run fire a buffer full event should specify its source w3c/resource-timing#215 (1 comment by @rniwa)
-
Should onresourcetimingbufferfull be called all the time when unhandled? w3c/resource-timing#231 (1 comment by @yoavweiss)
-
-
3 pull requests opened.
-
Conform 'current time' definition to the current hr-time spec w3c/resource-timing#236, by @igneel64.
-
Respec update w3c/resource-timing#234, by @plehegar.
-
Add task source to queue a task w3c/resource-timing#232, by @npm1.
-
-
2 pull requests merged.
-
Respec update w3c/resource-timing#234.
-
Add task source to queue a task w3c/resource-timing#232.
-
-
3 pull requests received 10 new comments.
-
Conform 'current time' definition to the current hr-time spec w3c/resource-timing#236 (6 comments by @igneel64, @yoavweiss)
-
Pass realm when creating PerformanceResourceTiming w3c/resource-timing#225 (2 comments by @annevk, @yoavweiss)
-
w3c/element-timing
-
1 issue opened.
-
Point "current high resolution time" definition to hr-time "current high resolution time" algorithm w3c/element-timing#49, by @igneel64.
-
-
1 issue received 1 new comment.
w3c/largest-contentful-paint
-
1 issue opened.
-
Can LCP exceed PLT w3c/largest-contentful-paint#60, by @ThierryMajutec.
-
-
1 issue closed.
-
Can LCP exceed PLT w3c/largest-contentful-paint#60.
-
-
3 issues received 6 new comments.
-
Can LCP exceed PLT w3c/largest-contentful-paint#60 (4 comments by @anniesullie, @npm1, @ThierryMajutec)
-
"Contentful style-background-images" definition is too vague to be relied upon? w3c/largest-contentful-paint#55 (1 comment by @npm1)
-
Call back to indicate that the observer is about to stop w3c/largest-contentful-paint#43 (1 comment by @npm1)
-
-
1 pull request opened.
-
Update index.bs w3c/largest-contentful-paint#59, by @npm1.
-
-
1 pull request closed.
-
Update index.bs w3c/largest-contentful-paint#59.
-
-
1 pull request received 2 new comments.
w3c/user-timing
-
1 issue opened.
-
Clarify behavior when `detail` is omitted from `PerformanceMeasureOptions` w3c/user-timing#74, by @samweinig.
-
-
1 issue closed.
-
Clarify behavior when `detail` is omitted from `PerformanceMeasureOptions` w3c/user-timing#74.
-
-
1 pull request opened.
-
Query if detail is present w3c/user-timing#75, by @npm1.
-
-
1 pull request merged.
-
Query if detail is present w3c/user-timing#75.
-
-
1 pull request received 1 new comment.
w3c/event-timing
-
1 issue closed.
-
The definition of first input is imprecise & lacking w3c/event-timing#91.
-
-
1 issue received 2 new comments.
-
The definition of first input is imprecise & lacking w3c/event-timing#91 (2 comments by @npm1, @rniwa)
-
TR publications
-
2 documents published.
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
User Timing Level 3 published as a Working Draft. History of User Timing Level 3
-
Participants
-
2 participants joined.
-
Carine Bournez (W3C) joined.
-
Jinxin She (Alibaba Group) joined.
-
GitHub
w3c/reporting
-
1 issue opened.
-
Report body interfaces w3c/reporting#216, by @domenic.
-
-
1 issue received 7 new comments.
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/reporting#215, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/reporting#215.
-
-
1 pull request received 1 new comment.
w3c/resource-timing
-
1 issue opened.
-
[Question] What happens when the resource timing entries buffer is full? w3c/resource-timing#230, by @Nithanaroy.
-
-
1 issue closed.
-
[Question] What happens when the resource timing entries buffer is full? w3c/resource-timing#230.
-
-
4 issues received 6 new comments.
-
[Question] What happens when the resource timing entries buffer is full? w3c/resource-timing#230 (3 comments by @Nithanaroy, @npm1, @yoavweiss)
-
Would like a precise way to map PerformanceTimings to FetchEvent w3c/resource-timing#259 (1 comment by @marcelduran)
-
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage w3c/resource-timing#222 (1 comment by @rniwa)
-
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/resource-timing#229, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/resource-timing#229.
-
w3c/event-timing
-
5 issues opened.
-
CFC: adopt to WebPerfWG as a Working Draft w3c/event-timing#94, by @yoavweiss.
-
Address accessibility issues w3c/event-timing#92, by @npm1.
-
The definition of first input is imprecise & lacking w3c/event-timing#91, by @rniwa.
-
Event's delay is rather vague w3c/event-timing#90, by @smaug----.
-
It is surprising that 'wheel' event is exluded from the event timing w3c/event-timing#89, by @smaug----.
-
-
6 issues closed.
-
Add a note to caution about meaningfulness of first event w3c/event-timing#50.
-
Event Timing spec is up! w3c/event-timing#47.
-
"Queuing other entries" section is confusing w3c/event-timing#34.
-
Scrolling Event w3c/event-timing#23.
-
Specify async EventCounts updating w3c/event-timing#19.
-
Original Event as attribute w3c/event-timing#9.
-
-
8 issues received 18 new comments.
-
CFC: adopt to WebPerfWG as a Working Draft w3c/event-timing#94 (3 comments by @cwilso, @marcoscaceres, @yoavweiss)
-
The definition of first input is imprecise & lacking w3c/event-timing#91 (3 comments by @npm1, @rniwa)
-
It is surprising that 'wheel' event is exluded from the event timing w3c/event-timing#89 (1 comment by @npm1)
-
2 pull requests opened.
-
Update should add PerformanceEventTiming w3c/event-timing#95, by @npm1.
-
Expand introduction in spec w3c/event-timing#93, by @npm1.
-
-
2 pull requests merged.
-
Update should add PerformanceEventTiming w3c/event-timing#95.
-
Expand introduction in spec w3c/event-timing#93.
-
-
1 pull request received 12 new comments.
w3c/server-timing
-
1 issue opened.
-
Server-Timing is too limited in scope, rename to Server-Metrics w3c/server-timing#77, by @plutora-steve-g.
-
-
1 issue received 1 new comment.
w3c/largest-contentful-paint
-
3 issues opened.
-
Does display:none need special-casing? w3c/largest-contentful-paint#58, by @npm1.
-
CFC: adopt to WebPerfWG as a Working Draft w3c/largest-contentful-paint#57, by @yoavweiss.
-
Why 'has dispatched scroll event' depends on whether untrusted scroll events have been dispatched? w3c/largest-contentful-paint#56, by @smaug----.
-
-
2 issues received 8 new comments.
-
Why 'has dispatched scroll event' depends on whether untrusted scroll events have been dispatched? w3c/largest-contentful-paint#56 (7 comments by @npm1, @smaug----)
-
"Contentful style-background-images" definition is too vague to be relied upon? w3c/largest-contentful-paint#55 (1 comment by @seanw)
-
w3c/hr-time
-
2 issues received 4 new comments.
-
Make high resolution time dependant on cross-origin isolated w3c/hr-time#89 (2 comments by @npm1, @yoavweiss)
-
Security and privacy considerations for DOMHighResTimeStamp resolution w3c/hr-time#79 (2 comments by @npm1, @rniwa)
-
w3c/requestidlecallback
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/requestidlecallback#89, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/requestidlecallback#89.
-
w3c/user-timing
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/user-timing#73, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/user-timing#73.
-
w3c/performance-timeline
-
1 issue closed.
-
Determining if the buffer was full when using the buffered flag w3c/performance-timeline#169.
-
-
1 issue received 1 new comment.
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (1 comment by @rniwa)
-
-
4 pull requests opened.
-
Editorial: Align with Web IDL specification w3c/performance-timeline#174, by @autokagami.
-
Check shouldAdd when appending to buffer w3c/performance-timeline#173, by @npm1.
-
Add hasDroppedEntry to explainer w3c/performance-timeline#172, by @npm1.
-
Add boolean unbufferedEntry to observe() w3c/performance-timeline#171, by @npm1.
-
-
4 pull requests merged.
-
Editorial: Align with Web IDL specification w3c/performance-timeline#174.
-
Check shouldAdd when appending to buffer w3c/performance-timeline#173.
-
Add hasDroppedEntry to explainer w3c/performance-timeline#172.
-
Add boolean unbufferedEntry to observe() w3c/performance-timeline#171.
-
-
1 pull request received 4 new comments.
-
Add boolean unbufferedEntry to observe() w3c/performance-timeline#171 (4 comments by @npm1, @yoavweiss)
-
w3c/timing-entrytypes-registry
-
1 pull request opened.
-
Expand `should add entry` to perf timeline w3c/timing-entrytypes-registry#15, by @npm1.
-
-
1 pull request merged.
-
Expand `should add entry` to perf timeline w3c/timing-entrytypes-registry#15.
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
1 issue opened.
-
worker start needs to be added to diagram w3c/navigation-timing#128, by @pauljroy.
-
-
2 issues received 5 new comments.
-
worker start needs to be added to diagram w3c/navigation-timing#128 (4 comments by @nicjansma, @npm1, @yoavweiss)
-
Definition of "back_forward" navigation type does not make sense w3c/navigation-timing#115 (1 comment by @paulirish)
-
w3c/element-timing
-
1 issue opened.
-
CFC: adopt to WebPerfWG as a Working Draft w3c/element-timing#48, by @yoavweiss.
-
TR publications
-
1 document published.
-
Server Timing published as a Working Draft. History of Server Timing
-
Participants
-
3 participants joined.
-
Ziran Sun (Igalia) joined.
-
Rob Buis (Igalia) joined.
-
Jean-Guilhem Rouel (W3C) joined.
-
-
2 participants left.
-
Qingqian Tao (Baidu, Inc.) left.
-
Jean-Guilhem Rouel (W3C) left.
-
-
1 organization joined.
-
Igalia joined.
-
GitHub
w3c/performance-timeline
-
1 issue opened.
-
Determining if the buffer was full when using the buffered flag w3c/performance-timeline#169, by @nicjansma.
-
-
1 issue closed.
-
Is the observer buffer of a PerformanceObserver a PerformanceObserverEntryList or a PerformanceEntryList? w3c/performance-timeline#167.
-
-
1 issue received 2 new comments.
-
Determining if the buffer was full when using the buffered flag w3c/performance-timeline#169 (2 comments by @nicjansma, @npm1)
-
-
1 pull request opened.
-
Add entry list to PerformanceObserverEntryList w3c/performance-timeline#170, by @npm1.
-
-
1 pull request merged.
-
Add entry list to PerformanceObserverEntryList w3c/performance-timeline#170.
-
w3c/hr-time
-
1 issue received 1 new comment.
-
Make high resolution time dependant on cross-origin isolated w3c/hr-time#89 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
chore: fix ReSpec related errors w3c/hr-time#92, by @sidvishnoi.
-
-
1 pull request merged.
-
chore: fix ReSpec related errors w3c/hr-time#92.
-
-
1 pull request received 1 new comment.
w3c/resource-timing
-
1 issue opened.
-
Timing-Allow-Origin may expose allowed URLs w3c/resource-timing#228, by @noamr.
-
-
1 issue received 4 new comments.
-
Timing-Allow-Origin may expose allowed URLs w3c/resource-timing#228 (4 comments by @noamr, @npm1, @yoavweiss)
-
w3c/server-timing
-
1 pull request opened.
-
chore: fix default toJSON linking error w3c/server-timing#76, by @sidvishnoi.
-
-
1 pull request merged.
-
chore: fix default toJSON linking error w3c/server-timing#76.
-
-
1 pull request received 1 new comment.
w3c/largest-contentful-paint
-
1 issue opened.
-
"Contentful style-background-images" definition is too vague to be relied upon? w3c/largest-contentful-paint#55, by @seanw.
-
-
1 issue received 5 new comments.
-
"Contentful style-background-images" definition is too vague to be relied upon? w3c/largest-contentful-paint#55 (5 comments by @npm1, @seanw)
-
w3c/perf-timing-primer
-
1 pull request opened.
-
chore: fix ReSpec related errors w3c/perf-timing-primer#20, by @sidvishnoi.
-
-
1 pull request merged.
-
chore: fix ReSpec related errors w3c/perf-timing-primer#20.
-
w3c/event-timing
-
2 issues opened.
-
Add a normative definition for first input delay (FID) w3c/event-timing#87, by @fred-wang.
-
Clarify arbitrary constants in the spec w3c/event-timing#86, by @fred-wang.
-
-
1 issue closed.
-
Add a normative definition for first input delay (FID) w3c/event-timing#87.
-
-
2 issues received 2 new comments.
-
Add a normative definition for first input delay (FID) w3c/event-timing#87 (1 comment by @fred-wang)
-
-
1 pull request opened.
-
Add dfn for first input delay w3c/event-timing#88, by @npm1.
-
-
1 pull request merged.
-
Add dfn for first input delay w3c/event-timing#88.
-
w3c/network-error-logging
-
1 issue received 1 new comment.
w3c/reporting
-
1 pull request opened.
-
Editorial: align with Fetch's structured field changes w3c/reporting#214, by @annevk.
-
-
1 pull request merged.
-
Editorial: align with Fetch's structured field changes w3c/reporting#214.
-
-
1 pull request received 2 new comments.
-
Editorial: align with Fetch's structured field changes w3c/reporting#214 (2 comments by @annevk, @clelland)
-
w3c/navigation-timing
-
1 issue received 2 new comments.
-
What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? w3c/navigation-timing#124 (2 comments by @wanderview, @yoavweiss)
-
w3c/element-timing
-
1 issue opened.
-
Support canvas element for element timing w3c/element-timing#47, by @nhelfman.
-
-
1 issue received 1 new comment.
Lifecycle
-
1 charter extension.
-
Charter extended until 31 December 2020.
-
Participants
-
3 participants joined.
-
Chris Harrelson (Google LLC) joined.
-
Dominic Farolino (Google LLC) joined.
-
Noam Helfman (Microsoft Corporation) joined.
-
-
1 participant left.
-
Dominic Farolino (Google LLC) left.
-
-
1 organization joined.
-
Cloudflare joined.
-
GitHub
w3c/navigation-timing
-
2 issues received 2 new comments.
-
What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? w3c/navigation-timing#124 (1 comment by @wanderview)
-
Possibility to get the HTTP status code from the Response Header ? w3c/navigation-timing#126 (1 comment by @mmocny)
-
w3c/server-timing
-
1 issue closed.
-
Using Server-timing to carry TraceID w3c/server-timing#65.
-
-
1 issue received 1 new comment.
w3c/web-performance
-
1 pull request opened.
-
Fix spelling and capitalization errors in historical HAR spec w3c/web-performance#31, by @stevennyman.
-
-
1 pull request merged.
-
Fix spelling and capitalization errors in historical HAR spec w3c/web-performance#31.
-
w3c/performance-timeline
-
1 issue opened.
-
Fire Paint Timing events for soft navigations w3c/performance-timeline#168, by @dwsmart.
-
-
1 issue received 2 new comments.
-
Fire Paint Timing events for soft navigations w3c/performance-timeline#168 (2 comments by @dwsmart, @npm1)
-
w3c/paint-timing
-
1 issue closed.
-
1 issue received 2 new comments.
-
surprising (if not understandable) results for first-paint when `document.visibilityState === 'hidden'` w3c/paint-timing#40 (2 comments by @mikesherov, @npm1)
-
w3c/reporting
-
1 issue opened.
-
Please fix the build w3c/reporting#213, by @annevk.
-
-
1 issue closed.
-
Please fix the build w3c/reporting#213.
-
-
1 issue received 4 new comments.
-
2 pull requests opened.
-
Remove webdriver-spec.html from WebDriver URLs w3c/reporting#212, by @foolip.
-
Meta: make "queue a report" linkable w3c/reporting#211, by @domenic.
-
-
2 pull requests merged.
-
Remove webdriver-spec.html from WebDriver URLs w3c/reporting#212.
-
Meta: make "queue a report" linkable w3c/reporting#211.
-
-
1 pull request received 3 new comments.
w3c/event-timing
-
1 issue closed.
-
First input should ignore events before First Contentful Paint? w3c/event-timing#84.
-
-
1 issue received 2 new comments.
-
First input should ignore events before First Contentful Paint? w3c/event-timing#84 (2 comments by @npm1)
-
-
1 pull request opened.
-
Update duration description w3c/event-timing#85, by @npm1.
-
-
1 pull request merged.
-
Update duration description w3c/event-timing#85.
-
-
1 pull request received 4 new comments.
w3c/largest-contentful-paint
-
1 issue received 3 new comments.
-
Reset LCP for Single Page App soft navigations w3c/largest-contentful-paint#6 (3 comments by @Guillaume-Nx, @npm1)
-
Participants
-
1 organization joined.
-
The Washington Post joined.
-
GitHub
w3c/event-timing
-
1 issue opened.
-
First input should ignore events before First Contentful Paint? w3c/event-timing#84, by @patrickhulce.
-
-
1 issue received 4 new comments.
-
First input should ignore events before First Contentful Paint? w3c/event-timing#84 (4 comments by @npm1, @patrickhulce)
-
w3c/user-timing
-
1 issue closed.
-
2 issues received 5 new comments.
-
Allow performance.measure() to specify optional color parameter, to be used by perf visualizations in devtools w3c/user-timing#69 (3 comments by @mathiasbynens, @npm1, @yoavweiss)
-
Allow marks and measures to be shown in developer tooling without adding it to the performance timeline w3c/user-timing#68 (2 comments by @mathiasbynens, @yoavweiss)
-
w3c/navigation-timing
-
1 issue reopened.
-
Possibility to get the HTTP status code from the Response Header ? w3c/navigation-timing#126, by @npm1.
-
-
1 issue received 3 new comments.
-
Possibility to get the HTTP status code from the Response Header ? w3c/navigation-timing#126 (3 comments by @bripkens, @JohnRiv, @nicjansma)
-
w3c/network-error-logging
-
1 issue opened.
-
Proposal: Include certificate fingerprint(s) in NEL reports w3c/network-error-logging#127, by @ivanr.
-
-
2 issues received 4 new comments.
-
Proposal: Include certificate fingerprint(s) in NEL reports w3c/network-error-logging#127 (3 comments by @ivanr, @neilstuartcraig)
-
w3c/paint-timing
-
1 issue received 14 new comments.
-
surprising (if not understandable) results for first-paint when `document.visibilityState === 'hidden'` w3c/paint-timing#40 (14 comments by @marcusdarmstrong, @mikesherov, @npm1, @yoavweiss)
-
w3c/reporting
-
1 issue opened.
-
Incorrect timestamp format in the example report w3c/reporting#209, by @ivanr.
-
-
1 issue closed.
-
Incorrect timestamp format in the example report w3c/reporting#209.
-
-
2 issues received 4 new comments.
-
Incorrect timestamp format in the example report w3c/reporting#209 (3 comments by @clelland, @ivanr)
-
-
1 pull request opened.
-
Fix sample reports. w3c/reporting#210, by @aaronshim.
-
-
1 pull request merged.
-
Fix sample reports. w3c/reporting#210.
-
-
1 pull request received 1 new comment.
w3c/hr-time
-
1 issue opened.
-
Export definition of DOMHighResTimeStamp w3c/hr-time#90, by @hober.
-
-
1 issue closed.
-
Export definition of DOMHighResTimeStamp w3c/hr-time#90.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Export DOMHighResTimeStamp w3c/hr-time#91, by @npm1.
-
-
1 pull request merged.
-
Export DOMHighResTimeStamp w3c/hr-time#91.
-
w3c/performance-timeline
-
1 issue opened.
-
Is the observer buffer of a PerformanceObserver a PerformanceObserverEntryList or a PerformanceEntryList? w3c/performance-timeline#167, by @joyeecheung.
-
-
2 issues received 2 new comments.
-
Is the observer buffer of a PerformanceObserver a PerformanceObserverEntryList or a PerformanceEntryList? w3c/performance-timeline#167 (1 comment by @npm1)
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (1 comment by @npm1)
-
w3c/resource-timing
-
1 issue received 11 new comments.
-
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage w3c/resource-timing#222 (11 comments by @marcelduran, @npm1, @pes10k, @yoavweiss)
-
-
1 pull request received 2 new comments.
-
Surface failed fetches in the performance timeline w3c/resource-timing#19 (2 comments by @eligrey, @npm1)
-
w3c/largest-contentful-paint
-
1 issue closed.
-
LCP appears on the popup after mousemove interaction w3c/largest-contentful-paint#50.
-
-
1 issue received 1 new comment.
-
LCP appears on the popup after mousemove interaction w3c/largest-contentful-paint#50 (1 comment by @npm1)
-
TR publications
-
3 documents published.
-
Server Timing published twice as a Working Draft. History of Server Timing
-
User Timing Level 3 published as a Working Draft. History of User Timing Level 3
-
Participants
-
2 participants joined.
-
Neil Craig (British Broadcasting Corporation) joined.
-
Chris Needham (British Broadcasting Corporation) joined.
-
-
1 organization joined.
-
British Broadcasting Corporation joined.
-
GitHub
w3c/server-timing
-
2 issues opened.
-
Respec errors w3c/server-timing#73, by @yoavweiss.
-
API for fetching other metadata w3c/server-timing#72, by @hauleth.
-
-
1 issue closed.
-
Respec errors w3c/server-timing#73.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
chore: fix ReSpec linking error w3c/server-timing#74, by @sidvishnoi.
-
-
2 pull requests merged.
-
chore: update ReSpec syntax and error fixes w3c/server-timing#70.
-
chore: fix ReSpec linking error w3c/server-timing#74.
-
-
2 pull requests received 6 new comments.
-
chore: update ReSpec syntax and error fixes w3c/server-timing#70 (2 comments by @marcoscaceres, @yoavweiss)
w3c/network-error-logging
-
4 issues opened.
-
HTTP error types w3c/network-error-logging#126, by @neilstuartcraig.
-
Event severity and alerting w3c/network-error-logging#125, by @neilstuartcraig.
-
Path-based sampling w3c/network-error-logging#124, by @neilstuartcraig.
-
Respec errors w3c/network-error-logging#123, by @yoavweiss.
-
-
1 issue closed.
-
Respec errors w3c/network-error-logging#123.
-
-
5 issues received 18 new comments.
-
HTTP error types w3c/network-error-logging#126 (6 comments by @aaronpeters, @dcreager, @neilstuartcraig)
-
Event severity and alerting w3c/network-error-logging#125 (5 comments by @aaronpeters, @dcreager, @neilstuartcraig)
-
Path-based sampling w3c/network-error-logging#124 (4 comments by @aaronpeters, @dcreager, @neilstuartcraig)
-
Are user initiated aborts a network failure? w3c/network-error-logging#108 (1 comment by @aaronpeters)
-
-
1 pull request merged.
-
Editorial: fix some ReSpec issues w3c/network-error-logging#118.
-
w3c/timing-entrytypes-registry
-
1 issue opened.
-
Registry should define algorithm for observer vs entry w3c/timing-entrytypes-registry#12, by @npm1.
-
-
2 issues closed.
-
Registry should define algorithm for observer vs entry w3c/timing-entrytypes-registry#12.
-
registry stability w3c/timing-entrytypes-registry#5.
-
-
3 pull requests opened.
-
Update "should add entry" for Event Timing w3c/timing-entrytypes-registry#14, by @npm1.
-
Add column for algorithm of observer vs entry w3c/timing-entrytypes-registry#13, by @npm1.
-
Better define updates to the registry w3c/timing-entrytypes-registry#11, by @npm1.
-
-
3 pull requests merged.
-
Update "should add entry" for Event Timing w3c/timing-entrytypes-registry#14.
-
Add column for algorithm of observer vs entry w3c/timing-entrytypes-registry#13.
-
Better define updates to the registry w3c/timing-entrytypes-registry#11.
-
-
1 pull request received 3 new comments.
-
Add column for algorithm of observer vs entry w3c/timing-entrytypes-registry#13 (3 comments by @npm1, @yoavweiss)
-
w3c/event-timing
-
7 pull requests opened.
-
Remove monkey patch of PerformanceTimeline w3c/event-timing#83, by @npm1.
-
Custom duration threshold support w3c/event-timing#82, by @npm1.
-
Exclude pointerrawupdate in explainer w3c/event-timing#81, by @npm1.
-
Update event types in spec w3c/event-timing#80, by @npm1.
-
Set EventCounts map w3c/event-timing#79, by @npm1.
-
Update explainer to include target w3c/event-timing#78, by @npm1.
-
Add support for Target in spec w3c/event-timing#77, by @npm1.
-
-
8 pull requests merged.
-
Remove monkey patch of PerformanceTimeline w3c/event-timing#83.
-
Custom duration threshold support w3c/event-timing#82.
-
Update event types in spec w3c/event-timing#80.
-
Exclude pointerrawupdate in explainer w3c/event-timing#81.
-
Set EventCounts map w3c/event-timing#79.
-
Update explainer to include target w3c/event-timing#78.
-
Add support for Target in spec w3c/event-timing#77.
-
Add EventCounts example w3c/event-timing#76.
-
-
3 pull requests received 8 new comments.
w3c/performance-timeline
-
1 issue opened.
-
performance.timing obsoleted: What should web developers use instead? w3c/performance-timeline#165, by @sideshowbarker.
-
-
3 issues closed.
-
performance.timing obsoleted: What should web developers use instead? w3c/performance-timeline#165.
-
Queue the entry should require a global object as input w3c/performance-timeline#162.
-
Use of "SyntaxError" seems incorrect, should be TypeError w3c/performance-timeline#163.
-
-
5 issues received 9 new comments.
-
performance.timing obsoleted: What should web developers use instead? w3c/performance-timeline#165 (4 comments by @npm1, @sideshowbarker, @yoavweiss)
-
Queue the entry should require a global object as input w3c/performance-timeline#162 (1 comment by @npm1)
-
Use of "SyntaxError" seems incorrect, should be TypeError w3c/performance-timeline#163 (1 comment by @npm1)
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (1 comment by @noamr)
-
-
2 pull requests opened.
-
Use should add entry algorithm w3c/performance-timeline#166, by @npm1.
-
Do not use SyntaxError w3c/performance-timeline#164, by @npm1.
-
-
2 pull requests merged.
-
Use should add entry algorithm w3c/performance-timeline#166.
-
Do not use SyntaxError w3c/performance-timeline#164.
-
-
1 pull request received 2 new comments.
w3c/reporting
-
3 issues opened.
-
Remove all references to ECMAScript global environment w3c/reporting#208, by @domenic.
-
Setup auto-publishing w3c/reporting#207, by @yoavweiss.
-
Document vs ECMAScript global environment w3c/reporting#205, by @bakulf.
-
-
2 issues received 7 new comments.
-
1 pull request opened.
-
Add support for workers w3c/reporting#206, by @clelland.
-
-
2 pull requests received 4 new comments.
w3c/user-timing
-
1 issue opened.
-
Respec errors w3c/user-timing#71, by @yoavweiss.
-
-
1 issue closed.
-
Respec errors w3c/user-timing#71.
-
-
1 pull request opened.
-
Editorial: xref fixes w3c/user-timing#72, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: xref fixes w3c/user-timing#72.
-
w3c/navigation-timing
-
1 issue opened.
-
Respec errors w3c/navigation-timing#127, by @yoavweiss.
-
-
1 issue closed.
-
Respec errors w3c/navigation-timing#127.
-
-
1 issue received 1 new comment.
w3c/longtasks
-
2 issues opened.
-
Privacy & Security mitigations should not be in an external document w3c/longtasks#85, by @yoavweiss.
-
Attribution for alert() or other tasks blocked by user input w3c/longtasks#83, by @npm1.
-
-
2 issues closed.
-
Top-level browsing context scoping w3c/longtasks#75.
-
-
1 issue reopened.
-
Event loop timing reporting seems to ignore reentrancy w3c/longtasks#76, by @npm1.
-
-
3 issues received 12 new comments.
-
Top-level browsing context scoping w3c/longtasks#75 (7 comments by @annevk, @domenic, @nicjansma, @npm1, @yoavweiss)
-
Event loop timing reporting seems to ignore reentrancy w3c/longtasks#76 (3 comments by @annevk, @mmocny, @npm1)
-
Combination of paint timing and long tasks can expose precise paint timing w3c/longtasks#80 (2 comments by @npm1)
-
-
1 pull request opened.
-
Refactor report long task w3c/longtasks#84, by @npm1.
-
-
1 pull request merged.
-
Refactor report long task w3c/longtasks#84.
-
-
1 pull request received 5 new comments.
w3c/hr-time
-
3 issues opened.
-
Make high resolution time dependant on cross-origin isolated w3c/hr-time#89, by @annevk.
-
High resolution time is not defined w3c/hr-time#88, by @annevk.
-
-
3 issues received 8 new comments.
-
Make high resolution time dependant on cross-origin isolated w3c/hr-time#89 (4 comments by @mikewest, @npm1, @yoavweiss)
-
Security and privacy considerations for DOMHighResTimeStamp resolution w3c/hr-time#79 (3 comments by @annevk, @pes10k)
-
w3c/paint-timing
-
1 issue opened.
-
Set up auto-publishing? w3c/paint-timing#87, by @yoavweiss.
-
-
4 issues closed.
-
What is the scope of timings? w3c/paint-timing#31.
-
Clarify whether First Contentful Paint considers content outside the viewport w3c/paint-timing#58.
-
Be more precise about first paint vs first contentful paint w3c/paint-timing#38.
-
Allow optional implementation of first-paint w3c/paint-timing#57.
-
-
5 issues received 9 new comments.
-
surprising (if not understandable) results for first-paint when `document.visibilityState === 'hidden'` w3c/paint-timing#40 (4 comments by @noamr, @npm1, @yoavweiss)
-
Clarify whether First Contentful Paint considers content outside the viewport w3c/paint-timing#58 (1 comment by @rniwa)
-
-
4 pull requests opened.
-
Update affiliation for NoamR w3c/paint-timing#86, by @noamr.
-
Update Editors w3c/paint-timing#85, by @npm1.
-
Add definition for tainted w3c/paint-timing#84, by @noamr.
-
Fixed to use "environment settings object" based on comment" w3c/paint-timing#83, by @noamr.
-
-
5 pull requests merged.
-
Update Editors w3c/paint-timing#85.
-
Update affiliation for NoamR w3c/paint-timing#86.
-
Fixed to use "environment settings object" based on comment" w3c/paint-timing#83.
-
Be explicit about marking each paint type only once w3c/paint-timing#82.
-
Make first-paint optional w3c/paint-timing#81.
-
-
1 pull request closed.
-
Add definition for tainted w3c/paint-timing#84.
-
-
6 pull requests received 21 new comments.
-
Be explicit about marking each paint type only once w3c/paint-timing#82 (8 comments by @noamr, @npm1, @yoavweiss)
-
Fixed to use "environment settings object" based on comment" w3c/paint-timing#83 (2 comments by @noamr, @npm1)
-
w3c/device-memory
-
1 issue opened.
-
Setup auto-publishing w3c/device-memory#31, by @yoavweiss.
-
-
1 issue received 2 new comments.
-
Deploy failed on later push to master w3c/device-memory#26 (2 comments by @stephenmcgruer, @yoavweiss)
-
-
1 pull request opened.
-
New deploy key w3c/device-memory#30, by @yoavweiss.
-
-
1 pull request merged.
-
New deploy key w3c/device-memory#30.
-
-
1 pull request received 2 new comments.
w3c/largest-contentful-paint
-
1 issue received 1 new comment.
-
Call back to indicate that the observer is about to stop w3c/largest-contentful-paint#43 (1 comment by @patrickhulce)
-
w3c/element-timing
-
1 issue opened.
-
non-timing-allow images fall back to load time w3c/element-timing#46, by @paulirish.
-
-
1 issue closed.
-
non-timing-allow images fall back to load time w3c/element-timing#46.
-
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
User Timing Level 3 published as a Working Draft. History of User Timing Level 3
-
Participants
-
2 participants joined.
-
Michelle Vu (W3C Invited Experts) joined.
-
Noam Rosenthal (Google LLC) joined.
-
-
1 participant left.
-
bowen liu (360) left.
-
GitHub
w3c/largest-contentful-paint
-
1 issue opened.
-
renderTime definition is unclear in the spec for each element type w3c/largest-contentful-paint#54, by @patrickhulce.
-
-
4 issues received 10 new comments.
-
LCP appears on the popup after mousemove interaction w3c/largest-contentful-paint#50 (6 comments by @npm1, @patrickhulce)
-
renderTime definition is unclear in the spec for each element type w3c/largest-contentful-paint#54 (2 comments by @npm1, @patrickhulce)
-
Call back to indicate that the observer is about to stop w3c/largest-contentful-paint#43 (1 comment by @paulirish)
-
Reset LCP for Single Page App soft navigations w3c/largest-contentful-paint#6 (1 comment by @nithinnew2010)
-
-
3 pull requests opened.
-
Pass realm to LargestContentfulPaint w3c/largest-contentful-paint#53, by @npm1.
-
Upgrade to Python 3 w3c/largest-contentful-paint#52, by @yoavweiss.
-
-
3 pull requests merged.
-
Pass realm to LargestContentfulPaint w3c/largest-contentful-paint#53.
-
Fix typo w3c/largest-contentful-paint#51.
-
Upgrade to Python 3 w3c/largest-contentful-paint#52.
-
-
2 pull requests received 2 new comments.
w3c/event-timing
-
2 issues opened.
-
Remove the mention of "RAIL performance model" in security and privacy considerations w3c/event-timing#69, by @rniwa.
-
"nearest multiple of 8" in "dispatch pending Event Timing entries" must specify the unit w3c/event-timing#68, by @rniwa.
-
-
2 issues closed.
-
1 issue received 6 new comments.
-
"nearest multiple of 8" in "dispatch pending Event Timing entries" must specify the unit w3c/event-timing#68 (6 comments by @npm1, @rniwa)
-
-
8 pull requests opened.
-
Add EventCounts example w3c/event-timing#76, by @npm1.
-
Update EventCounts type w3c/event-timing#75, by @npm1.
-
Set event realm w3c/event-timing#74, by @npm1.
-
Add flexibility on duration w3c/event-timing#73, by @npm1.
-
Remove RAIL mention w3c/event-timing#72, by @npm1.
-
Update Python to 3.7 w3c/event-timing#71, by @npm1.
-
Specify the units when rounding w3c/event-timing#70, by @npm1.
-
Minor corrections to README w3c/event-timing#67, by @npm1.
-
-
7 pull requests merged.
-
Add flexibility on duration w3c/event-timing#73.
-
Update EventCounts type w3c/event-timing#75.
-
Set event realm w3c/event-timing#74.
-
Remove RAIL mention w3c/event-timing#72.
-
Specify the units when rounding w3c/event-timing#70.
-
Update Python to 3.7 w3c/event-timing#71.
-
Minor corrections to README w3c/event-timing#67.
-
-
1 pull request reopened.
-
Specify the units when rounding w3c/event-timing#70, by @npm1.
-
-
2 pull requests received 7 new comments.
w3c/paint-timing
-
13 issues opened.
-
Account for typographical pseudo-elements w3c/paint-timing#77, by @noamr.
-
Should transparent (alpha-value=0) text be considered contentful w3c/paint-timing#75, by @noamr.
-
Timestamps should be specified in an interoperative way w3c/paint-timing#62, by @smfr.
-
Clarify: are gradients considered contentful? w3c/paint-timing#61, by @noamr.
-
Clarify whether First Contentful Paint considers content outside the viewport w3c/paint-timing#58, by @smfr.
-
Allow optional implementation of first-paint w3c/paint-timing#57, by @noamr.
-
Clarify contentful state regarding images that are not foreground/background w3c/paint-timing#56, by @noamr.
-
Combination of paint timing and long tasks can expose precise paint timing w3c/paint-timing#55, by @rniwa.
-
Clarify what happens to a page which consists of just an iframe w3c/paint-timing#54, by @rniwa.
-
Clarify whether "first paint" or "first contentful paint" ever happens to a blank page w3c/paint-timing#53, by @rniwa.
-
Consider taking form controls into account for first contentful paint w3c/paint-timing#52, by @rniwa.
-
First contentful paint should take the poster image / first frame of video into account w3c/paint-timing#51, by @rniwa.
-
Wording about canvas/svg is a bit inaccurate w3c/paint-timing#50, by @noamr.
-
-
18 issues closed.
-
Clarify what happens to a page which consists of just an iframe w3c/paint-timing#54.
-
Account for typographical pseudo-elements w3c/paint-timing#77.
-
Should transparent (alpha-value=0) text be considered contentful w3c/paint-timing#75.
-
Consider taking form controls into account for first contentful paint w3c/paint-timing#52.
-
Define whether clipped contents should be included in first contextual paint w3c/paint-timing#20.
-
Clarify invisible text w3c/paint-timing#29.
-
Wording about canvas/svg is a bit inaccurate w3c/paint-timing#50.
-
Clarify contentful state regarding images that are not foreground/background w3c/paint-timing#56.
-
Clarify: are gradients considered contentful? w3c/paint-timing#61.
-
The exact timing of navigation should be defined w3c/paint-timing#19.
-
supported entry types needs to be context aware w3c/paint-timing#37.
-
Headings should be sentence case, not titlecase w3c/paint-timing#14.
-
Nits in "PerformancePaintTiming interface" w3c/paint-timing#12.
-
Nit: heading style for Paint timing w3c/paint-timing#11.
-
Cross-link to update the rendering w3c/paint-timing#10.
-
Combination of paint timing and long tasks can expose precise paint timing w3c/paint-timing#55.
-
-
5 issues reopened.
-
Clarify contentful state regarding images that are not foreground/background w3c/paint-timing#56, by @rniwa.
-
Clarify: are gradients considered contentful? w3c/paint-timing#61, by @rniwa.
-
First contentful paint should take the poster image / first frame of video into account w3c/paint-timing#51, by @rniwa.
-
Clarify whether First Contentful Paint considers content outside the viewport w3c/paint-timing#58, by @rniwa.
-
Clarify whether First Contentful Paint considers content outside the viewport w3c/paint-timing#58, by @rniwa.
-
-
22 issues received 191 new comments.
-
Clarify whether First Contentful Paint considers content outside the viewport w3c/paint-timing#58 (44 comments by @anniesullie, @mstange, @noamr, @npm1, @othermaciej, @rniwa, @sefeng211, @smfr, @yoavweiss)
-
Wording about canvas/svg is a bit inaccurate w3c/paint-timing#50 (29 comments by @annevk, @noamr, @npm1, @rniwa)
-
Allow optional implementation of first-paint w3c/paint-timing#57 (24 comments by @anniesullie, @bdekoz, @gi11es, @noamr, @npm1, @rniwa)
-
Clarify what happens to a page which consists of just an iframe w3c/paint-timing#54 (15 comments by @noamr, @npm1, @rniwa)
-
Clarify whether "first paint" or "first contentful paint" ever happens to a blank page w3c/paint-timing#53 (14 comments by @gi11es, @noamr, @npm1, @rniwa, @yoavweiss)
-
Clarify: are gradients considered contentful? w3c/paint-timing#61 (9 comments by @noamr, @npm1, @rniwa)
-
Timestamps should be specified in an interoperative way w3c/paint-timing#62 (7 comments by @npm1, @rniwa, @yoavweiss)
-
Consider taking form controls into account for first contentful paint w3c/paint-timing#52 (6 comments by @noamr, @npm1, @rniwa, @yoavweiss)
-
First contentful paint should take the poster image / first frame of video into account w3c/paint-timing#51 (6 comments by @noamr, @npm1, @rniwa, @yoavweiss)
-
Be more precise about first paint vs first contentful paint w3c/paint-timing#38 (5 comments by @noamr, @npm1, @rniwa, @yoavweiss)
-
Clarify contentful state regarding images that are not foreground/background w3c/paint-timing#56 (5 comments by @noamr, @npm1, @rniwa)
-
Should transparent (alpha-value=0) text be considered contentful w3c/paint-timing#75 (4 comments by @mstange, @noamr, @npm1, @rniwa)
-
Headings should be sentence case, not titlecase w3c/paint-timing#14 (4 comments by @domenic, @npm1, @tabatkins)
-
Define whether clipped contents should be included in first contextual paint w3c/paint-timing#20 (3 comments by @npm1, @rniwa, @yoavweiss)
-
Combination of paint timing and long tasks can expose precise paint timing w3c/paint-timing#55 (2 comments by @npm1, @rniwa)
-
surprising (if not understandable) results for first-paint when `document.visibilityState === 'hidden'` w3c/paint-timing#40 (1 comment by @npm1)
-
-
20 pull requests opened.
-
Be explicit about marking each paint type only once w3c/paint-timing#82, by @noamr.
-
Make first-paint optional w3c/paint-timing#81, by @noamr.
-
Cover an edge-case with typographic pseudo elements w3c/paint-timing#80, by @noamr.
-
Clarify that availability of paint-API is limited to a particular browsing context. w3c/paint-timing#79, by @noamr.
-
Remove unneeded viewport mentions w3c/paint-timing#78, by @npm1.
-
Make fully-transparent text non-contentful w3c/paint-timing#76, by @noamr.
-
Remove erronously added comma w3c/paint-timing#74, by @noamr.
-
Add note about contentfulness of input elements w3c/paint-timing#73, by @noamr.
-
Add note re blank pages w3c/paint-timing#72, by @noamr.
-
Upgrade to python 3.7 (required for bikeshed) w3c/paint-timing#71, by @noamr.
-
Clarify contentful video w3c/paint-timing#70, by @noamr.
-
Fix PerformanceEntry creation w3c/paint-timing#69, by @npm1.
-
Improve wording in introduction w3c/paint-timing#68, by @npm1.
-
Pass document as input to paint timing algorithms w3c/paint-timing#67, by @npm1.
-
Clarify what 'contentful' means w3c/paint-timing#66, by @noamr.
-
Add link to viewport w3c/paint-timing#65, by @npm1.
-
Editorial fixes w3c/paint-timing#64, by @npm1.
-
Editorial: update the rendering link fix w3c/paint-timing#63, by @npm1.
-
Allow mask images to be contentful w3c/paint-timing#60, by @npm1.
-
Clarify paints outside viewport w3c/paint-timing#59, by @npm1.
-
-
16 pull requests merged.
-
Clarify that availability of paint-API is limited to a particular browsing context. w3c/paint-timing#79.
-
Cover an edge-case with typographic pseudo elements w3c/paint-timing#80.
-
Remove unneeded viewport mentions w3c/paint-timing#78.
-
Add note about contentfulness of input elements w3c/paint-timing#73.
-
Remove erronously added comma w3c/paint-timing#74.
-
Add note re blank pages w3c/paint-timing#72.
-
Clarify contentful video w3c/paint-timing#70.
-
Upgrade to python 3.7 (required for bikeshed) w3c/paint-timing#71.
-
Clarify what 'contentful' means w3c/paint-timing#66.
-
Fix PerformanceEntry creation w3c/paint-timing#69.
-
Improve wording in introduction w3c/paint-timing#68.
-
Pass document as input to paint timing algorithms w3c/paint-timing#67.
-
Editorial fixes w3c/paint-timing#64.
-
Add link to viewport w3c/paint-timing#65.
-
Editorial: update the rendering link fix w3c/paint-timing#63.
-
Clarify paints outside viewport w3c/paint-timing#59.
-
-
2 pull requests closed.
-
Make fully-transparent text non-contentful w3c/paint-timing#76.
-
Allow mask images to be contentful w3c/paint-timing#60.
-
-
12 pull requests received 211 new comments.
-
Clarify what 'contentful' means w3c/paint-timing#66 (116 comments by @anniesullie, @noamr, @npm1, @rniwa, @smfr, @yoavweiss)
-
Clarify that availability of paint-API is limited to a particular browsing context. w3c/paint-timing#79 (31 comments by @noamr, @npm1, @yoavweiss)
-
Add note about contentfulness of input elements w3c/paint-timing#73 (14 comments by @noamr, @npm1, @rniwa, @yoavweiss)
-
Be explicit about marking each paint type only once w3c/paint-timing#82 (12 comments by @noamr, @npm1, @yoavweiss)
-
Make fully-transparent text non-contentful w3c/paint-timing#76 (9 comments by @noamr, @npm1, @rniwa, @yoavweiss)
-
w3c/resource-timing
-
2 issues opened.
-
PerformanceResourceTimings never published, nondeterministically w3c/resource-timing#227, by @bmk5cc.
-
Pass realm when creating PerformanceResourceTiming w3c/resource-timing#226, by @npm1.
-
-
1 issue closed.
-
PerformanceResourceTimings never published, nondeterministically w3c/resource-timing#227.
-
-
2 issues received 4 new comments.
-
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage w3c/resource-timing#222 (3 comments by @andydavies, @kdzwinel, @pes10k)
-
PerformanceResourceTimings never published, nondeterministically w3c/resource-timing#227 (1 comment by @rniwa)
-
-
1 pull request opened.
-
Pass realm when creating PerformanceResourceTiming w3c/resource-timing#225, by @npm1.
-
-
1 pull request received 5 new comments.
-
Pass realm when creating PerformanceResourceTiming w3c/resource-timing#225 (5 comments by @annevk, @npm1, @rniwa, @yoavweiss)
-
w3c/reporting
-
4 issues opened.
-
Support for CSP Frame Ancestor violation reports w3c/reporting#203, by @Bio2hazard.
-
Abstract needs updating w3c/reporting#200, by @annevk.
-
Reporting-Endpoints processing w3c/reporting#199, by @annevk.
-
-
5 issues closed.
-
Feedback from Mozilla w3c/reporting#158.
-
Switch reporting to Structured Headers w3c/reporting#177.
-
Valid URI-reference w3c/reporting#195.
-
5 issues received 16 new comments.
-
Support for CSP Frame Ancestor violation reports w3c/reporting#203 (9 comments by @Bio2hazard, @chlily1, @clelland, @mikewest)
-
An editorial suggestion to simplify the "Process reporting endpoints for response" algorithm w3c/reporting#201 (1 comment by @clelland)
-
-
3 pull requests opened.
-
Update to Python 3 w3c/reporting#204, by @siusin.
-
chore: Update CI config to use Python 3.7 w3c/reporting#202, by @plehegar.
-
-
5 pull requests merged.
-
chore: Update CI config to use Python 3.7 w3c/reporting#202.
-
Update to Python 3 w3c/reporting#204.
-
fix typo w3c/reporting#198.
-
Structured headers w3c/reporting#197.
-
Remove persistent non-document reporting from spec. w3c/reporting#191.
-
-
1 pull request received 1 new comment.
w3c/device-memory
-
1 pull request opened.
-
Update to Python 3 w3c/device-memory#29, by @siusin.
-
-
1 pull request merged.
-
Update to Python 3 w3c/device-memory#29.
-
w3c/longtasks
-
1 issue opened.
-
Combination of paint timing and long tasks can expose precise paint timing w3c/longtasks#80, by @rniwa.
-
-
3 pull requests opened.
-
Pass realms to objects upon creation w3c/longtasks#82, by @npm1.
-
chore: Update CI config to use Python 3.7 w3c/longtasks#81, by @plehegar.
-
-
3 pull requests merged.
-
Pass realms to objects upon creation w3c/longtasks#82.
-
chore: Update CI config to use Python 3.7 w3c/longtasks#81.
-
Fix typo w3c/longtasks#79.
-
w3c/element-timing
-
1 issue opened.
-
Definitions related to image loading are not precise w3c/element-timing#43, by @yoavweiss.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Set realm on object creation w3c/element-timing#45, by @npm1.
-
Upgrade Python w3c/element-timing#44, by @npm1.
-
-
2 pull requests merged.
-
Set realm on object creation w3c/element-timing#45.
-
Upgrade Python w3c/element-timing#44.
-
w3c/user-timing
-
1 issue received 1 new comment.
-
Allow performance.measure() to specify optional color parameter, to be used by perf visualizations in devtools w3c/user-timing#69 (1 comment by @fshort)
-
-
1 pull request opened.
-
Pass realms in UserTiming constructors w3c/user-timing#70, by @npm1.
-
-
1 pull request merged.
-
Pass realms in UserTiming constructors w3c/user-timing#70.
-
-
1 pull request received 4 new comments.
w3c/performance-timeline
-
2 issues opened.
-
Use of "SyntaxError" seems incorrect, should be TypeError w3c/performance-timeline#163, by @noamr.
-
Queue the entry should require a global object as input w3c/performance-timeline#162, by @npm1.
-
-
2 issues received 10 new comments.
-
Use of "SyntaxError" seems incorrect, should be TypeError w3c/performance-timeline#163 (7 comments by @noamr, @npm1, @yoavweiss)
-
Queue the entry should require a global object as input w3c/performance-timeline#162 (3 comments by @npm1, @rniwa)
-
w3c/navigation-timing
-
4 issues opened.
-
Possibility to get the HTTP status code from the Response Header ? w3c/navigation-timing#126, by @ThierryMajutec.
-
PerformanceNavigationTiming needs a realm w3c/navigation-timing#125, by @npm1.
-
Surface chunk network timing details w3c/navigation-timing#123, by @jtedesco.
-
-
3 issues received 4 new comments.
-
Possibility to get the HTTP status code from the Response Header ? w3c/navigation-timing#126 (2 comments by @yoavweiss)
-
Can hitting enter on address bar to same URL be considered a navigation of type 'reload'? w3c/navigation-timing#116 (1 comment by @yoavweiss)
-
TR publications
-
1 document published.
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
Participants
-
3 participants joined.
-
Aaron Schulz (Wikimedia Foundation) joined.
-
Timo Tijhof (Wikimedia Foundation) joined.
-
Dave Pifke (Wikimedia Foundation) joined.
-
-
1 participant left.
-
Ronald Ning (Microsoft Corporation) left.
-
GitHub
w3c/resource-timing
-
3 issues opened.
-
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage w3c/resource-timing#222, by @kdzwinel.
-
Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy w3c/resource-timing#221, by @kdzwinel.
-
4 issues received 32 new comments.
-
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage w3c/resource-timing#222 (25 comments by @andydavies, @jdorweiler, @kdzwinel, @michaelkleber, @npm1, @pes10k, @yoavweiss)
-
Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy w3c/resource-timing#221 (4 comments by @kdzwinel, @pes10k, @yoavweiss)
-
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent accidental application state leakage w3c/resource-timing#223 (2 comments by @kdzwinel, @npm1)
-
Cross-origin IFRAME opting-in to sharing ResourceTiming data w3c/resource-timing#210 (1 comment by @nicjansma)
-
-
1 pull request opened.
-
TAO-Protect nextHopProtocol w3c/resource-timing#224, by @yoavweiss.
-
-
1 pull request merged.
-
Update timing allow check algorithm w3c/resource-timing#218.
-
-
2 pull requests received 6 new comments.
w3c/user-timing
-
1 issue opened.
-
1 issue received 8 new comments.
-
Allow performance.measure() to specify optional color parameter, to be used by perf visualizations in devtools w3c/user-timing#69 (8 comments by @bgirard, @jakub-g, @npm1, @rniwa)
-
w3c/paint-timing
-
1 issue opened.
-
supportedEntryTypes: should show types rather than names w3c/paint-timing#48, by @noamr.
-
-
1 issue closed.
-
supportedEntryTypes: should show types rather than names w3c/paint-timing#48.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fix Note about supportedEntryTypes w3c/paint-timing#49, by @npm1.
-
-
1 pull request merged.
-
Fix Note about supportedEntryTypes w3c/paint-timing#49.
-
w3c/web-performance
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
HAR is history w3c/web-performance#30, by @plehegar.
-
Remove unmatched </pre> tag w3c/web-performance#29, by @ccouzens.
-
-
1 pull request merged.
-
HAR is history w3c/web-performance#30.
-
-
1 pull request closed.
-
Remove unmatched </pre> tag w3c/web-performance#29.
-
-
1 pull request received 5 new comments.
w3c/performance-timeline
-
1 issue closed.
-
Using a single observer instance throughout the application lifetime w3c/performance-timeline#160.
-
-
1 issue received 4 new comments.
-
Using a single observer instance throughout the application lifetime w3c/performance-timeline#160 (4 comments by @npm1, @vigneshshanmugam, @yoavweiss)
-
-
1 pull request opened.
-
Clear options list upon call to disconnect w3c/performance-timeline#161, by @npm1.
-
-
1 pull request merged.
-
Clear options list upon call to disconnect w3c/performance-timeline#161.
-
w3c/longtasks
-
1 issue reopened.
-
Can we find which script or function is taking longer than 50 ms? w3c/longtasks#28, by @npm1.
-
-
1 issue received 3 new comments.
-
Can we find which script or function is taking longer than 50 ms? w3c/longtasks#28 (3 comments by @npm1, @RaoufHammami, @vigneshshanmugam)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
LCP appears on the popup after mousemove interaction w3c/largest-contentful-paint#50, by @alekseykulikov.
-
-
2 issues received 3 new comments.
-
LCP appears on the popup after mousemove interaction w3c/largest-contentful-paint#50 (1 comment by @npm1)
w3c/device-memory
-
1 issue opened.
-
Deploy failed on later push to master w3c/device-memory#26, by @foolip.
-
-
1 issue closed.
-
Deploy failed on later push to master w3c/device-memory#26.
-
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
Fix bikeshed issues w3c/device-memory#28, by @yoavweiss.
-
Modified deploy_key.enc w3c/device-memory#27, by @yoavweiss.
-
-
2 pull requests merged.
-
Fix bikeshed issues w3c/device-memory#28.
-
Modified deploy_key.enc w3c/device-memory#27.
-
-
2 pull requests received 2 new comments.
w3c/reporting
-
3 issues received 6 new comments.
-
Should we remove load-balancing and failover/retry logic from document-centered reporting? w3c/reporting#196 (1 comment by @clelland)
-
1 pull request received 1 new comment.
w3c/requestidlecallback
-
1 pull request received 3 new comments.
-
Define algorithm for determining whether high priority work exists. w3c/requestidlecallback#88 (3 comments by @annevk, @rmcilroy)
-
w3c/server-timing
-
1 issue received 1 new comment.
-
add start time to distinguish between cached and active entries w3c/server-timing#43 (1 comment by @hauleth)
-
TR publications
-
3 documents published.
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Server Timing published as a Working Draft. History of Server Timing
-
Participants
-
4 participants left.
-
Panos Astithas (Mozilla Foundation) left.
-
Vivek Sekhar (Google LLC) left.
-
James Simonsen (Google LLC) left.
-
Tony Gentilcore (Google LLC) left.
-
-
1 organization joined.
-
Search Engine Optimization Inc joined.
-
GitHub
w3c/performance-timeline
-
2 issues opened.
-
Using a single observer instance throughout the application lifetime w3c/performance-timeline#160, by @vigneshshanmugam.
-
Are we always supposed to queue a notification task when there are buffered entries to see? w3c/performance-timeline#158, by @pshaughn.
-
-
1 issue closed.
-
Are we always supposed to queue a notification task when there are buffered entries to see? w3c/performance-timeline#158.
-
-
2 issues received 2 new comments.
-
Are we always supposed to queue a notification task when there are buffered entries to see? w3c/performance-timeline#158 (1 comment by @npm1)
-
-
1 pull request opened.
-
Fix observe() with buffered flag w3c/performance-timeline#159, by @npm1.
-
-
1 pull request merged.
-
Fix observe() with buffered flag w3c/performance-timeline#159.
-
-
2 pull requests received 3 new comments.
w3c/beacon
-
1 pull request opened.
-
Set the keepalive flag when extracting the body w3c/beacon#66, by @ricea.
-
-
1 pull request merged.
-
Set the keepalive flag when extracting the body w3c/beacon#66.
-
w3c/reporting
-
4 issues opened.
-
Valid URI-reference w3c/reporting#195, by @annevk.
-
Report Delivery w3c/reporting#194, by @annevk.
-
Privacy considerations should describe how user IDs can leak w3c/reporting#192, by @jyasskin.
-
1 issue closed.
-
Remove concrete reporting types from Reporting API spec w3c/reporting#189.
-
-
4 issues received 20 new comments.
-
Should we remove load-balancing and failover/retry logic from document-centered reporting? w3c/reporting#196 (3 comments by @clelland, @dcreager)
-
2 pull requests opened.
-
Structured headers w3c/reporting#197, by @clelland.
-
Update deploy and compile scripts to support long-lived target branches w3c/reporting#193, by @clelland.
-
-
2 pull requests merged.
-
Update deploy and compile scripts to support long-lived target branches w3c/reporting#193.
-
Remove concrete reports w3c/reporting#190.
-
-
2 pull requests received 5 new comments.
-
Disallow credentials from cross-origin reports w3c/reporting#186 (3 comments by @jyasskin, @yoavweiss)
-
Remove persistent non-document reporting from spec. w3c/reporting#191 (2 comments by @clelland, @dcreager)
-
w3c/resource-timing
-
1 issue opened.
-
Provide a TAO-bypass for Navigation timing w3c/resource-timing#220, by @yoavweiss.
-
-
1 issue closed.
-
Handling of 0-RTT interactions w3c/resource-timing#199.
-
-
3 issues received 5 new comments.
-
Expose JavaScript code caching information in PerformanceResourceTiming w3c/resource-timing#190 (2 comments by @mathiasbynens, @rniwa)
-
Cross-origin IFRAME opting-in to sharing ResourceTiming data w3c/resource-timing#210 (2 comments by @npm1, @yoavweiss)
-
The step to queue a task to run fire a buffer full event should specify its source w3c/resource-timing#215 (1 comment by @npm1)
-
-
1 pull request opened.
-
Zero RTT clarifications from davidben w3c/resource-timing#219, by @yoavweiss.
-
-
1 pull request merged.
-
Zero RTT clarifications from davidben w3c/resource-timing#219.
-
-
1 pull request received 12 new comments.
-
Zero RTT clarifications from davidben w3c/resource-timing#219 (12 comments by @davidben, @npm1, @yoavweiss)
-
w3c/server-timing
-
1 issue opened.
-
Exposing data on production w3c/server-timing#71, by @SilentImp.
-
-
1 issue closed.
-
Exposing data on production w3c/server-timing#71.
-
-
2 issues received 6 new comments.
-
Using Server-timing to carry TraceID w3c/server-timing#65 (5 comments by @plehegar, @SilentImp, @yoavweiss)
-
-
1 pull request merged.
-
Add conformance section w3c/server-timing#66.
-
-
1 pull request received 2 new comments.
-
chore: update ReSpec syntax and error fixes w3c/server-timing#70 (2 comments by @plehegar, @sidvishnoi)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
'name' is never being set w3c/largest-contentful-paint#48, by @npm1.
-
-
1 issue closed.
-
'name' is never being set w3c/largest-contentful-paint#48.
-
-
1 issue received 3 new comments.
-
Call back to indicate that the observer is about to stop w3c/largest-contentful-paint#43 (3 comments by @npm1, @philipwalton)
-
-
1 pull request opened.
-
Name is empty string w3c/largest-contentful-paint#49, by @npm1.
-
-
1 pull request merged.
-
Name is empty string w3c/largest-contentful-paint#49.
-
w3c/device-memory
-
1 pull request opened.
-
Convert NavigatorDeviceClass to an interface mixin w3c/device-memory#25, by @foolip.
-
-
1 pull request merged.
-
Convert NavigatorDeviceClass to an interface mixin w3c/device-memory#25.
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
1 issue closed.
-
Add a new entry type for navigations from the BFCache w3c/navigation-timing#118.
-
-
2 issues received 7 new comments.
-
Add a new entry type for navigations from the BFCache w3c/navigation-timing#118 (5 comments by @npm1, @philipwalton)
-
Definition of "back_forward" navigation type does not make sense w3c/navigation-timing#115 (2 comments by @npm1, @yoavweiss)
-
-
3 pull requests opened.
-
run html5 tidy on spec w3c/navigation-timing#122, by @janiceshiu.
-
remove jquery from spec w3c/navigation-timing#121, by @janiceshiu.
-
add retiredDate to former editors instead of using note w3c/navigation-timing#120, by @janiceshiu.
-
-
3 pull requests merged.
-
run html5 tidy on spec w3c/navigation-timing#122.
-
add retiredDate to former editors instead of using note w3c/navigation-timing#120.
-
remove jquery from spec w3c/navigation-timing#121.
-
-
3 pull requests received 3 new comments.
-
add retiredDate to former editors instead of using note w3c/navigation-timing#120 (1 comment by @yoavweiss)
w3c/event-timing
-
1 issue closed.
-
Considered for event timing: drag & drop w3c/event-timing#52.
-
-
1 issue received 1 new comment.
-
Add element and/or id fields to PerformanceEventTiming to indicate target of the event w3c/event-timing#60 (1 comment by @npm1)
-
-
3 pull requests opened.
-
Add wheel exclusion w3c/event-timing#66, by @npm1.
-
Update explainer event types w3c/event-timing#65, by @npm1.
-
Add Drag&Drop, remove continous event types w3c/event-timing#64, by @npm1.
-
-
3 pull requests merged.
-
Add wheel exclusion w3c/event-timing#66.
-
Update explainer event types w3c/event-timing#65.
-
Add Drag&Drop, remove continous event types w3c/event-timing#64.
-
w3c/paint-timing
-
1 issue closed.
-
The code example incorrectly mentions observing "long tasks" w3c/paint-timing#46.
-
-
1 issue received 1 new comment.
-
The code example incorrectly mentions observing "long tasks" w3c/paint-timing#46 (1 comment by @npm1)
-
w3c/user-timing
-
1 issue received 1 new comment.
-
Allow marks and measures to be shown in developer tooling without adding it to the performance timeline w3c/user-timing#68 (1 comment by @andydavies)
-
w3c/network-error-logging
-
1 issue received 1 new comment.
w3c/requestidlecallback
-
1 pull request received 1 new comment.
-
Define algorithm for determining whether high priority work exists. w3c/requestidlecallback#88 (1 comment by @yoavweiss)
-
w3c/timing-entrytypes-registry
-
1 pull request merged.
-
chore: switch to faster/lighter ReSpec w3c/timing-entrytypes-registry#10.
-
w3c/hr-time
-
1 pull request merged.
-
chore: remove ReSpec format option, spec uses HTML w3c/hr-time#86.
-