chrome-devtools-frontend 1.0.1681498 → 1.0.1682249

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

@@ -6806,6 +6806,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 +8152,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;