UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36
Steps to reproduce the problem:
Log aborts before user interaction in Page Load Metrics
What is the expected behavior?
This allows us to track user aborts before any user interaction on the page. It'd better filter user aborts because of page quality / satisfaction from aborts because of page loads.
What went wrong?
This helps to user behavior analysis on user perceived latency.
Did this work before? N/A
Chrome version: 50.0.2661.94 Channel: stable
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0
Comment 1 by dgozman@chromium.org
, May 17 2016