Closed Bug 1513657 Opened 8 months ago Closed 8 months ago
_FRAME _TIME is now using the refresh driver tick start time instead of the transaction start
Bug 1513657 - Record CONTENT_FRAME_TIME_REASON after CONTENT_FRAME_TIME so that we don't clobber the calculations. r?jrmuizel
47 bytes, text/x-phabricator-request
|Details | Review|
This is a regression from bug 1510853, where I added CONTENT_FRAME_TIME_REASON (which intentionally uses the refresh driver tick start), and it clobbers the value used by CONTENT_FRAME_TIME.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/2d581255f6d4 Record CONTENT_FRAME_TIME_REASON after CONTENT_FRAME_TIME so that we don't clobber the calculations. r=jrmuizel
You need to log in before you can comment on or make changes to this bug.