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

[a11y-request] Issue: User Timing 2021-06-02 > 2021-06-23 (#5) marked as REVIEW REQUESTED

From: caribouW3 via GitHub <sysbot+gh@w3.org>
Date: Wed, 02 Jun 2021 14:54:56 +0000
To: public-apa@w3.org
Message-ID: <issues.labeled-909592028-None-sysbot+gh@w3.org>
caribouW3 has just labeled an issue for https://github.com/w3c/a11y-request as "REVIEW REQUESTED":

== User Timing 2021-06-02 > 2021-06-23 ==
- name of spec to be reviewed: User Timing 
- URL of spec: https://w3c.github.io/user-timing/ 

- What and when is your next expected transition? 
https://github.com/w3c/transitions/issues/338#issuecomment-850636248
Wide review was already done for level 2. The WG wants to drop levels and merge level 3 in it.
The Director is requesting a formal wide review with the most recent horizontal review process.

- What has changed since any previous review? 
In level 3, addition of ability to execute marks and measures across arbitrary timestamps and
support for reporting arbitrary metadata along with marks and measures.

- 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/user-timing/issues/
 
- Pointer to any explainer for the spec? 
https://w3c.github.io/user-timing/#introduction


See https://github.com/w3c/a11y-request/issues/5


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

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:08 UTC