chrome-devtools-frontend 1.0.1681498 → 1.0.1683520

package/front_end/models/ai_assistance/agents/PerformanceAgent.snapshot.txt

@@ -38,7 +38,7 @@ Content:
     "details": [
       {
         "title": "Trace details",
-        "text": "Trace summary:\nURL: https://chromedevtools.github.io/performance-stories/lcp-large-image/index.html\nTrace bounds: {min: 658799706428µs, max: 658804825864µs}\nCPU throttling: 1x\nNetwork throttling: No throttling\n\n# Available insight sets\n\nThe following is a list of insight sets. An insight set covers a specific part of the trace, split by navigations. The insights within each insight set are specific to that part of the trace. Be sure to consider the insight set id and bounds when calling functions. If no specific insight set or navigation is mentioned, assume the user is referring to the first one.\n\n## insight set id: NAVIGATION_0\n\nURL: https://chromedevtools.github.io/performance-stories/lcp-large-image/index.html\nBounds: {min: 658799738257µs, max: 658804825864µs}\nMetrics (lab / observed):\n  - LCP: 110 ms, event: (eventKey: r-2399, ts: 658799847880), nodeId: 10\n  - LCP breakdown:\n    - TTFB: 7 ms, bounds: {min: 658799738257µs, max: 658799745193µs}\n    - Load delay: 34 ms, bounds: {min: 658799745193µs, max: 658799778937µs}\n    - Load duration: 12 ms, bounds: {min: 658799778937µs, max: 658799791032µs}\n    - Render delay: 57 ms, bounds: {min: 658799791032µs, max: 658799847880µs}\n  - CLS: 0.00\nMetrics (field / real users): n/a – no data for this page in CrUX\nAvailable insights:\n  - insight name: LCPBreakdown\n    description: Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.\n    relevant trace bounds: {min: 658799738257µs, max: 658799847880µs}\n    example question: Help me optimize my LCP score\n    example question: Which LCP subpart was most problematic?\n    example question: What can I do to reduce the LCP time for this page load?\n  - insight name: LCPDiscovery\n    description: [Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading\n    relevant trace bounds: {min: 658799745193µs, max: 658799793683µs}\n    example question: Suggest fixes to reduce my LCP\n    example question: What can I do to reduce my LCP discovery time?\n    example question: Why is LCP discovery time important?\n  - insight name: RenderBlocking\n    description: Requests are blocking the page’s initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.\n    relevant trace bounds: {min: 658799775876µs, max: 658799791419µs}\n    example question: Show me the most impactful render-blocking requests that I should focus on\n    example question: How can I reduce the number of render-blocking requests?\n  - insight name: Cache\n    description: A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).\n    relevant trace bounds: {min: 658799777502µs, max: 658799791419µs}\n    example question: What caching strategies can I apply to improve my page performance?\n# Critical network requests\n\nnone\n\n# Main thread bottom-up summary\n\nThis is the bottom-up summary for the entire trace. Only the top 10 activities (sorted by self time) are shown. An activity is all the aggregated time spent on the same type of work. For example, it can be all the time spent in a specific JavaScript function, or all the time spent in a specific browser rendering stage (like layout, v8 compile, parsing html). \"Self time\" represents the aggregated time spent directly in an activity, across all occurrences. \"Total time\" represents the aggregated time spent in an activity or any of its children.\n\n- self: 57 ms, total: 79 ms, source: Task\n- self: 5 ms, total: 5 ms, source: Layout\n- self: 4 ms, total: 4 ms, source: Major GC\n- self: 3 ms, total: 3 ms, source: Parse HTML\n- self: 2 ms, total: 2 ms, source: Recalculate style\n- self: 2 ms, total: 2 ms, source: Commit\n- self: 1 ms, total: 1 ms, source: C++ GC\n- self: 1 ms, total: 1 ms, source: Paint\n\n# 3rd party summary\n\n- name: GitHub, main thread time: 3 ms, network transfer size: 0 B\n\n# Longest tasks\n\n- total time: 23 ms, event: (eventKey: r-617, ts: 658799757023)\n- total time: 12 ms, event: (eventKey: r-1571, ts: 658799793885)\n- total time: 11 ms, event: (eventKey: r-1891, ts: 658799811130)\n\nUser selected the LCPBreakdown insight.\n\n\n# User query\n\ntest"
+        "text": "Trace summary:\nURL: https://chromedevtools.github.io/performance-stories/lcp-large-image/index.html\nTrace bounds: {min: 658799706428µs, max: 658804825864µs}\nCPU throttling: 1x\nNetwork throttling: No throttling\n\n# Available insight sets\n\nThe following is a list of insight sets. An insight set covers a specific part of the trace, split by navigations. The insights within each insight set are specific to that part of the trace. Be sure to consider the insight set id and bounds when calling functions. If no specific insight set or navigation is mentioned, assume the user is referring to the first one.\n\n## insight set id: NAVIGATION_0\n\nURL: https://chromedevtools.github.io/performance-stories/lcp-large-image/index.html\nBounds: {min: 658799738257µs, max: 658804825864µs}\nMetrics (lab / observed):\n  - LCP: 110 ms, event: (eventKey: r-2399, ts: 658799847880), nodeId: 10\n  - LCP breakdown:\n    - TTFB: 7 ms, bounds: {min: 658799738257µs, max: 658799745193µs}\n    - Load delay: 34 ms, bounds: {min: 658799745193µs, max: 658799778937µs}\n    - Load duration: 12 ms, bounds: {min: 658799778937µs, max: 658799791032µs}\n    - Render delay: 57 ms, bounds: {min: 658799791032µs, max: 658799847880µs}\n  - CLS: 0.00\nMetrics (field / real users): n/a – no data for this page in CrUX\nAvailable insights:\n  - insight name: LCPBreakdown\n    description: Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.\n    relevant trace bounds: {min: 658799738257µs, max: 658799847880µs}\n    example question: Help me optimize my LCP score\n    example question: Which LCP subpart was most problematic?\n    example question: What can I do to reduce the LCP time for this page load?\n  - insight name: LCPDiscovery\n    description: [Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading.\n    relevant trace bounds: {min: 658799745193µs, max: 658799793683µs}\n    example question: Suggest fixes to reduce my LCP\n    example question: What can I do to reduce my LCP discovery time?\n    example question: Why is LCP discovery time important?\n  - insight name: RenderBlocking\n    description: Requests are blocking the page’s initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.\n    relevant trace bounds: {min: 658799775876µs, max: 658799791419µs}\n    example question: Show me the most impactful render-blocking requests that I should focus on\n    example question: How can I reduce the number of render-blocking requests?\n  - insight name: Cache\n    description: A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).\n    relevant trace bounds: {min: 658799777502µs, max: 658799791419µs}\n    example question: What caching strategies can I apply to improve my page performance?\n# Critical network requests\n\nnone\n\n# Main thread bottom-up summary\n\nThis is the bottom-up summary for the entire trace. Only the top 10 activities (sorted by self time) are shown. An activity is all the aggregated time spent on the same type of work. For example, it can be all the time spent in a specific JavaScript function, or all the time spent in a specific browser rendering stage (like layout, v8 compile, parsing html). \"Self time\" represents the aggregated time spent directly in an activity, across all occurrences. \"Total time\" represents the aggregated time spent in an activity or any of its children.\n\n- self: 57 ms, total: 79 ms, source: Task\n- self: 5 ms, total: 5 ms, source: Layout\n- self: 4 ms, total: 4 ms, source: Major GC\n- self: 3 ms, total: 3 ms, source: Parse HTML\n- self: 2 ms, total: 2 ms, source: Recalculate style\n- self: 2 ms, total: 2 ms, source: Commit\n- self: 1 ms, total: 1 ms, source: C++ GC\n- self: 1 ms, total: 1 ms, source: Paint\n\n# 3rd party summary\n\n- name: GitHub, main thread time: 3 ms, network transfer size: 0 B\n\n# Longest tasks\n\n- total time: 23 ms, event: (eventKey: r-617, ts: 658799757023)\n- total time: 12 ms, event: (eventKey: r-1571, ts: 658799793885)\n- total time: 11 ms, event: (eventKey: r-1891, ts: 658799811130)\n\nUser selected the LCPBreakdown insight.\n\n\n# User query\n\ntest"
       }
     ],
     "widgets": [

package/front_end/models/ai_assistance/agents/PerformanceAgent.ts

@@ -5,7 +5,6 @@
 import * as Common from '../../../core/common/common.js';
 import * as Host from '../../../core/host/host.js';
 import * as i18n from '../../../core/i18n/i18n.js';
-import type {UrlString} from '../../../core/platform/DevToolsPath.js';
 import type * as Platform from '../../../core/platform/platform.js';
 import * as Root from '../../../core/root/root.js';
 import * as SDK from '../../../core/sdk/sdk.js';
@@ -36,6 +35,8 @@ import {
   type ToolResult,
 } from './AiAgent.js';
 
+type UrlString = Platform.DevToolsPath.UrlString;
+
 const UIStringsNotTranslated = {
   /**
    * @description Shown when the agent is investigating network activity

package/front_end/models/ai_assistance/contexts/PerformanceTraceContext.ts

@@ -3,7 +3,6 @@
 // found in the LICENSE file.
 
 import * as Common from '../../../core/common/common.js';
-import type {UrlString} from '../../../core/platform/DevToolsPath.js';
 import type * as Platform from '../../../core/platform/platform.js';
 import * as SDK from '../../../core/sdk/sdk.js';
 import * as Tracing from '../../../services/tracing/tracing.js';
@@ -24,6 +23,8 @@ import {PerformanceTraceFormatter} from '../data_formatters/PerformanceTraceForm
 import type {AICallTree} from '../performance/AICallTree.js';
 import {AgentFocus} from '../performance/AIContext.js';
 
+type UrlString = Platform.DevToolsPath.UrlString;
+
 /**
  * Labels used to identify specific periods or categories in the trace for getting main thread summary.
  * Supports hardcoded phases, dynamic navigation IDs (`NAVIGATION_X`), and insight models.

package/front_end/models/ai_assistance/data_formatters/PerformanceInsightFormatter.snapshot.txt

@@ -226,7 +226,7 @@ Response headers
 
 The result of the checks for this insight are:
 - fetchpriority=high should be applied: FAILED
-- LCP resources should not use loading=lazy: PASSED
+- LCP resources shouldn’t use loading=lazy: PASSED
 - Request is discoverable in initial document: PASSED
 
 ## Estimated savings: none
@@ -1052,7 +1052,7 @@ The network dependency tree checks revealed no problems, but optimization sugges
 
 No rendering tasks impacted by network dependencies.
 
-no origins were preconnected.
+No origins were preconnected.
 
 ## Estimated savings: none
 
@@ -1085,7 +1085,7 @@ The following is the critical request chain:
   - http://localhost:8787/lcp-iframes/app.js (eventKey: s-7225, ts: 566782574106) (5,015 ms) (longest chain)
   - http://localhost:8787/lcp-iframes/app.css (eventKey: s-7213, ts: 566782573909) (5,010 ms)
 
-no origins were preconnected.
+No origins were preconnected.
 
 ## Estimated savings: none
 
@@ -1097,13 +1097,13 @@ no origins were preconnected.
 
 Title: PerformanceInsightFormatter SlowCssSelector serializes correctly when there are no results
 Content:
-## Insight Title: CSS Selector costs
+## Insight Title: CSS selector costs
 
 ## Insight Summary:
 This insight identifies CSS selectors that are slowing down your page's rendering performance.
 
 ## Detailed analysis:
-No CSS selector data was found. CSS selector stats need to be enabled in the performance panel settings.
+No CSS selector data was found. CSS selector stats need to be enabled in the Performance panel settings.
 
 ## Estimated savings: none
 
@@ -1114,7 +1114,7 @@ No CSS selector data was found. CSS selector stats need to be enabled in the per
 
 Title: PerformanceInsightFormatter SlowCssSelector serializes the correct details when CSS selectors are found
 Content:
-## Insight Title: CSS Selector costs
+## Insight Title: CSS selector costs
 
 ## Insight Summary:
 This insight identifies CSS selectors that are slowing down your page's rendering performance.
@@ -1130,7 +1130,7 @@ Elapsed time: 0 ms
 Match attempts: 2444
 Match count: 465
 
-If Recalculate Style costs remain high, selector optimization can reduce them. [Optimize the selectors](https://developer.chrome.com/docs/performance/insights/slow-css-selector) with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs.
+If recalculate style costs remain high, selector optimization can reduce them. [Optimize the selectors](https://developer.chrome.com/docs/performance/insights/slow-css-selector) with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs.
 
 ## Estimated savings: none
 
@@ -1258,7 +1258,7 @@ The webpage is not optimized for mobile viewing.
 
 The viewport meta tag is missing.
 
-Tap interactions may be [delayed by up to 300 ms](https://developer.chrome.com/docs/performance/insights/viewport) if the viewport is not optimized for mobile.
+Tap interactions may be [delayed by up to 300 ms](https://developer.chrome.com/docs/performance/insights/viewport) if the viewport isn’t optimized for mobile.
 
 ## Estimated savings: none
 

package/front_end/models/ai_assistance/data_formatters/PerformanceTraceFormatter.snapshot.txt

@@ -530,7 +530,7 @@ Available insights:
     relevant trace bounds: {min: 157423489126µs, max: 157426527569µs}
     example question: How do I optimize my network dependency tree?
   - insight name: ImageDelivery
-    description: Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)
+    description: Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery).
     relevant trace bounds: {min: 157423794709µs, max: 157424082831µs}
     estimated metric savings: FCP 0 ms, LCP 0 ms
     estimated wasted bytes: 97.8 kB
@@ -552,7 +552,7 @@ Available insights:
     estimated wasted bytes: 847.4 kB
     example question: What caching strategies can I apply to improve my page performance?
   - insight name: LegacyJavaScript
-    description: Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren’t necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)
+    description: Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren’t necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript).
     relevant trace bounds: {min: 157423489126µs, max: 157426132225µs}
     estimated metric savings: FCP 0 ms, LCP 0 ms
     estimated wasted bytes: 126.9 kB
@@ -660,7 +660,7 @@ Available insights:
     estimated wasted bytes: 971.5 kB
     example question: What caching strategies can I apply to improve my page performance?
   - insight name: ImageDelivery
-    description: Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)
+    description: Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery).
     relevant trace bounds: {min: 59728701403µs, max: 59729395208µs}
     estimated metric savings: FCP 0 ms, LCP 100 ms
     estimated wasted bytes: 2 MB
@@ -673,7 +673,7 @@ Available insights:
     example question: Which LCP subpart was most problematic?
     example question: What can I do to reduce the LCP time for this page load?
   - insight name: LCPDiscovery
-    description: [Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
+    description: [Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading.
     relevant trace bounds: {min: 59728656735µs, max: 59729209036µs}
     example question: Suggest fixes to reduce my LCP
     example question: What can I do to reduce my LCP discovery time?
@@ -691,7 +691,7 @@ Available insights:
     example question: How do I decrease the initial loading time of my page?
     example question: Did anything slow down the request for this document?
   - insight name: Viewport
-    description: Tap interactions may be [delayed by up to 300 ms](https://developer.chrome.com/docs/performance/insights/viewport) if the viewport is not optimized for mobile.
+    description: Tap interactions may be [delayed by up to 300 ms](https://developer.chrome.com/docs/performance/insights/viewport) if the viewport isn’t optimized for mobile.
     relevant trace bounds: {min: 59728649746µs, max: 59734400108µs}
     estimated metric savings: INP 0 ms
     example question: How do I make sure my page is optimized for mobile viewing?
@@ -744,7 +744,7 @@ Available insights:
     estimated wasted bytes: 971.5 kB
     example question: What caching strategies can I apply to improve my page performance?
   - insight name: ImageDelivery
-    description: Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)
+    description: Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery).
     relevant trace bounds: {min: 59728701403µs, max: 59729395208µs}
     estimated metric savings: FCP 0 ms, LCP 100 ms
     estimated wasted bytes: 2 MB
@@ -757,7 +757,7 @@ Available insights:
     example question: Which LCP subpart was most problematic?
     example question: What can I do to reduce the LCP time for this page load?
   - insight name: LCPDiscovery
-    description: [Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
+    description: [Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading.
     relevant trace bounds: {min: 59728656735µs, max: 59729209036µs}
     example question: Suggest fixes to reduce my LCP
     example question: What can I do to reduce my LCP discovery time?
@@ -775,7 +775,7 @@ Available insights:
     example question: How do I decrease the initial loading time of my page?
     example question: Did anything slow down the request for this document?
   - insight name: Viewport
-    description: Tap interactions may be [delayed by up to 300 ms](https://developer.chrome.com/docs/performance/insights/viewport) if the viewport is not optimized for mobile.
+    description: Tap interactions may be [delayed by up to 300 ms](https://developer.chrome.com/docs/performance/insights/viewport) if the viewport isn’t optimized for mobile.
     relevant trace bounds: {min: 59728649746µs, max: 59734400108µs}
     estimated metric savings: INP 0 ms
     example question: How do I make sure my page is optimized for mobile viewing?

package/front_end/models/bindings/DebuggerLanguagePlugins.ts

@@ -11,6 +11,7 @@ import * as SDK from '../../core/sdk/sdk.js';
 import * as TextUtils from '../../core/text_utils/text_utils.js';
 import * as Protocol from '../../generated/protocol.js';
 import * as StackTrace from '../stack_trace/stack_trace.js';
+// eslint-disable-next-line @devtools/es-modules-import
 import type * as StackTraceImpl from '../stack_trace/stack_trace_impl.js';
 import * as Workspace from '../workspace/workspace.js';
 

package/front_end/models/formatter/ScriptFormatter.ts

@@ -4,6 +4,7 @@
 
 import type * as Common from '../../core/common/common.js';
 import * as Platform from '../../core/platform/platform.js';
+// eslint-disable-next-line @devtools/es-modules-import
 import type * as FormatterActions from '../../entrypoints/formatter_worker/FormatterActions.js';
 
 import {formatterWorkerPool} from './FormatterWorkerPool.js';

package/front_end/models/javascript_metadata/NativeFunctions.js

@@ -6718,6 +6718,10 @@ export const NativeFunctions = [
     name: "copyElementImageToTexture",
     signatures: [["source","destination"]]
   },
+  {
+    name: "drawElementImageToTexture",
+    signatures: [["source","destination"]]
+  },
   {
     name: "multiDrawIndirect",
     signatures: [["indirectBuffer","indirectOffset","maxDrawCount","?drawCountBuffer","?drawCountBufferOffset"]]
@@ -6806,6 +6810,10 @@ export const NativeFunctions = [
     name: "texElementImage2D",
     signatures: [["target","internalformat","element","?config"]]
   },
+  {
+    name: "texElementSubImage2D",
+    signatures: [["target","level","xoffset","yoffset","element","?config"]]
+  },
   {
     name: "drawingBufferStorage",
     signatures: [["sizedformat","width","height"]]
@@ -8148,7 +8156,7 @@ export const NativeFunctions = [
   },
   {
     name: "drawElementImage",
-    signatures: [["element","dx","dy","?dwidth","?dheight"],["element","sx","sy","swidth","sheight","dx","dy","?dwidth","?dheight"]]
+    signatures: [["element","dx","dy","?options"],["element","dx","dy","dwidth","dheight","?options"],["element","sx","sy","swidth","sheight","dx","dy","?options"],["element","sx","sy","swidth","sheight","dx","dy","dwidth","dheight","?options"]]
   },
   {
     name: "CanvasFilter",

package/front_end/models/live-metrics/web-vitals-injected/spec/spec.ts

@@ -2,7 +2,7 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-import type {INPAttribution, Metric} from '../../../../third_party/web-vitals/web-vitals.js';
+import type * as WebVitals from '../../../../third_party/web-vitals/web-vitals.js';
 import type * as Trace from '../../../trace/trace.js';
 
 export const EVENT_BINDING_NAME = '__chromium_devtools_metrics_reporter';
@@ -48,7 +48,7 @@ export interface ClsChangeEvent {
 export interface InpChangeEvent {
   name: 'INP';
   value: Trace.Types.Timing.Milli;
-  interactionType: INPAttribution['interactionType'];
+  interactionType: WebVitals.INPAttribution['interactionType'];
   subparts: InpSubparts;
   startTime: number;
   entryGroupId: InteractionEntryGroupId;
@@ -95,7 +95,7 @@ export interface PerformanceLongAnimationFrameTimingJSON {
  */
 export interface InteractionEntryEvent {
   name: 'InteractionEntry';
-  interactionType?: INPAttribution['interactionType'];
+  interactionType?: WebVitals.INPAttribution['interactionType'];
   eventName: string;
   entryGroupId: InteractionEntryGroupId;
   startTime: number;
@@ -107,7 +107,7 @@ export interface InteractionEntryEvent {
   longAnimationFrameEntries: PerformanceLongAnimationFrameTimingJSON[];
 }
 
-export type NavigationType = Metric['navigationType'];
+export type NavigationType = WebVitals.Metric['navigationType'];
 
 export interface LayoutShiftEvent {
   name: 'LayoutShift';

package/front_end/models/logs/NetworkLog.ts

@@ -19,6 +19,13 @@ const UIStrings = {
 const str_ = i18n.i18n.registerUIStrings('models/logs/NetworkLog.ts', UIStrings);
 const i18nString = i18n.i18n.getLocalizedString.bind(undefined, str_);
 
+export const recordNetworkLogSettingDescriptor: Common.Settings.SettingDescriptor<boolean> = {
+  name: 'network-log.record-log',
+  type: Common.Settings.SettingType.BOOLEAN,
+  defaultValue: true,
+  storageType: Common.Settings.SettingStorageType.SESSION,
+};
+
 export class NetworkLog extends Common.ObjectWrapper.ObjectWrapper<EventTypes> implements
     SDK.TargetManager.SDKModelObserver<SDK.NetworkManager.NetworkManager> {
   #requests: SDK.NetworkRequest.NetworkRequest[] = [];
@@ -43,7 +50,7 @@ export class NetworkLog extends Common.ObjectWrapper.ObjectWrapper<EventTypes> i
     this.#settings = settings;
 
     this.#targetManager.observeModels(SDK.NetworkManager.NetworkManager, this);
-    const recordLogSetting: Common.Settings.Setting<boolean> = this.#settings.moduleSetting('network-log.record-log');
+    const recordLogSetting = this.#settings.resolve(recordNetworkLogSettingDescriptor);
     recordLogSetting.addChangeListener(() => {
       const preserveLogSetting = this.#settings.resolve(SDK.SDKSettings.preserveNetworkLogSettingDescriptor);
       if (!preserveLogSetting.get() && recordLogSetting.get()) {

package/front_end/models/persistence/AutomaticFileSystemWorkspaceBinding.ts

@@ -6,8 +6,7 @@ import * as Common from '../../core/common/common.js';
 import * as Host from '../../core/host/host.js';
 import type * as Platform from '../../core/platform/platform.js';
 import * as Root from '../../core/root/root.js';
-import type {ContentDataOrError} from '../../core/text_utils/ContentData.js';
-import type {SearchMatch} from '../../core/text_utils/ContentProvider.js';
+import type * as TextUtils from '../../core/text_utils/text_utils.js';
 import * as Workspace from '../workspace/workspace.js';
 
 import {
@@ -20,6 +19,9 @@ import {
   type IsolatedFileSystemManager,
 } from './IsolatedFileSystemManager.js';
 
+type ContentDataOrError = TextUtils.ContentData.ContentDataOrError;
+type SearchMatch = TextUtils.ContentProvider.SearchMatch;
+
 /**
  * Placeholder project that acts as an empty file system within the workspace,
  * and automatically disappears when the user connects the automatic workspace

package/front_end/models/stack_trace/StackTraceImpl.ts

@@ -6,6 +6,7 @@ import * as Common from '../../core/common/common.js';
 import type * as SDK from '../../core/sdk/sdk.js';
 import type * as Workspace from '../workspace/workspace.js';
 
+// eslint-disable-next-line @devtools/es-modules-import
 import type * as StackTrace from './stack_trace.js';
 import type {EvalOrigin, FrameNode, ParsedFrameInfo} from './Trie.js';
 

package/front_end/models/trace/Name.ts

@@ -16,7 +16,7 @@ const UIStrings = {
    */
   anonymous: '(anonymous)',
   /**
-   * @description Text used to show an EventDispatch event which has a type associated with it
+   * @description Text used to show an EventDispatch event which has a type associated with it.
    * @example {click} PH1
    */
   eventDispatchS: 'Event: {PH1}',
@@ -25,20 +25,20 @@ const UIStrings = {
    */
   frame: 'Frame',
   /**
-   * @description Text in Timeline Flame Chart Data Provider of the Performance panel
+   * @description Text in the flame chart of the Performance panel.
    */
   wsConnectionOpened: 'WebSocket opened',
   /**
-   * @description Text in Timeline Flame Chart Data Provider of the Performance panel
+   * @description Text in the flame chart of the Performance panel.
    * @example {ws://example.com} PH1
    */
   wsConnectionOpenedWithUrl: 'WebSocket opened: {PH1}',
   /**
-   * @description Text in Timeline Flame Chart Data Provider of the Performance panel
+   * @description Text in the flame chart of the Performance panel.
    */
   wsConnectionClosed: 'WebSocket closed',
   /**
-   * @description Text in Timeline Flame Chart Data Provider of the Performance panel
+   * @description Text in the flame chart of the Performance panel.
    */
   layoutShift: 'Layout shift',
 } as const;

package/front_end/models/trace/Processor.ts

@@ -606,6 +606,7 @@ export class TraceProcessor extends EventTarget {
         'missing metric scores for main frame',
         'missing metric: FCP',
         'missing metric: LCP',
+        'NO_LCP',
         'No network requests found in trace',
         'Trace is too old',
       ];