[Chore] Replace Chromium with Chrome
See the Chromium style guide: https://chromium.googlesource.com/chromium/src/+/HEAD/styleguide/c++/c++.md#naming
Bug: none
Change-Id: I899b40da7c9fca7e1772ce976eab5af0b50cdd63
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7001336
Commit-Queue: Paul Irish <[email protected]>
Reviewed-by: Paul Irish <[email protected]>
diff --git a/front_end/models/trace/types/TraceEvents.ts b/front_end/models/trace/types/TraceEvents.ts
index 8c45b44..dd50216 100644
--- a/front_end/models/trace/types/TraceEvents.ts
+++ b/front_end/models/trace/types/TraceEvents.ts
@@ -124,10 +124,10 @@
processId: ProcessID;
url: string;
parent?: string;
- // Added to Chromium in April 2024:
+ // Added to Chrome in April 2024:
// crrev.com/c/5424783
isOutermostMainFrame?: boolean;
- // Added to Chromium in June 2024:
+ // Added to Chrome in June 2024:
// crrev.com/c/5595033
isInPrimaryMainFrame?: boolean;
}
@@ -549,7 +549,6 @@
* consuming screenshot events from the ScreenshotHandler, you must make sure
* to have your code deal with the two different formats.
*/
-// These are nullable because in January 2025 a CL in Chromium
export interface LegacyScreenshot extends Event {
/**
* @deprecated This value is incorrect. Use ScreenshotHandler.getPresentationTimestamp()
@@ -745,7 +744,7 @@
nodeId: Protocol.DOM.BackendNodeId,
loadingAttr: string,
type?: string,
- // Landed in Chromium M140: crrev.com/c/6702010
+ // Landed in Chrome M140: crrev.com/c/6702010
nodeName?: string,
},
};
@@ -990,7 +989,7 @@
export const NO_NAVIGATION = 'NO_NAVIGATION';
/**
- * This maybe be a navigation id string from Chromium, or `NO_NAVIGATION`, which represents the
+ * This maybe be a navigation id string from Chrome, or `NO_NAVIGATION`, which represents the
* portion of the trace for which we don't have any navigation event for (as it happeneded prior
* to the trace start).
*/
