element-timing
element-timing copied to clipboard
WICG
A proposal for an Element Timing specification.
Currently Element Timing only supports a small number of elements – image, text elements etc. Developers increasingly think in terms of components, some of these may be a more complex...
The spec doesn't appear to say how Element Timing for pseudo-elements should be handled. A surprising number of sites put large content in pseudo-elements, so explicit support would be helpful...
This replaces the unlinked "viewport" term with a link to the document's initial containing block, which will be the bounds of the browser window or iframe containing the document. Closes:...
Currently we only support image elements inside SVG, but SVG can have other things. It would be good to think about whether we need to provide more support for SVG....
Element Timing exposes rendering timing information about images (and we want to add text soon). It has some attributes which contain useful information for attribution such as `element`. However, right...
See https://github.com/whatwg/html/issues/8024
Since LCP [heavily relies on element timing](https://wicg.github.io/largest-contentful-paint/#biblio-element-timing), I wonder how exactly it does that, since it would need the timings of all elements on the page that could have a...
Why special case data: URLs? Other URLs can be thousands of code points as well...
We currently have a bunch of hardcoded references. We should try to get rid of them by exporting from the source (HTML and such).
I'm trying to wrap my head around https://wicg.github.io/element-timing/#sec-security and failing. Is "load time" different from Fetch's timing info's end time somehow?