Skip to content

GitLab

T
tangled
Commit ff416310 authored by Liquan(Max) Gu's avatar Liquan(Max) Gu Committed by Commit Bot
Browse files
Options

[FCP++] Fix inconsistency between PageLoadTimingStatus and enums.xml 

We introduced a bug in cl/1283474. The added item should have been to the end
of PageLoadTimingStatus, and corresponding change should have been made to
enums.xml. And, the added item was actually not necessary. This Cl remove the
introduced item.

Bug: 869924
Change-Id: Idedde9b86f82ea027cb7924369364f068559a82e
Reviewed-on: https://chromium-review.googlesource.com/c/1297743Reviewed-by: default avatarBryan McQuade <bmcquade@chromium.org>
Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602351}
parent 2de0dc43
Hide whitespace changes
Inline Side-by-side
Showing with 0 additions and 1 deletion
chrome/browser/page_load_metrics/page_load_metrics_update_dispatcher.h
View file @ ff416310
...@@ -62,7 +62,6 @@ enum PageLoadTimingStatus { ...@@ -62,7 +62,6 @@ enum PageLoadTimingStatus {
INVALID_ORDER_FIRST_PAINT_FIRST_CONTENTFUL_PAINT, INVALID_ORDER_FIRST_PAINT_FIRST_CONTENTFUL_PAINT,
INVALID_ORDER_FIRST_PAINT_FIRST_MEANINGFUL_PAINT, INVALID_ORDER_FIRST_PAINT_FIRST_MEANINGFUL_PAINT,
INVALID_ORDER_FIRST_MEANINGFUL_PAINT_PAGE_INTERACTIVE, INVALID_ORDER_FIRST_MEANINGFUL_PAINT_PAGE_INTERACTIVE,
INVALID_ORDER_FIRST_CONTENTFUL_PAINT_LARGEST_IMAGE_PAINT,
// We received a first input delay without a first input timestamp. // We received a first input delay without a first input timestamp.
INVALID_NULL_FIRST_INPUT_TIMESTAMP, INVALID_NULL_FIRST_INPUT_TIMESTAMP,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment