Bug 202661 - Add support for Element Timing
Summary: Add support for Element Timing
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-07 17:21 PDT by Jash Sayani
Modified: 2022-07-01 15:06 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jash Sayani 2019-10-07 17:21:17 PDT
Add support for Element Timing API: https://wicg.github.io/element-timing/
Comment 1 Brent Fulgham 2022-07-01 15:06:31 PDT
As discussed in webkit-dev mailing list:

"Apple's WebKit team reviewed this API and we have a few concerns including
but not limited to:

   - The proposed API exposes timing at which a given element is painted.
   Implemented naively, this exposes the implementation detail of what kind of
   compositing tiles are used on a given web page. Hiding this
   implementation detail and recording the exact theoretical paint timing will
   be prohibitively expensive to do on all websites.
   - The definition of the set of owned text nodes and how they compute
   intersectionRect seems inadequate. It's unclear what "border box" of
   *Text* node would mean. The spec doesn't seem to ever populate "set of
   elements with rendered text" either.
   - The use of this API seems to incur a significant runtime as well as
   memory cost."

Moving to "RESOLVED | WONTFIX". We can reopen if we revisit this, or the spec issues are resolved.