Issue metadata
Sign in to add a comment
|
DOMContentLoaded Blue bar timing incorrectly reported
Reported by
bruno.ra...@gmail.com,
May 2 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36 Steps to reproduce the problem: 1. Go to https://mywebbrowser.info/ 2. Open the timeline panel 3. Reload and watch the timeline What is the expected behavior? The blue bar should report the DOMContentLoaded timing right before the Event (DOMContentLoaded) block, and before the 'window.load' red bar. What went wrong? The blue bar almost consistently misreports the DOMContentLoaded line+timing to have occurred after the 'load', especially on reloads. Did this work before? No Chrome version: 59.0.32071.29 Channel: beta OS Version: OS X 10.10.5 Flash Version: Start observing this last year on multiple sites along using my ua.js script which pretty much listens to and fire all window events in order, as well as polyfill them. Not sure at all what causes this.
,
May 2 2017
Issue 717387 has been merged into this issue.
,
May 2 2017
,
Jul 14 2017
Seems related to bug 596899 .Hence merging this into 596899. Please feel free to undupe if not similar. Thanks, |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bruno.ra...@gmail.com
, May 2 2017