A proposal from Google's team to add HTTP header-based performance data reporting without requiring JavaScript. Key benefits include:
Discussion points: Challenges around data reconciliation between declarative and JavaScript-based reporting, and the need for flexible dimensions like session IDs.
A proposal from Yoav to add a "landing" attribute to indicate whether a page is the first navigation in a tab/session.
Value: Helps segment RUM data between first visits and subsequent navigations, which have vastly different performance characteristics. Currently, RUM solutions use heuristics like referrer checks and session cookies.
Status: The original PR was very basic; needs further development and community input on definition and implementation.
Barry Pollard presented the long-awaited soft navigation feature, now available in Chrome 151 (unflagged and stable). This addresses SPAs where route changes weren't previously measured.
Key capabilities:
Important caveats:
DevTools support: Chrome DevTools and Chrome 152 show soft nav metrics; CrUX support coming with experimental data.
Next steps: Barry encouraged the community to test, provide feedback, and advocate for cross-browser support.
A fix for fetch later on the last tab of a browser (Chrome 153) ensures beacons send even when closing the browser, making it a truly reliable beacon mechanism.
Strong turnout with 28 participants at one point, including new and returning members.