add support for tracking same-page navigations in page load metrics |
|||||||
Issue descriptionThe current PLM implementation ignores same page navigations. As same page navigations become more common, in particular as they are used for AMP page views from Google Search, we should figure out how to track them. We may not want to track all same-page navs. In particular we likely want to ignore same-page navs where the document URL is unchanged (e.g. fragment navigations). It's also a bit unclear what constitutes a 'first paint' for same-page navs - perhaps the first paint after the navigation is initiated?
,
May 4 2017
,
Aug 15 2017
Assigning this to Max - Bryan, let me know if you are planning to get to this, but last time we talked, it didn't sound like it. The first step is improving our metrics on the frequency of same document navigations.
,
Aug 15 2017
I'm happy to take this but I think it'd be ideal for someone else to drive it, so we can increase familiarity with the page load metrics codebase across the org.
,
Nov 23 2017
There's some debate about priority here - I'll follow up once we've sorted this out.
,
Mar 15 2018
,
Jun 27 2018
Any update?
,
Jun 27 2018
,
Jul 4
Thanks Annie for taking it!
,
Nov 26
Ping! This bug has been flagged as stale by Chrome Speed Metrics bug triage, and it has an owner. Any update on this issue? |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by bmcquade@chromium.org
, Mar 20 2017