New issue
Advanced search Search tips

Issue 895496 link

Starred by 1 user
Status: Assigned
Owner:
chaopeng@chromium.org
Cc:
bokan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Bug

Blocking:
issue 841843



Sign in to add a comment

implement metrics to measure impact of 'scroll to css selector'

Project Member Reported by bmcquade@chromium.org, Oct 15 
As part of launching support for scroll to css selector we should add metrics to understand:
* how often it is used
* how often it finds a matching element
* how often it fails to find a matching element

In addition there were some potential metrics discussed in the I2I for this feature that we should also consider implementing.

Comment 1 by bokan@chromium.org, Nov 8

Cc: bokan@chromium.org
Labels: -Pri-3 M-73 OS-Android OS-Chrome OS-Linux OS-Mac OS-Windows Pri-1
Owner: chaopeng@chromium.org
Status: Assigned (was: Available)
For reference, I2I thread: https://groups.google.com/a/chromium.org/forum/#!searchin/blink-dev/css$20fragment$20selector$20scroll%7Csort:date/blink-dev/aKI6doxffgQ/VhYi6bO7AQAJ

One of the things to measure requested in that thread is how often the fragment matches an id on the page. E.g. We should measure how often we navigate to a page with #targetElement=.myselector but that page has <div id='targetElement=.mySelector'>.

I think we should also add a counter to check if existing pages already use targetElement=* in their fragments.
►

Sign in to add a comment