w3c/server-timing

Issues

• Normative references to discontinued specs in Server Timing

  #98 opened a month ago
  1

• Broken references in Server Timing

  #96 opened 4 months ago
  0

• PerformanceServerTiming entry always has a duration field even when the original header did not

  #95 opened 7 months ago
  3

• Broken references in Server Timing

  #91 opened 2 years ago
  0

• Privacy and Security section should mention that a user agent may choose to not expose cross-origin PerformanceServerTiming entries even with TAO

  #89 opened 2 years ago
  10

• Spec is broken

  #88 opened 2 years ago
  2

• Make it clearer what the units for `duration` are

  #86 opened a year ago
  1

• Should PerformanceServerTiming inherit from PerformanceEntry?

  #85 opened 2 years ago
  1

• Server-Timing header field isn't registered

  #83 opened 3 years ago
  3

• Clarify security context for PerformanceResourceTiming

  #79 opened 3 years ago
  7

• Nested hierarchy and grouping of sub-tasks

  #78 opened 2 years ago
  1

• Server-Timing is too limited in scope, rename to Server-Metrics

  #77 opened 4 years ago
  2

• Respec errors

  #73 opened 4 years ago
  2

• API for fetching other metadata

  #72 opened 4 years ago
  0

• Exposing data on production

  #71 opened 5 years ago
  1

• Creation time of PerformanceServerTiming objects unclear

  #69 opened 2 years ago
  4

• Multiple trailer "chunks" each containing server-timing

  #68 opened 5 years ago
  0

• Server Timing can be used a persistent 3rd party identifier

  #67 opened 5 years ago
  9

• Using Server-timing to carry TraceID

  #65 opened 4 years ago
  8

• Support in the Firefox DevTools?

  #64 opened 5 years ago
  3

• TAO is not fully aligned with ACAO

  #63 opened 6 years ago
  2

• Privacy/Security Review

  #61 opened 6 years ago
  1

• Relax (or remove) trailer processing requirement

  #58 opened 6 years ago
  3

• Server-Timing header and opaque responses

  #56 opened 6 years ago
  6

• Fetch integration is missing

  #55 opened 2 years ago
  4

• Limiting sever timing to secure origins

  #54 opened 6 years ago
  14

• clarify extraneous characters after names

  #51 opened 6 years ago
  1

• clarify invalid params

  #48 opened 7 years ago
  5

• clarify incomplete params

  #46 opened 7 years ago
  4

• expand description field to allow json instead of just quoted-string and token

  #45 opened 7 years ago
  6

• add total to distinguish between calendar time and effort time

  #44 opened 7 years ago
  2

• add start time to distinguish between cached and active entries

  #43 opened 7 years ago
  6

• Evaluate current parsing error strategy

  #42 opened 2 years ago
  5

• Consider shorter names for the attributes

  #40 opened 7 years ago
  6

• Future considerations

  #39 opened 7 years ago
  8

• RT and NT processing is not well defined

  #38 opened 2 years ago
  3

• readdress TAO

  #35 opened 7 years ago
  3

• Incorporating feedback from TAG review

  #32 opened 7 years ago
  7

• Transition Level 1 to CR

  #24 opened 7 years ago
  1

• Visualizing `value` for server timing entries

  #22 opened 7 years ago
  8

• Link to a defined extension hook in Resource Timing & Nav Timing

  #19 opened 7 years ago
  2

• Setup travis

  #17 opened 7 years ago
  2

• Linking to ResourceTiming

  #14 opened 7 years ago
  4

• Server-Timing Headers Read from Browser Cache

  #13 opened 7 years ago
  6

• ABNF for metric-value

  #12 opened 7 years ago
  34

• Spec should clarify that metrics are in seconds

  #11 opened 8 years ago
  3

• Having duration with no start time makes it hard to profile servers with parallel processes.

  #10 opened 7 years ago
  8

• Secure context only

  #9 opened 7 years ago
  3

• Metric values are timestamps in PerformanceServerTiming interface

  #7 opened 8 years ago
  2

• Rendering bug in the spec

  #5 opened 8 years ago
  15