W3C home > Mailing lists > Public > public-apa@w3.org > June 2021

[a11y-request] Resource Timing 2021-06-02 > 2021-06-23 (#4)

From: caribouW3 via GitHub <sysbot+gh@w3.org>
Date: Wed, 02 Jun 2021 14:53:29 +0000
To: public-apa@w3.org
Message-ID: <issues.opened-909590515-1622645606-sysbot+gh@w3.org>
caribouW3 has just created a new issue for https://github.com/w3c/a11y-request:

== Resource Timing 2021-06-02 > 2021-06-23 ==
- 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?
w3c/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/apa/fast/checklist.html)
This specification relies on APIs, the API can't be used for structured content, the API does not rely on 
user agents to generate a user interface.

- 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


Please view or discuss this issue at https://github.com/w3c/a11y-request/issues/4 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 June 2021 14:54:11 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 2 June 2021 14:54:33 UTC