service worker: Fix navigation-preload/resource-timing.https.html test
Before this CL, this test tried to get performance entries right after Response#text() is resolved, but Chrome doesn't guarantee that there will be a performance entry for the response at that point. This CL changes the test to use PerformanceObserver so that we can make sure that there will be a performance entry for the response. Bug: 872078 Change-Id: I6ecfcb8e0721df541d5a32f56ec4c062efbffdae Reviewed-on: https://chromium-review.googlesource.com/1170679 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#583483}
Showing
Please register or sign in to comment