You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What has changed since any previous review?
In comparison to previously published "level 1" (in CR), changes are mainly
the addition of the size attributes, better buffering algorithms and Fetch integration.
We plan to drop levels and use a living standard development model (from process2020).
name of spec to be reviewed: Resource Timing
URL of spec: https://w3c.github.io/resource-timing/
What and when is your next expected transition?
CR Request for Resource Timing -- shortname: resource-timing transitions#337 (comment)
Wide review was done in 2017. The Director is requesting a formal wide review with the most recent horizontal review process.
What has changed since any previous review?
In comparison to previously published "level 1" (in CR), changes are mainly
the addition of the size attributes, better buffering algorithms and Fetch integration.
We plan to drop levels and use a living standard development model (from process2020).
Please point to the results of your own self-review (see https://w3c.github.io/i18n-drafts/techniques/shortchecklist)
This specification relies on APIs, there is no natural language exposed, no text, no localization.
Where and how to file issues arising?
https://github.com/w3c/resource-timing/issues/
Pointer to any explainer for the spec?
https://w3c.github.io/resource-timing/#introduction
Other comments:
The text was updated successfully, but these errors were encountered: