chrome-devtools-frontend 1.0.1525561 → 1.0.1526203

package/front_end/models/ai_assistance/data_formatters/PerformanceInsightFormatter.ts

@@ -1009,55 +1009,73 @@ ${this.#links()}`;
   }
 
   #links(): string {
+    const links = [];
+
+    if (this.#insight.docs) {
+      links.push(this.#insight.docs);
+    }
+
     switch (this.#insight.insightKey) {
       case 'CLSCulprits':
-        return `- https://web.dev/articles/cls
-- https://web.dev/articles/optimize-cls`;
+        links.push('https://web.dev/articles/cls');
+        links.push('https://web.dev/articles/optimize-cls');
+        break;
       case 'DocumentLatency':
-        return '- https://web.dev/articles/optimize-ttfb';
+        links.push('https://web.dev/articles/optimize-ttfb');
+        break;
       case 'DOMSize':
-        return '- https://developer.chrome.com/docs/lighthouse/performance/dom-size/';
-      case 'DuplicatedJavaScript':
-        return '';
+        links.push('https://developer.chrome.com/docs/lighthouse/performance/dom-size/');
+        break;
       case 'FontDisplay':
-        return `- https://web.dev/articles/preload-optional-fonts
-- https://fonts.google.com/knowledge/glossary/foit
-- https://developer.chrome.com/blog/font-fallbacks`;
+        links.push('https://web.dev/articles/preload-optional-fonts');
+        links.push('https://fonts.google.com/knowledge/glossary/foit');
+        links.push('https://developer.chrome.com/blog/font-fallbacks');
+        break;
       case 'ForcedReflow':
-        return '- https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid-forced-synchronous-layouts';
+        links.push(
+            'https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid-forced-synchronous-layouts');
+        break;
       case 'ImageDelivery':
-        return '- https://developer.chrome.com/docs/lighthouse/performance/uses-optimized-images/';
+        links.push('https://developer.chrome.com/docs/lighthouse/performance/uses-optimized-images/');
+        break;
       case 'INPBreakdown':
-        return `- https://web.dev/articles/inp
-- https://web.dev/explore/how-to-optimize-inp
-- https://web.dev/articles/optimize-long-tasks
-- https://web.dev/articles/avoid-large-complex-layouts-and-layout-thrashing`;
-      case 'LCPDiscovery':
-        return `- https://web.dev/articles/lcp
-- https://web.dev/articles/optimize-lcp`;
+        links.push('https://web.dev/articles/inp');
+        links.push('https://web.dev/explore/how-to-optimize-inp');
+        links.push('https://web.dev/articles/optimize-long-tasks');
+        links.push('https://web.dev/articles/avoid-large-complex-layouts-and-layout-thrashing');
+        break;
       case 'LCPBreakdown':
-        return `- https://web.dev/articles/lcp
-- https://web.dev/articles/optimize-lcp`;
-      case 'NetworkDependencyTree':
-        return `- https://web.dev/learn/performance/understanding-the-critical-path
-- https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/`;
+      case 'LCPDiscovery':
       case 'RenderBlocking':
-        return `- https://web.dev/articles/lcp
-- https://web.dev/articles/optimize-lcp`;
+        links.push('https://web.dev/articles/lcp');
+        links.push('https://web.dev/articles/optimize-lcp');
+        break;
+      case 'NetworkDependencyTree':
+        links.push('https://web.dev/learn/performance/understanding-the-critical-path');
+        links.push('https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/');
+        break;
       case 'SlowCSSSelector':
-        return '- https://developer.chrome.com/docs/devtools/performance/selector-stats';
+        links.push('https://developer.chrome.com/docs/devtools/performance/selector-stats');
+        break;
       case 'ThirdParties':
-        return '- https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/';
+        links.push('https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/');
+        break;
       case 'Viewport':
-        return '- https://developer.chrome.com/blog/300ms-tap-delay-gone-away/';
+        links.push('https://developer.chrome.com/blog/300ms-tap-delay-gone-away/');
+        break;
       case 'Cache':
-        return '- https://web.dev/uses-long-cache-ttl/';
+        links.push('https://web.dev/uses-long-cache-ttl/');
+        break;
       case 'ModernHTTP':
-        return '- https://developer.chrome.com/docs/lighthouse/best-practices/uses-http2';
+        links.push('https://developer.chrome.com/docs/lighthouse/best-practices/uses-http2');
+        break;
       case 'LegacyJavaScript':
-        return `- https://web.dev/articles/baseline-and-polyfills
-- https://philipwalton.com/articles/the-state-of-es5-on-the-web/`;
+        links.push('https://web.dev/articles/baseline-and-polyfills');
+        links.push('https://philipwalton.com/articles/the-state-of-es5-on-the-web/');
+        break;
     }
+
+    return links.map(link => '- ' + link).join('\n');
   }
 
   #description(): string {

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

@@ -516,20 +516,20 @@ Metrics (lab / observed):
 Metrics (field / real users): n/a – no data for this page in CrUX
 Available insights:
   - insight name: LCPBreakdown
-    description: Each [subpart has specific improvement strategies](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.
+    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.
     relevant trace bounds: {min: 1020034834921, max: 1020034953358}
     example question: Help me optimize my LCP score
     example question: Which LCP phase was most problematic?
     example question: What can I do to reduce the LCP time for this page load?
   - insight name: DocumentLatency
-    description: Your first network request is the most important.  Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
+    description: Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression.
     relevant trace bounds: {min: 1020034836013, max: 1020034892491}
     estimated metric savings: FCP 0 ms, LCP 0 ms
     estimated wasted bytes: 52.1 kB
     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: ThirdParties
-    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/) to prioritize your page's content.
+    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://developer.chrome.com/docs/performance/insights/third-parties) to prioritize your page's content.
     relevant trace bounds: {min: 1020034871372, max: 1020035171789}
     example question: Which third parties are having the largest impact on my page performance?
 === end content
@@ -551,44 +551,44 @@ Metrics (lab / observed):
 Metrics (field / real users): n/a – no data for this page in CrUX
 Available insights:
   - insight name: LCPBreakdown
-    description: Each [subpart has specific improvement strategies](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.
+    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.
     relevant trace bounds: {min: 157423488682, max: 157423953162}
     example question: Help me optimize my LCP score
     example question: Which LCP phase was most problematic?
     example question: What can I do to reduce the LCP time for this page load?
   - insight name: CLSCulprits
-    description: Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://web.dev/articles/optimize-cls), such as elements being added, removed, or their fonts changing as the page loads.
+    description: Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads.
     relevant trace bounds: {min: 157425604232, max: 157426760958}
     example question: Help me optimize my CLS score
     example question: How can I prevent layout shifts on this page?
   - insight name: NetworkDependencyTree
-    description: [Avoid chaining critical requests](https://developer.chrome.com/docs/lighthouse/performance/critical-request-chains) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
+    description: [Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
     relevant trace bounds: {min: 157423489126, max: 157426527569}
     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/lighthouse/performance/uses-optimized-images/)
+    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, max: 157424082831}
     estimated metric savings: FCP 0 ms, LCP 0 ms
     estimated wasted bytes: 97.8 kB
     example question: What should I do to improve and optimize the time taken to fetch and display images on the page?
     example question: Are all images on my site optimized?
   - insight name: FontDisplay
-    description: Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
+    description: Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
     relevant trace bounds: {min: 157425661196, max: 157425696387}
     estimated metric savings: FCP 20 ms
     example question: How can I update my CSS to avoid layout shifts caused by incorrect `font-display` properties?
   - insight name: ThirdParties
-    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/) to prioritize your page's content.
+    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://developer.chrome.com/docs/performance/insights/third-parties) to prioritize your page's content.
     relevant trace bounds: {min: 157423742399, max: 157427277086}
     example question: Which third parties are having the largest impact on my page performance?
   - insight name: Cache
-    description: A long cache lifetime can speed up repeat visits to your page. [Learn more](https://web.dev/uses-long-cache-ttl/).
+    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).
     relevant trace bounds: {min: 157423742399, max: 157426980482}
     estimated metric savings: FCP 0 ms, LCP 0 ms
     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://philipwalton.com/articles/the-state-of-es5-on-the-web/)
+    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, max: 157426132225}
     estimated metric savings: FCP 0 ms, LCP 0 ms
     estimated wasted bytes: 126.9 kB
@@ -613,49 +613,49 @@ Metrics (lab / observed):
 Metrics (field / real users): n/a – no data for this page in CrUX
 Available insights:
   - insight name: Cache
-    description: A long cache lifetime can speed up repeat visits to your page. [Learn more](https://web.dev/uses-long-cache-ttl/).
+    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).
     relevant trace bounds: {min: 59728702014, max: 59728867430}
     estimated metric savings: FCP 0 ms, LCP 150 ms
     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/lighthouse/performance/uses-optimized-images/)
+    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, max: 59729395208}
     estimated metric savings: FCP 0 ms, LCP 100 ms
     estimated wasted bytes: 2 MB
     example question: What should I do to improve and optimize the time taken to fetch and display images on the page?
     example question: Are all images on my site optimized?
   - insight name: LCPBreakdown
-    description: Each [subpart has specific improvement strategies](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.
+    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.
     relevant trace bounds: {min: 59728649746, max: 59729312744}
     example question: Help me optimize my LCP score
     example question: Which LCP phase was most problematic?
     example question: What can I do to reduce the LCP time for this page load?
   - insight name: LCPDiscovery
-    description: Optimize LCP by making the LCP image [discoverable](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) from the HTML immediately, and [avoiding lazy-loading](https://web.dev/articles/lcp-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, max: 59729209036}
     example question: Suggest fixes to reduce my LCP
     example question: What can I do to reduce my LCP discovery time?
     example question: Why is LCP discovery time important?
   - insight name: CLSCulprits
-    description: Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://web.dev/articles/optimize-cls), such as elements being added, removed, or their fonts changing as the page loads.
+    description: Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads.
     relevant trace bounds: {min: 59729100192, max: 59730317334}
     example question: Help me optimize my CLS score
     example question: How can I prevent layout shifts on this page?
   - insight name: DocumentLatency
-    description: Your first network request is the most important.  Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
+    description: Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression.
     relevant trace bounds: {min: 59728651057, max: 59728790724}
     estimated metric savings: FCP 0 ms, LCP 0 ms
     estimated wasted bytes: 1.6 kB
     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/blog/300ms-tap-delay-gone-away/) 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 is not optimized for mobile.
     relevant trace bounds: {min: 59728649746, max: 59734400108}
     estimated metric savings: INP 0 ms
     example question: How do I make sure my page is optimized for mobile viewing?
   - insight name: ThirdParties
-    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/) to prioritize your page's content.
+    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://developer.chrome.com/docs/performance/insights/third-parties) to prioritize your page's content.
     relevant trace bounds: {min: 59728701403, max: 59729465969}
     example question: Which third parties are having the largest impact on my page performance?
 === end content
@@ -684,49 +684,49 @@ Metrics (field / real users):
   - Lab metrics describe how this specific page load performed, while field metrics are an aggregation of results from real-world users. Best practice is to prioritize metrics that are bad in field data. Lab metrics may be better or worse than fields metrics depending on the developer's machine, network, or the actions performed while tracing.
 Available insights:
   - insight name: Cache
-    description: A long cache lifetime can speed up repeat visits to your page. [Learn more](https://web.dev/uses-long-cache-ttl/).
+    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).
     relevant trace bounds: {min: 59728702014, max: 59728867430}
     estimated metric savings: FCP 0 ms, LCP 150 ms
     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/lighthouse/performance/uses-optimized-images/)
+    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, max: 59729395208}
     estimated metric savings: FCP 0 ms, LCP 100 ms
     estimated wasted bytes: 2 MB
     example question: What should I do to improve and optimize the time taken to fetch and display images on the page?
     example question: Are all images on my site optimized?
   - insight name: LCPBreakdown
-    description: Each [subpart has specific improvement strategies](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.
+    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.
     relevant trace bounds: {min: 59728649746, max: 59729312744}
     example question: Help me optimize my LCP score
     example question: Which LCP phase was most problematic?
     example question: What can I do to reduce the LCP time for this page load?
   - insight name: LCPDiscovery
-    description: Optimize LCP by making the LCP image [discoverable](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) from the HTML immediately, and [avoiding lazy-loading](https://web.dev/articles/lcp-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, max: 59729209036}
     example question: Suggest fixes to reduce my LCP
     example question: What can I do to reduce my LCP discovery time?
     example question: Why is LCP discovery time important?
   - insight name: CLSCulprits
-    description: Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://web.dev/articles/optimize-cls), such as elements being added, removed, or their fonts changing as the page loads.
+    description: Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads.
     relevant trace bounds: {min: 59729100192, max: 59730317334}
     example question: Help me optimize my CLS score
     example question: How can I prevent layout shifts on this page?
   - insight name: DocumentLatency
-    description: Your first network request is the most important.  Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
+    description: Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression.
     relevant trace bounds: {min: 59728651057, max: 59728790724}
     estimated metric savings: FCP 0 ms, LCP 0 ms
     estimated wasted bytes: 1.6 kB
     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/blog/300ms-tap-delay-gone-away/) 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 is not optimized for mobile.
     relevant trace bounds: {min: 59728649746, max: 59734400108}
     estimated metric savings: INP 0 ms
     example question: How do I make sure my page is optimized for mobile viewing?
   - insight name: ThirdParties
-    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/) to prioritize your page's content.
+    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://developer.chrome.com/docs/performance/insights/third-parties) to prioritize your page's content.
     relevant trace bounds: {min: 59728701403, max: 59729465969}
     example question: Which third parties are having the largest impact on my page performance?
 === end content
@@ -743,13 +743,13 @@ Metrics (lab / observed):
 Metrics (field / real users): n/a – no data for this page in CrUX
 Available insights:
   - insight name: INPBreakdown
-    description: Start investigating with the longest subpart. [Delays can be minimized](https://web.dev/articles/optimize-inp#optimize_interactions). To reduce processing duration, [optimize the main-thread costs](https://web.dev/articles/optimize-long-tasks), often JS.
+    description: Start investigating [how to improve INP](https://developer.chrome.com/docs/performance/insights/inp-breakdown) by looking at the longest subpart.
     relevant trace bounds: {min: 337944870984, max: 337945010222}
     example question: Suggest fixes for my longest interaction
     example question: Why is a large INP score problematic?
     example question: What's the biggest contributor to my longest interaction?
   - insight name: ThirdParties
-    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/) to prioritize your page's content.
+    description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://developer.chrome.com/docs/performance/insights/third-parties) to prioritize your page's content.
     relevant trace bounds: {min: 337944792445, max: 337944809570}
     example question: Which third parties are having the largest impact on my page performance?
 === end content

package/front_end/models/javascript_metadata/NativeFunctions.js

@@ -986,7 +986,7 @@ export const NativeFunctions = [
   {
     name: "from",
     signatures: [["value"]],
-    receivers: ["Observable"]
+    receivers: ["Observable","Origin"]
   },
   {
     name: "drawArraysInstancedANGLE",
@@ -5356,19 +5356,14 @@ export const NativeFunctions = [
   },
   {
     name: "createImageBitmap",
-    signatures: [["image","?options"],["image","sx","sy","sw","sh","?options"]],
+    signatures: [["image","?options"],["imageBitmap","?options"],["image","sx","sy","sw","sh","?options"],["imageBitmap","sx","sy","sw","sh","?options"]],
     receivers: ["Window","WorkerGlobalScope"]
   },
   {
     name: "createImageBitmap",
-    signatures: [["image","?options"],["imageBitmap","?options"],["image","sx","sy","sw","sh","?options"],["imageBitmap","sx","sy","sw","sh","?options"]],
+    signatures: [["image","?options"],["image","sx","sy","sw","sh","?options"]],
     receivers: ["Window"]
   },
-  {
-    name: "createImageBitmap",
-    signatures: [["imageBitmap","?options"],["imageBitmap","sx","sy","sw","sh","?options"]],
-    receivers: ["WorkerGlobalScope"]
-  },
   {
     name: "fetch",
     signatures: [["input","?init"]],

package/front_end/models/trace/handlers/UserTimingsHandler.ts

@@ -151,7 +151,7 @@ function getEventTrack(event: Types.Events.SyntheticEventPair|Types.Events.Conso
 }
 
 /**
- * Similar to the default {@see Helpers.Trace.eventTimeComparator}
+ * Similar to the default {@link Helpers.Trace.eventTimeComparator}
  * but with a twist:
  * In case of equal start and end times, put the second event (within a
  * track) first.

package/front_end/models/trace/insights/CLSCulprits.ts

@@ -25,7 +25,7 @@ export const UIStrings = {
    * This is displayed after a user expands the section to see more. No character length limits.
    */
   description:
-      'Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://web.dev/articles/optimize-cls), such as elements being added, removed, or their fonts changing as the page loads.',
+      'Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads.',
   /**
    * @description Text indicating the worst layout shift cluster.
    */
@@ -583,6 +583,7 @@ function finalize(partialModel: PartialInsightModel<CLSCulpritsInsightModel>): C
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/cls-culprit',
     category: InsightCategory.CLS,
     state,
     ...partialModel,

package/front_end/models/trace/insights/Cache.ts

@@ -27,7 +27,7 @@ export const UIStrings = {
    * @description Text to tell the user about how caching can help improve performance.
    */
   description:
-      'A long cache lifetime can speed up repeat visits to your page. [Learn more](https://web.dev/uses-long-cache-ttl/).',
+      'A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).',
   /**
    * @description Column for a font loaded by the page to render text.
    */
@@ -67,6 +67,7 @@ function finalize(partialModel: PartialInsightModel<CacheInsightModel>): CacheIn
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/cache',
     category: InsightCategory.ALL,
     state: partialModel.requests.length > 0 ? 'fail' : 'pass',
     ...partialModel,

package/front_end/models/trace/insights/DOMSize.ts

@@ -25,7 +25,7 @@ export const UIStrings = {
    * @description Description of an insight that recommends reducing the size of the DOM tree as a means to improve page responsiveness. "DOM" is an acronym and should not be translated. "layout reflows" are when the browser will recompute the layout of content on the page.
    */
   description:
-      'A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. [Learn how to avoid an excessive DOM size](https://developer.chrome.com/docs/lighthouse/performance/dom-size/).',
+      'A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. [Learn how to avoid an excessive DOM size](https://developer.chrome.com/docs/performance/insights/dom-size).',
   /**
    * @description Header for a column containing the names of statistics as opposed to the actual statistic values.
    */
@@ -97,6 +97,7 @@ function finalize(partialModel: PartialInsightModel<DOMSizeInsightModel>): DOMSi
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/dom-size',
     category: InsightCategory.INP,
     state: relatedEvents.length > 0 ? 'informative' : 'pass',
     ...partialModel,

package/front_end/models/trace/insights/DocumentLatency.ts

@@ -27,7 +27,7 @@ export const UIStrings = {
    * @description Description of an insight that provides a breakdown for how long it took to download the main document.
    */
   description:
-      'Your first network request is the most important.  Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.',
+      'Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression.',
   /**
    * @description Text to tell the user that the document request does not have redirects.
    */
@@ -182,6 +182,7 @@ function finalize(partialModel: PartialInsightModel<DocumentLatencyInsightModel>
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/document-latency',
     category: InsightCategory.ALL,
     state: hasFailure ? 'fail' : 'pass',
     ...partialModel,

package/front_end/models/trace/insights/DuplicatedJavaScript.ts

@@ -26,7 +26,7 @@ export const UIStrings = {
    * @description Description of an insight that identifies multiple copies of the same JavaScript sources, and recommends removing the duplication.
    */
   description:
-      'Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.',
+      'Remove large, [duplicate JavaScript modules](https://developer.chrome.com/docs/performance/insights/duplicated-javascript) from bundles to reduce unnecessary bytes consumed by network activity.',
   /** Label for a column in a data table; entries will be the locations of JavaScript or CSS code, e.g. the name of a Javascript package or module. */
   columnSource: 'Source',
   /** Label for a column in a data table; entries will be the number of wasted bytes due to duplication of a web resource. */
@@ -53,6 +53,7 @@ function finalize(partialModel: PartialInsightModel<DuplicatedJavaScriptInsightM
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/duplicated-javascript',
     category: InsightCategory.LCP,
     state: Boolean(partialModel.duplication.values().next().value) ? 'fail' : 'pass',
     relatedEvents: [...new Set(requests)],

package/front_end/models/trace/insights/FontDisplay.ts

@@ -23,7 +23,7 @@ export const UIStrings = {
    * @description Text to tell the user about the font-display CSS feature to help improve a the UX of a page.
    */
   description:
-      'Consider setting [`font-display`](https://developer.chrome.com/blog/font-display) to `swap` or `optional` to ensure text is consistently visible. `swap` can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).',
+      'Consider setting [`font-display`](https://developer.chrome.com/docs/performance/insights/font-display) to `swap` or `optional` to ensure text is consistently visible. `swap` can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).',
   /** Column for a font loaded by the page to render text. */
   fontColumn: 'Font',
   /** Column for the amount of time wasted. */
@@ -50,6 +50,7 @@ function finalize(partialModel: PartialInsightModel<FontDisplayInsightModel>): F
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/font-display',
     category: InsightCategory.INP,
     state: partialModel.fonts.find(font => font.wastedTime > 0) ? 'fail' : 'pass',
     ...partialModel,

package/front_end/models/trace/insights/ForcedReflow.ts

@@ -27,7 +27,7 @@ export const UIStrings = {
    * @description Text to describe the forced reflow.
    */
   description:
-      'A forced reflow occurs when JavaScript queries geometric properties (such as `offsetWidth`) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid-forced-synchronous-layouts) and possible mitigations.',
+      'A forced reflow occurs when JavaScript queries geometric properties (such as `offsetWidth`) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.',
   /**
    * @description Title of a list to provide related stack trace data
    */
@@ -144,6 +144,7 @@ function finalize(partialModel: PartialInsightModel<ForcedReflowInsightModel>):
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/forced-reflow',
     category: InsightCategory.ALL,
     state: partialModel.aggregatedBottomUpData.length !== 0 ? 'fail' : 'pass',
     ...partialModel,

package/front_end/models/trace/insights/INPBreakdown.ts

@@ -21,7 +21,7 @@ export const UIStrings = {
    * @description Text to tell the user about the longest user interaction.
    */
   description:
-      'Start investigating with the longest subpart. [Delays can be minimized](https://web.dev/articles/optimize-inp#optimize_interactions). To reduce processing duration, [optimize the main-thread costs](https://web.dev/articles/optimize-long-tasks), often JS.',
+      'Start investigating [how to improve INP](https://developer.chrome.com/docs/performance/insights/inp-breakdown) by looking at the longest subpart.',
   /**
    * @description Title for the performance insight "INP breakdown", which shows a breakdown of INP by subparts / sections.
    */
@@ -83,6 +83,7 @@ function finalize(partialModel: PartialInsightModel<INPBreakdownInsightModel>):
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/inp-breakdown',
     category: InsightCategory.INP,
     state,
     ...partialModel,

package/front_end/models/trace/insights/ImageDelivery.ts

@@ -25,7 +25,7 @@ export const UIStrings = {
    * @description Description of an insight that recommends ways to reduce the size of images downloaded and used on the page.
    */
   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/lighthouse/performance/uses-optimized-images/)',
+      '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 Message displayed in a chip explaining that an image file size is large for the # of pixels it has and recommends possible adjustments to improve the image size.
    */
@@ -166,6 +166,7 @@ function finalize(partialModel: PartialInsightModel<ImageDeliveryInsightModel>):
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/image-delivery',
     category: InsightCategory.LCP,
     state: partialModel.optimizableImages.length > 0 ? 'fail' : 'pass',
     ...partialModel,

package/front_end/models/trace/insights/LCPBreakdown.ts

@@ -28,7 +28,7 @@ export const UIStrings = {
    * This is displayed after a user expands the section to see more. No character length limits.
    */
   description:
-      'Each [subpart has specific improvement strategies](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.',
+      '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.',
   /**
    * @description Time to first byte title for the Largest Contentful Paint's subparts timespan breakdown.
    */
@@ -197,6 +197,7 @@ function finalize(partialModel: PartialInsightModel<LCPBreakdownInsightModel>):
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/lcp-breakdown',
     category: InsightCategory.LCP,
     state,
     ...partialModel,

package/front_end/models/trace/insights/LCPDiscovery.ts

@@ -27,7 +27,7 @@ export const UIStrings = {
    * @description Description of an insight that provides details about the LCP metric, and the network requests necessary to load it.
    */
   description:
-      'Optimize LCP by making the LCP image [discoverable](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) from the HTML immediately, and [avoiding lazy-loading](https://web.dev/articles/lcp-lazy-loading)',
+      '[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 Text to tell the user how long after the earliest discovery time their LCP element loaded.
    * @example {401ms} PH1
@@ -83,6 +83,7 @@ function finalize(partialModel: PartialInsightModel<LCPDiscoveryInsightModel>):
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/lcp-discovery',
     category: InsightCategory.LCP,
     state: partialModel.lcpRequest && partialModel.checklist &&
             (!partialModel.checklist.eagerlyLoaded.value || !partialModel.checklist.requestDiscoverable.value ||

package/front_end/models/trace/insights/LegacyJavaScript.ts

@@ -28,7 +28,7 @@ export const UIStrings = {
    * @description Description of an insight that identifies polyfills for modern JavaScript features, and recommends their removal.
    */
   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://philipwalton.com/articles/the-state-of-es5-on-the-web/)',
+      '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)',
   /** Label for a column in a data table; entries will be the individual JavaScript scripts. */
   columnScript: 'Script',
   /** Label for a column in a data table; entries will be the number of wasted bytes (aka the estimated savings in terms of bytes). */
@@ -65,6 +65,7 @@ function finalize(partialModel: PartialInsightModel<LegacyJavaScriptInsightModel
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/legacy-javascript',
     category: InsightCategory.ALL,
     state: requests.length ? 'fail' : 'pass',
     relatedEvents: [...new Set(requests)],

package/front_end/models/trace/insights/ModernHTTP.ts

@@ -27,7 +27,7 @@ export const UIStrings = {
    * @description Description of an insight that recommends recommends using HTTP/2 over HTTP/1.1 because of the performance benefits. "HTTP" should not be translated.
    */
   description:
-      'HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. [Learn more about using modern HTTP](https://developer.chrome.com/docs/lighthouse/best-practices/uses-http2/).',
+      'HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. [Learn more about using modern HTTP](https://developer.chrome.com/docs/performance/insights/modern-http).',
   /**
    * @description Column header for a table where each cell represents a network request.
    */
@@ -220,6 +220,7 @@ function finalize(partialModel: PartialInsightModel<ModernHTTPInsightModel>): Mo
     strings: UIStrings,
     title: i18nString(UIStrings.title),
     description: i18nString(UIStrings.description),
+    docs: 'https://developer.chrome.com/docs/performance/insights/modern-http',
     category: InsightCategory.LCP,
     state: partialModel.http1Requests.length > 0 ? 'fail' : 'pass',
     ...partialModel,