Re: [w3ctag/design-reviews] Element Timing API (images and text) (#326)

@kenchris and I are looking at this in a breakout in the TAG face-to-face in Reykjavík.

I think we're both OK with using this review to cover both images and text -- though based on a quick skim it seems like text is currently covered only in the explainer but not in the text.  Is that correct?  That said, it seems like it might also make sense to separate if they're going to progress at substantially different rates.  It seems like the text parts probably need to be developed a good bit more before we can really review them, since it's not yet clear what they are.

A few thoughts:
* one thing I'm a little concerned about is implicit registration.  It seems like it might have substantial performance overhead since finding out whether something *should* be implicitly registered seems like it would happen relatively late in the loading process, which would therefore require *everything* to be tracked up until that point, which might have a bit of overhead.  Is that the case?  (I notice there's a "TODO: fix implicit registration.") in the explainer.)
* does the API support vector images, or is it just raster images?  It's a little unclear.
* defining when images are fully loaded requires a little care for animated images.  Is the concern about the first frame of an animated raster image?
* there should probably be a formal-ish definition of the `elementtiming` attribute somewhere that is intended to be moved into the HTML spec eventually (and when that happens, this spec could link to it).
* How much discussion has there been of the naming here?  Is it better to call a bunch of different things `"element"` or to call image specific information `"image"`, etc.?
* This seems like it's tightly tied to the work that's done in the Web Performance Working Group -- to what extent has it been discussed with the other participants of that working group, and is there a plan to move it there?  (There were some points above that you said you *would* discuss there.)
* We're also curious what the level of urgency is -- are there plans to ship this soon?  Are those plans separate for images versus text?  (And if so, that also increases the urgency of bringing into the Web Performance WG and getting it discussed effectively there...)

-- 
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#issuecomment-494858816