-
Notifications
You must be signed in to change notification settings - Fork 8
Open
Description
Currently, the PerformanceContainerTiming IDL has these attributes and functions:
From PerformanceEntry: entryType, name, startTime, duration, navigationId, toJSON(). Those are coming from other specifications, so not the scope of the discussion here.
Then, for PerformanceContainerTiming itself:
intersectionRect: copied fromPerformanceElementTiming, the intersection of the paint rectangles in the viewport.size: the area in pixels of the view port that have been painted.identifier: the ID set as the parameter of thecontainertimingattribute. Again consistent withPerformanceElementTiming.lastPaintedElement: one of the element that has been painted last. We use theelementsuffix for consistency with theelementattribute in LCP, ICP.firstRenderTime: again, for consistency with what we get inPerformanceElementTiming, the fieldrenderTime, but this is the first render event.
And new attributes that are expected to land in the spec:
rootElement: the container timing root. With the suffixElementto give consistency withlastPaintedElement.
Also, we are moving to support the Paint Timing Mixin. This brings us two new attributes: paintTime and presentationTime.
Some problems:
identifierrefers to thecontainertimingattribute value. But we also have the node ID. Should it berootIdentifier?- Do we need the
Elementsuffix? This was for consistency with the fact that we have theelementattribute in other paint events, and to state the difference between the observed root and others. - The "root" concept may not be obvious. Specially if we want consistency with
elementtimingwhere we should also offer a reference to the observed element. If we want to add toPerformanceObserveran specific API for observing only a container timing root or element timing node, then... maybeobservedElement,observedorobservedRoot? firstRenderTime, but we do not offer arenderTimeattribute, as it is alwaysstartTime. We should likely add arenderTimeexplicitely for consistency. Specially if we could eventually move to unify the API.- Should we expose, if mixin is enabled,
firstPaintTimeandfirstPresentationTime? sizeis not very specific. Should we rename it to something likepaintedArea?lastPaintedElement: should it belastRenderedElement?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels