Issue metadata
Sign in to add a comment
|
No data received for loading.mobile from android-nexus6 since 458252 |
||||||||||||||||||||
Issue descriptionNed, looks like we are no longer getting timeToFirstContentfulPaint on loading.mobile. From the revisions I'm guessing this could be caused byt "Remove TTI wait for loading.mobile pages". Was this intended?
,
Apr 28 2017
We shouldn't lose timeToFirstContentfulPaint by removing the wait for TTI. ksakamoto@: can you help investigate?
,
May 8 2017
It seems these pages are affected: http://www.bradesco.com.br http://www.dramaq.com.tw http://www.gsshop.com http://www.locanto.in They do not render anything contentful, but just jump to another URL by changing window.location.href. Currently we use WaitForDocumentReadyStateToBeComplete but it may return before location.href change. Maybe we should wait for HasReachedQuiescence()?
,
May 8 2017
Changing to HasReachedQuiescence sgtm.
,
May 11 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0c42bb9692ce450bee3e9db90982faba46349f3d commit 0c42bb9692ce450bee3e9db90982faba46349f3d Author: ksakamoto <ksakamoto@chromium.org> Date: Thu May 11 04:34:44 2017 Wait for network quiescence in loading.mobile pages Some pages in loading.mobile use location.href to redirect to their mobile site. WaitForDocumentReadyStateToBeComplete() does not wait such second navigation, so this patch changes PageCyclerStory to wait for network quiescence. Note to perf sheriffs: This may affect loading.mobile benchmark, as this will fix a bug where metrics for some navigations were not recorded. BUG= 716433 Review-Url: https://codereview.chromium.org/2867283002 Cr-Commit-Position: refs/heads/master@{#470805} [modify] https://crrev.com/0c42bb9692ce450bee3e9db90982faba46349f3d/tools/perf/page_sets/page_cycler_story.py
,
May 15 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rmcilroy@chromium.org
, Apr 28 2017