Skip to content

Issues: w3c/resource-timing

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
0 Open 128 Closed
0 Open 128 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

The spec uses the wrong Origin definition, and missing a note regarding TAO redirects
#195 by yoavweiss was closed Feb 11, 2019 Level 2
1
Should 404 codes be considered aborts? requires Fetch integration
#165 by npm1 was closed Sep 29, 2019 Level 3
7
elaborate on stalled or blocked stage in specs Clarification
#164 by jasonslyvia was closed Apr 13, 2022 Level 3
1
8
Need to define an actual processing model for what things are added to resource timing and for what global
#166 by bzbarsky was closed Nov 6, 2018 Level 2
Clarify cross-origin resources requires Fetch integration
#173 by alanwaketan was closed Oct 11, 2019 Level 3
13
Broken links in https://w3c.github.io/resource-timing/#sec-performanceresourcetiming
#167 by miketaylr was closed Oct 11, 2018
1
Meta: When should Fetch integration happen?
#179 by yoavweiss was closed Nov 29, 2018
1
DNS lookups can occur even when reusing a connection Pending PR
#160 by npm1 was closed Dec 19, 2018 Level 2
3
Terminated fetch() vs Resource Timing
#161 by npm1 was closed Nov 28, 2018 Level 3
3
Register Timing-Allow-Origin as a header
#174 by yoavweiss was closed Nov 22, 2018 Level 2
1
Specify TAO check for 304 responses
#201 by npm1 was closed Apr 24, 2019
1
8
Encapsulate responseEnd in an algorithm
#208 by npm1 was closed May 16, 2019
1
Use "cross-origin-resource-policy: cross-origin" for timing-allow-origin
#216 by yutakahirano was closed Oct 16, 2019
5
Which DNS timings should be exposed when fetching redirected resource
#258 by tommckee1 was closed Mar 4, 2021
5
Current definition of startTime exposes total redirect time even when TAO fails
#260 by noamr was closed Sep 22, 2021
8
Should onresourcetimingbufferfull be called all the time when unhandled? Clarification
#231 by npm1 was closed Nov 2, 2020
2
transferSize might reveal HttpOnly cookies requires Fetch integration
#238 by annevk was closed Apr 15, 2021
1
12
Are fetchStart, connectStart, redirectStart relative to navigationStart?
#237 by Nithanaroy was closed Jan 9, 2021
10
Add tests for TAO-fail behavior changes since FETCH integration fetch-integration
#264 by noamr was closed Apr 18, 2021
1
2
PerformanceResourceTimings never published, nondeterministically
#227 by bmk5cc was closed Mar 31, 2020
1
[Question] What happens when the resource timing entries buffer is full?
#230 by Nithanaroy was closed Aug 28, 2020
3
WPT Cleanup
#254 by tommckee1 was closed Jul 18, 2022
3
Why not consider to add "fetchStart" event?
#239 by imtaotao was closed Jan 8, 2021
1
Point "current time" definition to hr-time "current high resolution time" algorithm Clarification hackathon_2020
#235 by igneel64 was closed Sep 29, 2021
1
"Queue a task to run fire a buffer full event" needs to have a task queue fetch-integration
#249 by yoavweiss was closed Jan 17, 2022
2
ProTip! Type g i on any issue or pull request to go back to the issue listing page.