chrome-types 0.1.302 → 0.1.304

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/_all.d.ts +35 -4
  2. package/index.d.ts +35 -4
  3. package/package.json +2 -2
package/_all.d.ts CHANGED
@@ -14,8 +14,8 @@
14
14
  * limitations under the License.
15
15
  */
16
16
 
17
- // Generated on Sat Sep 07 2024 22:31:52 GMT+0000 (Coordinated Universal Time)
18
- // Built at 218dfceeb37976e28272a0bad6d095fc909f0838
17
+ // Generated on Thu Sep 12 2024 22:31:36 GMT+0000 (Coordinated Universal Time)
18
+ // Built at caa1a3b162888f00aa540908a190947fcf0bd471
19
19
 
20
20
  // Includes all types, including MV2 + Platform Apps APIs.
21
21
 
@@ -8402,7 +8402,7 @@ declare namespace chrome {
8402
8402
  /**
8403
8403
  * The headers provided by a hypothetical response if the request does not get blocked or redirected before it is sent. Represented as an object which maps a header name to a list of string values. If not specified, the hypothetical response would return empty response headers, which can match rules which match on the non-existence of headers. E.g. `{"content-type": ["text/html; charset=utf-8", "multipart/form-data"]}`
8404
8404
  *
8405
- * @since Pending
8405
+ * @since Chrome 129
8406
8406
  */
8407
8407
  responseHeaders?: {[name: string]: any};
8408
8408
  }
@@ -10188,7 +10188,7 @@ declare namespace chrome {
10188
10188
  /**
10189
10189
  * Use the `chrome.devtools.performance` API to listen to recording status updates in the Performance panel in DevTools.
10190
10190
  *
10191
- * @since Pending
10191
+ * @since Chrome 129
10192
10192
  */
10193
10193
  export namespace devtools.performance {
10194
10194
 
@@ -12740,6 +12740,37 @@ declare namespace chrome {
12740
12740
  }
12741
12741
  }
12742
12742
 
12743
+ /**
12744
+ * Experimental API to handle data collection in the browser process for AI features.
12745
+ *
12746
+ * @alpha
12747
+ * @chrome-channel dev
12748
+ */
12749
+ export namespace experimentalAiData {
12750
+
12751
+ export function getAiData(
12752
+
12753
+ domNodeId: number,
12754
+
12755
+ frameId: string,
12756
+
12757
+ userInput: string,
12758
+ ): Promise<ArrayBuffer>;
12759
+
12760
+ export function getAiData(
12761
+
12762
+ domNodeId: number,
12763
+
12764
+ frameId: string,
12765
+
12766
+ userInput: string,
12767
+
12768
+ callback?: (
12769
+ data: ArrayBuffer,
12770
+ ) => void,
12771
+ ): void;
12772
+ }
12773
+
12743
12774
  /**
12744
12775
  * The `chrome.extension` API has utilities that can be used by any extension page. It includes support for exchanging messages between an extension and its content scripts or between extensions, as described in detail in [Message Passing](https://developer.chrome.com/docs/extensions/messaging).
12745
12776
  */
package/index.d.ts CHANGED
@@ -14,8 +14,8 @@
14
14
  * limitations under the License.
15
15
  */
16
16
 
17
- // Generated on Sat Sep 07 2024 22:31:47 GMT+0000 (Coordinated Universal Time)
18
- // Built at 218dfceeb37976e28272a0bad6d095fc909f0838
17
+ // Generated on Thu Sep 12 2024 22:31:31 GMT+0000 (Coordinated Universal Time)
18
+ // Built at caa1a3b162888f00aa540908a190947fcf0bd471
19
19
 
20
20
  // Includes MV3+ APIs only.
21
21
 
@@ -5148,7 +5148,7 @@ declare namespace chrome {
5148
5148
  /**
5149
5149
  * The headers provided by a hypothetical response if the request does not get blocked or redirected before it is sent. Represented as an object which maps a header name to a list of string values. If not specified, the hypothetical response would return empty response headers, which can match rules which match on the non-existence of headers. E.g. `{"content-type": ["text/html; charset=utf-8", "multipart/form-data"]}`
5150
5150
  *
5151
- * @since Pending
5151
+ * @since Chrome 129
5152
5152
  */
5153
5153
  responseHeaders?: {[name: string]: any};
5154
5154
  }
@@ -6385,7 +6385,7 @@ declare namespace chrome {
6385
6385
  /**
6386
6386
  * Use the `chrome.devtools.performance` API to listen to recording status updates in the Performance panel in DevTools.
6387
6387
  *
6388
- * @since Pending
6388
+ * @since Chrome 129
6389
6389
  */
6390
6390
  export namespace devtools.performance {
6391
6391
 
@@ -8870,6 +8870,37 @@ declare namespace chrome {
8870
8870
  }
8871
8871
  }
8872
8872
 
8873
+ /**
8874
+ * Experimental API to handle data collection in the browser process for AI features.
8875
+ *
8876
+ * @alpha
8877
+ * @chrome-channel dev
8878
+ */
8879
+ export namespace experimentalAiData {
8880
+
8881
+ export function getAiData(
8882
+
8883
+ domNodeId: number,
8884
+
8885
+ frameId: string,
8886
+
8887
+ userInput: string,
8888
+ ): Promise<ArrayBuffer>;
8889
+
8890
+ export function getAiData(
8891
+
8892
+ domNodeId: number,
8893
+
8894
+ frameId: string,
8895
+
8896
+ userInput: string,
8897
+
8898
+ callback?: (
8899
+ data: ArrayBuffer,
8900
+ ) => void,
8901
+ ): void;
8902
+ }
8903
+
8873
8904
  /**
8874
8905
  * The `chrome.extension` API has utilities that can be used by any extension page. It includes support for exchanging messages between an extension and its content scripts or between extensions, as described in detail in [Message Passing](https://developer.chrome.com/docs/extensions/messaging).
8875
8906
  */
package/package.json CHANGED
@@ -5,7 +5,7 @@
5
5
  "type": "module",
6
6
  "name": "chrome-types",
7
7
  "config": {
8
- "build-hash": "78274e6c67807cd9"
8
+ "build-hash": "d38042d12d78de98"
9
9
  },
10
10
  "repository": {
11
11
  "type": "git",
@@ -16,5 +16,5 @@
16
16
  "url": "https://github.com/GoogleChrome/chrome-types/issues"
17
17
  },
18
18
  "homepage": "https://github.com/GoogleChrome/chrome-types",
19
- "version": "0.1.302"
19
+ "version": "0.1.304"
20
20
  }