#326: Element Timing API for images
Discussions
2019-07-03
(And Event Timing API)
Dan: Was there a breakout..?
David: I was supposed to and I didn't :(
... I have been being productive and ignoring my to-do list.
Dan: Will you be able to get one organised?
David: Let's bump this two weeks because I suspect holidays will interfere this week.
... Same goes for the next topic (Event Timing API - @dbaron, @kenchris)
Dan: Are they blocked on us?
David: Not that I'm aware of
2019-07-17
David: the order has the harder one first. there was a bunch of stuff related to text that wasn't fleshed out last time we looked. we should probably split images and texts into different reivews
kenneth: they also had questions re shadow dom, and wanted to move this to web performance
David: (currently WICG)
torgo: doing something useful and specific sounds like the right approach to me.
David: Yes. We should probably open the other review ourselves for text and close this one.
Originally this wasn't meant to include text... we tried to add it in, but that probably wasn't ideal.
Assuming Kenneth is okay with the images part
Kenneth: Yes
OpenedNov 16, 2018
こんにちはTAG！
I'm requesting a TAG review of:
Further details (optional):
Security and Privacy Questionnaire: https://docs.google.com/document/d/15T51ya-7GCtDQGF_ukGAPXBkygI6WFZBV9e9Bc8mjic/edit
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):