issues
search
w3c
/
server-timing
Server Timing
http://w3c.github.io/server-timing/
Other
75
stars
20
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Support ReSpec dark mode.
#99
clelland
closed
2 weeks ago
1
Normative references to discontinued specs in Server Timing
#98
dontcallmedom-bot
opened
2 weeks ago
1
Fix broken reference
#97
clelland
closed
3 months ago
0
Broken references in Server Timing
#96
dontcallmedom-bot
closed
3 months ago
0
PerformanceServerTiming entry always has a duration field even when the original header did not
#95
andydavies
opened
6 months ago
3
Add `[SecureContext]` tag to the interface
#94
OnkarRuikar
closed
1 month ago
2
Editorial: Note about millis
#93
noamr
closed
1 year ago
0
Fix broken references to INFRA#map.
#92
clelland
closed
1 year ago
0
Broken references in Server Timing
#91
dontcallmedom-bot
closed
1 year ago
0
Allow user agents to keep same-origin restrictions on PerformanceServ…
#90
achristensen07
closed
1 year ago
2
Privacy and Security section should mention that a user agent may choose to not expose cross-origin PerformanceServerTiming entries even with TAO
#89
achristensen07
closed
1 year ago
10
Spec is broken
#88
npm1
closed
2 years ago
2
Add explicit parsing rules for FETCH integration
#87
noamr
closed
2 years ago
3
Make it clearer what the units for `duration` are
#86
npm1
closed
1 year ago
1
Should PerformanceServerTiming inherit from PerformanceEntry?
#85
npm1
closed
2 years ago
1
Expose everywhere
#84
Ms2ger
closed
2 years ago
1
Server-Timing header field isn't registered
#83
mnot
closed
2 years ago
3
Switch to GitHub action
#81
plehegar
closed
3 years ago
0
Clarify security context for PerformanceResourceTiming
#79
fred-wang
closed
2 years ago
7
Nested hierarchy and grouping of sub-tasks
#78
ibnesayeed
closed
2 years ago
1
Server-Timing is too limited in scope, rename to Server-Metrics
#77
plutora-steve-g
opened
4 years ago
2
chore: fix default toJSON linking error
#76
sidvishnoi
closed
4 years ago
1
chore: fix ReSpec linking error
#74
sidvishnoi
closed
4 years ago
0
Respec errors
#73
yoavweiss
closed
4 years ago
2
API for fetching other metadata
#72
hauleth
opened
4 years ago
0
Exposing data on production
#71
SilentImp
closed
4 years ago
1
chore: update ReSpec syntax and error fixes
#70
sidvishnoi
closed
4 years ago
11
Creation time of PerformanceServerTiming objects unclear
#69
annevk
closed
2 years ago
4
Multiple trailer "chunks" each containing server-timing
#68
annevk
opened
4 years ago
0
Server Timing can be used a persistent 3rd party identifier
#67
JibberJim
closed
4 years ago
9
Add conformance section
#66
tidoust
closed
4 years ago
0
Using Server-timing to carry TraceID
#65
plehegar
closed
4 years ago
8
Support in the Firefox DevTools?
#64
SilentImp
closed
5 years ago
3
TAO is not fully aligned with ACAO
#63
youennf
closed
5 years ago
2
Correct encoded values in sample response body
#62
fj
closed
5 years ago
6
Privacy/Security Review
#61
toddreifsteck
opened
5 years ago
1
Trailer processing should be optional
#60
cvazac
closed
5 years ago
0
Specify behavior for user-agents who only support secure contexts
#59
cvazac
closed
5 years ago
0
Relax (or remove) trailer processing requirement
#58
igrigorik
closed
5 years ago
3
Update web-platform-tests URL
#57
foolip
closed
6 years ago
2
Server-Timing header and opaque responses
#56
youennf
closed
5 years ago
6
Fetch integration is missing
#55
annevk
closed
2 years ago
4
Limiting sever timing to secure origins
#54
valenting
closed
5 years ago
14
Add example with both dur and desc
#53
paulirish
closed
6 years ago
1
clarify extraneous characters after names
#52
cvazac
closed
6 years ago
0
clarify extraneous characters after names
#51
cvazac
closed
6 years ago
1
remove empty anchor
#50
cvazac
closed
6 years ago
4
clarify processing after incomplete or invalid param
#49
cvazac
closed
6 years ago
0
clarify invalid params
#48
cvazac
closed
6 years ago
5
clarify duplicate param names
#47
cvazac
closed
6 years ago
3
Next