Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[UserTimingL3] Fix meature, mark API feature detection #14084

Merged
merged 1 commit into from
Nov 15, 2018
Merged

[UserTimingL3] Fix meature, mark API feature detection #14084

merged 1 commit into from
Nov 15, 2018
+46 −0

Commits on Nov 15, 2018

  1. [UserTimingL3] Fix meature, mark API feature detection 

    UserTimingL3 uses returned value for feature detection. If measure and mark
API returns null, the APIs are L2 API; If the APIs return an entry, the APIs are
L3 API. However, in the current implementation, when L3 API is enabled, the
APIs do not always return the created entry.

This CL is to fix this bug, and add layout tests to verify it.

Change-Id: I9854f0abd0d64a3334701e09d6ce0fc245fcca3e
Reviewed-on: https://chromium-review.googlesource.com/c/1338225
Commit-Queue: Liquan (Max) Gǔ <[email protected]>
Reviewed-by: Nicolás Peña Moreno <[email protected]>
Cr-Commit-Position: refs/heads/master@{#608552}
    @maxlgu @chromium-wpt-export-bot
    maxlgu authored and chromium-wpt-export-bot committed Nov 15, 2018
    Configuration menu
    Copy the full SHA
    d38540d View commit details
    Browse the repository at this point in the history