commit | 22898e830b2a064bd160c58cb46f60bb41628291 | [log] [tgz] |
---|---|---|
author | Aoyuan Zuo <zuoaoyuan@chromium.org> | Wed Jan 24 17:21:39 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 24 17:21:39 2024 |
tree | 439a01ae977920bb17d7f0715474a2bc012dab2f | |
parent | ab1b775e008fd1108ffbdcc60c3d93abc4582fb7 [diff] |
Post EventTimingMatchPresentationIndex Launch Cleanup Since the EventTimingMatchPresentationIndex finch experiment has diverged event timing into two code paths and it's now launched, we remove those code paths that are no longer reachable and clean up those obsolete use counters & histograms. - feature flags removed since launched: * EventTimingMatchPresentationIndex - feature flags removed since abandoned: * EventTimingReportAllEarlyEntriesOnPaintedPresentation - histograms removed: * PageLoad.Internal.EventTiming.PendingPresentationPromiseCount - use counters removed: * EventTimingPresentationPromiseResolvedAfterReport * EventTimingPaintedPresentationPromiseResolvedWithEarlierPromiseUnresolved OBSOLETE_HISTOGRAM[PageLoad.Internal.EventTiming.PendingPresentationPromiseCount]=Remove prior launch analysis after EventTimingMatchPresentationIndex is launched. Bug: 1425540 Change-Id: I2f1dd425ba0808fb621cc0c104a02d62258dce78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5225107 Commit-Queue: Aoyuan Zuo <zuoaoyuan@chromium.org> Reviewed-by: Alison Maher <almaher@microsoft.com> Reviewed-by: Michal Mocny <mmocny@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/main@{#1251478}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.