Instrument usage of browser's find function
Context
With virtual scrolling, the browser's find function (CMD+F
) is not able to find all of the possible matches since virtual scrolling “removes” content from the DOM. Because of this, it's not obvious that the find function is not working correctly — it may return an incorrect number of matches. The only way to be sure is to manually scroll through the diffs while re-checking the browser's find function.
In summary, with virtual scrolling, users won't know if the browser's find function is working correctly or not, but it's likely that they will accept the find results because they don't have any reasons to suspect that it's misbehaving. Instrumenting the usage of this find function will help us understand the urgency of Address browser find function with virtual scrolling on MRs.
We want to track both users and counts. Users can help understand the potential reach (e.g. X users have used this last month), and counts can help understand the potential impact (e.g. on average, users use this X times per day).
Proposal
See https://stackoverflow.com/a/6680403 for possible ways to track the keyboard shortcuts that trigger browser's find function.
Note: be mindful of cross-platform compatibility (CMD vs CTRL, etc.).