w3c/resource-timing issues and pull requests

#304 - Consider to limit the max size of resource timing buffer

Issue - State: closed - Opened by smaug---- almost 3 years ago - 13 comments

#303 - Reflect preload information (in ResourceTiming?)

Issue - State: open - Opened by noamr almost 3 years ago - 23 comments
Labels: enhancement

#302 - Expose everywhere

Pull Request - State: closed - Opened by Ms2ger almost 3 years ago - 6 comments
Labels: blocked:feedback

#302 - Expose everywhere

Pull Request - State: closed - Opened by Ms2ger almost 3 years ago - 6 comments
Labels: blocked:feedback

#299 - Should favicon loading times be exposed to the document?

Issue - State: closed - Opened by noamr almost 3 years ago - 4 comments

#286 - Missing tests following the Fetch integration

Issue - State: closed - Opened by yoavweiss about 3 years ago - 1 comment

#262 - Render blocking status of resources

Issue - State: closed - Opened by yoavweiss over 3 years ago - 5 comments
Labels: enhancement

#255 - Resource direct lookup support

Issue - State: open - Opened by sean-roberts over 3 years ago - 7 comments
Labels: enhancement

#254 - WPT Cleanup

Issue - State: closed - Opened by tommckee1 over 3 years ago - 3 comments

#254 - WPT Cleanup

Issue - State: closed - Opened by tommckee1 over 3 years ago - 3 comments

#249 - "Queue a task to run fire a buffer full event" needs to have a task queue

Issue - State: closed - Opened by yoavweiss over 3 years ago - 2 comments
Labels: fetch-integration

#249 - "Queue a task to run fire a buffer full event" needs to have a task queue

Issue - State: closed - Opened by yoavweiss over 3 years ago - 2 comments
Labels: fetch-integration

#236 - Conform 'current time' definition to the current hr-time spec

Pull Request - State: open - Opened by igneel64 about 4 years ago - 1 comment
Labels: hackathon_2020

#233 - ResourceTiming Test Triage 9/2020

Issue - State: open - Opened by nicjansma about 4 years ago - 1 comment
Labels: hackathon_15_09_20, hackathon_2020

#222 - Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage

Issue - State: open - Opened by kdzwinel over 4 years ago - 42 comments
Labels: privacy-needs-resolution

#222 - Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage

Issue - State: open - Opened by kdzwinel over 4 years ago - 42 comments
Labels: privacy-needs-resolution

#221 - Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy

Issue - State: open - Opened by kdzwinel over 4 years ago - 11 comments
Labels: privacy-needs-resolution

#221 - Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy

Issue - State: open - Opened by kdzwinel over 4 years ago - 11 comments
Labels: privacy-needs-resolution

#220 - Provide a TAO-bypass for Navigation timing

Issue - State: open - Opened by yoavweiss over 4 years ago - 16 comments
Labels: Clarification, editorial, requires Fetch integration, hackathon_15_09_20, hackathon_2020

#210 - Cross-origin IFRAME opting-in to sharing ResourceTiming data

Issue - State: open - Opened by nicjansma over 5 years ago - 8 comments
Labels: enhancement, requires Fetch integration

#204 - Add tests for not-same-site nested contexts

Issue - State: open - Opened by yoavweiss over 5 years ago - 3 comments
Labels: test:missing-coverage

#203 - Include Content Type

Issue - State: closed - Opened by Snugug over 5 years ago - 5 comments
Labels: enhancement

#188 - Test multiple DNS responses and connection failures

Issue - State: open - Opened by yoavweiss almost 6 years ago - 3 comments
Labels: test:missing-coverage

#186 - Test domainLookup values in the connection coalescing case

Issue - State: open - Opened by yoavweiss almost 6 years ago - 1 comment
Labels: test:missing-coverage

#186 - Test domainLookup values in the connection coalescing case

Issue - State: open - Opened by yoavweiss almost 6 years ago - 1 comment
Labels: test:missing-coverage

#164 - elaborate on `stalled` or `blocked` stage in specs

Issue - State: closed - Opened by jasonslyvia about 6 years ago - 8 comments
Labels: Clarification

#142 - `InitiatorType` should not single out XHR

Issue - State: open - Opened by yoavweiss over 6 years ago - 14 comments
Labels: Clarification

#132 - Collect initiatorType use-cases

Issue - State: open - Opened by nicjansma almost 7 years ago - 3 comments

#126 - Review that Resource Timing 2 language works for QUIC

Issue - State: closed - Opened by toddreifsteck almost 7 years ago
Labels: Clarification

#119 - spec what requestStart, responseStart, and responseEnd should represent when service worker is involved

Issue - State: closed - Opened by wanderview almost 7 years ago - 29 comments
Labels: needs tests, Clarification, requires Fetch integration

#102 - Expose a way to link a call to fetch to an individual PerformanceResourceTiming object

Issue - State: open - Opened by n8schloss over 7 years ago - 4 comments
Labels: enhancement, requires Fetch integration

#100 - Clarify what constitutes a "downloadable resource"

Issue - State: closed - Opened by JosephPecoraro over 7 years ago - 9 comments
Labels: needs tests, Clarification, requires Fetch integration

#90 - Add response status codes for resources in Resource Timing API.

Issue - State: closed - Opened by vaibhavtripathi over 7 years ago - 5 comments
Labels: enhancement, whiteboard, requires Fetch integration

#71 - Transition Level 2 to CR

Issue - State: closed - Opened by igrigorik almost 8 years ago - 9 comments
Labels: w3c

#71 - Transition Level 2 to CR

Issue - State: closed - Opened by igrigorik almost 8 years ago - 9 comments
Labels: w3c

#58 - ResourceTiming and preconnect

Issue - State: closed - Opened by yoavweiss over 8 years ago - 8 comments
Labels: enhancement, whiteboard

#54 - initiatorType definition doesn't define initiator in multiple element scenarios

Issue - State: open - Opened by yoavweiss over 8 years ago - 10 comments
Labels: whiteboard, Clarification

#53 - Server pushed resources in ResourceTiming

Issue - State: closed - Opened by igrigorik over 8 years ago - 24 comments

#27 - Same-origin policy & observing no-cors fetches

Issue - State: closed - Opened by igrigorik about 9 years ago - 17 comments
Labels: security-tracker

#21 - RT should handle multi-request fetches

Issue - State: open - Opened by igrigorik over 9 years ago - 4 comments
Labels: enhancement, requires Fetch integration

#12 - Clarify presence of requests that don't return a response

Issue - State: closed - Opened by igrigorik over 9 years ago - 56 comments

GitHub / w3c/resource-timing issues and pull requests