3) Add soft_navigation_count to LargestContentfulPaintTiming,why add soft_navigation_count to LCP? That feels out of place.
If you need an ID, you can call it navigationId or interactionId, even if you use "count" as the id in early prototype?
mojo_base.mojom.TimeTicks layout_shift_time;Michal MocnyThis will be compared with SoftNavigationMetrics.commit_time, when we interpret the render_data's new_layout_shifts, which arrive as a parameter of the UpdateTiming call.
The only risk with this is that the timestamp of layout shifts is sort of unique and different relative to paint timings.
If you had:
... then Layout Shifts get attributed to this URL.
If you had:
... then Layout Shifts get attributed to the previous URL.
---
We cannot easily move the timestamps around for spec / interop reasons, though we could consider making Shifts a paint timing and giving them a paintTime instead of their currently "random" middle-of-rendering time.
But we could consider forcing their navigationId to match "the current animation frame" navigationId, since the user sees this shift together with the other stuff, intra-frame ordering doesn't matter.
(Alternatively, we could expose a paintTime to LayoutShift just for internal metrics, if thats the direction)
mojo_base.mojom.TimeTicks start_time;Michal MocnyThis will be compared with SoftNavigationMetrics.commit_time, when we interpret the event_timings parameter of the UpdateTiming call.
Similar issue to Layout Shift, the start_time is the wrong unit of time for comparison (its async from the main thread).
But for INP we already plan to add paintTime very soon.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Johannes Henkel abandoned this change.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |