[w3ctag/design-reviews] Element Timing API for img (#326)

こんにちはTAG！

I'm requesting a TAG review of:

  - Name: ElementTiming
  - Explainer: we currently only have this [doc](https://docs.google.com/document/d/1blFeMVdqxB0V3BAJh60ptOBFY7cJSXnf7VyW3wspbZ8/)
  - Tests: not yet in WPT, we have [some](https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/http/tests/performance-timing/element-timing/?q=element-timing&sq=package:chromium&dr) in Chrome, which we'll move when standardized.
  - Primary contacts: @npm1 @tdresser

Further details (optional):

  - Relevant time constraints or deadlines: Chrome has implemented this feature but we haven't fleshed out the spec yet. We'd probably like to launch early 2019.
  - We have a Chrome launch [bug](https://bugs.chromium.org/p/chromium/issues/approval?id=883483) (sorry, Googlers only), which received privacy and security approvals. If you'd like me to fill out the Security and Privacy Questionnaire, let me know.

You should also know that...

The current proposal is for ElementTiming for `<img>` elements, but we received feedback at TPAC that including background images in our first iteration could also be very helpful. So we may add that. Later versions of this API would like to expose other elements, but for most we will need to think about text rendering timing. We are deferring that to a future version of this API.

We'd prefer the TAG provide feedback as (please select one):

  - [X] leave review feedback as a comment in this issue and @-notify @npm1 and @tdresser


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/326