w3c resource-timing issues

w3c / resource-timing

Resource Timing

https://w3c.github.io/resource-timing/

Other

122 stars 37 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

`nextHopProtocol` needs to be defined in terms of Fetch

#247 yoavweiss closed 3 years ago
2
`initiatorType` processing model needs to be defined in terms of Fetch

#246 yoavweiss closed 3 years ago
1
4.3 `startTime` and `duration` should point to the processing model

#245 yoavweiss closed 3 years ago
1
Definition of `name` needs to be more precise

#244 yoavweiss closed 3 years ago
1
Examples in 4.2 are not normative, but look like ones

#243 yoavweiss closed 3 years ago
0
Network aborted resources SHOULD be present (not MAY)

#242 yoavweiss closed 3 years ago
1
Update the editors list

#241 yoavweiss closed 3 years ago
3
Rationalize Resource-Timing opt-ins with CORS/CORP

#240 yoavweiss opened 3 years ago
5
Why not consider to add "fetchStart" event?

#239 imtaotao closed 3 years ago
1
transferSize might reveal HttpOnly cookies

#238 annevk closed 3 years ago
12
Are fetchStart, connectStart, redirectStart relative to navigationStart?

#237 Nithanaroy closed 3 years ago
10
Conform 'current time' definition to the current hr-time spec

#236 igneel64 opened 4 years ago
1
Point "current time" definition to hr-time "current high resolution time" algorithm

#235 igneel64 closed 3 years ago
0
Respec update

#234 plehegar closed 4 years ago
0
ResourceTiming Test Triage 9/2020

#233 nicjansma opened 4 years ago
1
Add task source to queue a task

#232 npm1 closed 4 years ago
0
Should onresourcetimingbufferfull be called all the time when unhandled?

#231 npm1 closed 4 years ago
2
[Question] What happens when the resource timing entries buffer is full?

#230 Nithanaroy closed 4 years ago
3
Editorial: Align with Web IDL specification

#229 autokagami closed 4 years ago
0
Timing-Allow-Origin may expose allowed URLs

#228 noamr closed 3 years ago
6
PerformanceResourceTimings never published, nondeterministically

#227 bmk5cc closed 4 years ago
1
Pass realm when creating PerformanceResourceTiming

#226 npm1 closed 3 years ago
1
Pass realm when creating PerformanceResourceTiming

#225 npm1 closed 3 years ago
11
TAO-Protect nextHopProtocol

#224 yoavweiss closed 3 years ago
4
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent accidental application state leakage

#223 kdzwinel opened 4 years ago
2
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage

#222 kdzwinel opened 4 years ago
42
Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy

#221 kdzwinel opened 4 years ago
11
Provide a TAO-bypass for Navigation timing

#220 yoavweiss opened 4 years ago
16
Zero RTT clarifications from davidben

#219 yoavweiss closed 4 years ago
2
Update timing allow check algorithm

#218 npm1 closed 4 years ago
1
Protect workerStart with a TAO check

#217 yoavweiss closed 4 years ago
1
Use "cross-origin-resource-policy: cross-origin" for timing-allow-origin

#216 yutakahirano closed 5 years ago
5
The step to queue a task to run fire a buffer full event should specify its source

#215 rniwa closed 4 years ago
2
Align TAO processing with CORS

#214 yoavweiss closed 5 years ago
1
fix: small xref fixes

#213 marcoscaceres closed 5 years ago
0
Spec errors related to DOMHighResTimestamp and EventHandler

#212 yoavweiss closed 5 years ago
0
Replace supportedEntryTypes registration with Note

#211 npm1 closed 5 years ago
0
Cross-origin IFRAME opting-in to sharing ResourceTiming data

#210 nicjansma opened 5 years ago
8
Split response end to a separate algorithm

#209 yoavweiss closed 5 years ago
0
Encapsulate responseEnd in an algorithm

#208 npm1 closed 5 years ago
0
Clarify that TAO needs to be set even on same origin resource after cross-origin redirects

#207 rniwa closed 5 years ago
2
Clarify TAO processing when it comes to revalidation responses

#206 yoavweiss closed 5 years ago
1
Resource Timing and range requests

#205 yoavweiss closed 5 years ago
3
Add tests for not-same-site nested contexts

#204 yoavweiss opened 5 years ago
3
Include Content Type

#203 Snugug closed 1 year ago
5
Timing-Allow-Origin check should be case-insensitive

#202 npm1 closed 5 years ago
6
Specify TAO check for 304 responses

#201 npm1 closed 5 years ago
8
Be a bit more explicit about which subresources are to be ignored from stylesheets

#200 npm1 closed 3 years ago
13
Handling of 0-RTT interactions

#199 yoavweiss closed 4 years ago
10
Register TAO as Permanent Message Header Field Name

#198 plehegar opened 5 years ago
0

Previous Next