chrome-types 0.1.416 → 0.1.418

package/_all.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Thu Feb 19 2026 22:27:09 GMT+0000 (Coordinated Universal Time)
-// Built at 301af2ced25c43c50bc4c344cfb45785057198ca
+// Generated on Wed Feb 25 2026 22:27:30 GMT+0000 (Coordinated Universal Time)
+// Built at 2b93825721e2831587aedf172ceddd03c0dc30bb
 
 // Includes all types, including MV2 + Platform Apps APIs.
 
@@ -12428,7 +12428,7 @@ declare namespace chrome {
       /**
        * Implements the WebCrypto's [SubtleCrypto](https://www.w3.org/TR/WebCryptoAPI/#subtlecrypto-interface) interface. The cryptographic operations, including key generation, are hardware-backed.
        *
-       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 135+) with `modulusLength` up to 2048 and ECDSA with `namedCurve` P-256. Each RSASSA-PKCS1-V1\_5 and ECDSA key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely. RSA-OAEP keys are supported since Chrome version 135 and can be used by extensions allowlisted through that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 with `modulusLength` up to 2048 and ECDSA with `namedCurve` P-256. Each key can be used for signing data at most once, unless the extension is allowlisted by the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely.
        *
        * Keys generated on a specific `Token` cannot be used with any other Tokens, nor can they be used with `window.crypto.subtle`. Equally, `Key` objects created with `window.crypto.subtle` cannot be used with this interface.
        */
@@ -12437,7 +12437,7 @@ declare namespace chrome {
       /**
        * Implements the WebCrypto's [SubtleCrypto](https://www.w3.org/TR/WebCryptoAPI/#subtlecrypto-interface) interface. The cryptographic operations, including key generation, are software-backed. Protection of the keys, and thus implementation of the non-extractable property, is done in software, so the keys are less protected than hardware-backed keys.
        *
-       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 135+) with `modulusLength` up to 2048. Each RSASSA-PKCS1-V1\_5 key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely. RSA-OAEP keys are supported since Chrome version 135 and can be used by extensions allowlisted through that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The only supported key type is RSASSA-PKCS1-V1\_5 with `modulusLength` up to 2048. Each key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely.
        *
        * Keys generated on a specific `Token` cannot be used with any other Tokens, nor can they be used with `window.crypto.subtle`. Equally, `Key` objects created with `window.crypto.subtle` cannot be used with this interface.
        *
@@ -23668,6 +23668,13 @@ declare namespace chrome {
        */
       autofillCreditCardEnabled: types.ChromeSetting<boolean>,
 
+      /**
+       * If enabled, Chrome offers to automatically fill in the other data types. This includes travel and identity docs. This preference's value is a boolean, defaulting to `true`.
+       *
+       * @since Pending
+       */
+      autofillOtherDatatypesEnabled: types.ChromeSetting<boolean>,
+
       /**
        * If enabled, the password manager will ask if you want to save passwords. This preference's value is a boolean, defaulting to `true`.
        */
@@ -31536,10 +31543,11 @@ declare namespace chrome {
     ): void;
 
     /**
-     * Sends a single message to the content script(s) in the specified tab, with an optional callback to run when a response is sent back. The {@link runtime.onMessage} event is fired in each content script running in the specified tab for the current extension.
+     * Sends a single message to the content script(s) in the specified tab. The {@link runtime.onMessage} event is fired in each content script running in the specified tab for the current extension.
      *
      * @chrome-returns-extra since Chrome 99
      * @param message The message to send. This message should be a JSON-ifiable object.
+     * @returns Promise that resolves with the response from the content script. If an error occurs while connecting to the specified tab, the promise will be rejected.
      */
     export function sendMessage(
 
@@ -31564,7 +31572,7 @@ declare namespace chrome {
     ): Promise<any>;
 
     /**
-     * Sends a single message to the content script(s) in the specified tab, with an optional callback to run when a response is sent back. The {@link runtime.onMessage} event is fired in each content script running in the specified tab for the current extension.
+     * Sends a single message to the content script(s) in the specified tab. The {@link runtime.onMessage} event is fired in each content script running in the specified tab for the current extension.
      *
      * @param message The message to send. This message should be a JSON-ifiable object.
      */
@@ -31590,7 +31598,7 @@ declare namespace chrome {
       },
 
       /**
-       * @param response The JSON response object sent by the handler of the message. If an error occurs while connecting to the specified tab, the promise will be rejected.
+       * @param response The JSON response object sent by the handler of the message.
        * @since Chrome 99
        */
       callback?: (

package/index.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Thu Feb 19 2026 22:27:04 GMT+0000 (Coordinated Universal Time)
-// Built at 301af2ced25c43c50bc4c344cfb45785057198ca
+// Generated on Wed Feb 25 2026 22:27:26 GMT+0000 (Coordinated Universal Time)
+// Built at 2b93825721e2831587aedf172ceddd03c0dc30bb
 
 // Includes MV3+ APIs only.
 
@@ -8616,7 +8616,7 @@ declare namespace chrome {
       /**
        * Implements the WebCrypto's [SubtleCrypto](https://www.w3.org/TR/WebCryptoAPI/#subtlecrypto-interface) interface. The cryptographic operations, including key generation, are hardware-backed.
        *
-       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 135+) with `modulusLength` up to 2048 and ECDSA with `namedCurve` P-256. Each RSASSA-PKCS1-V1\_5 and ECDSA key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely. RSA-OAEP keys are supported since Chrome version 135 and can be used by extensions allowlisted through that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 with `modulusLength` up to 2048 and ECDSA with `namedCurve` P-256. Each key can be used for signing data at most once, unless the extension is allowlisted by the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely.
        *
        * Keys generated on a specific `Token` cannot be used with any other Tokens, nor can they be used with `window.crypto.subtle`. Equally, `Key` objects created with `window.crypto.subtle` cannot be used with this interface.
        */
@@ -8625,7 +8625,7 @@ declare namespace chrome {
       /**
        * Implements the WebCrypto's [SubtleCrypto](https://www.w3.org/TR/WebCryptoAPI/#subtlecrypto-interface) interface. The cryptographic operations, including key generation, are software-backed. Protection of the keys, and thus implementation of the non-extractable property, is done in software, so the keys are less protected than hardware-backed keys.
        *
-       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 135+) with `modulusLength` up to 2048. Each RSASSA-PKCS1-V1\_5 key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely. RSA-OAEP keys are supported since Chrome version 135 and can be used by extensions allowlisted through that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The only supported key type is RSASSA-PKCS1-V1\_5 with `modulusLength` up to 2048. Each key can be used for signing data at most once, unless the extension is allowlisted through the [KeyPermissions policy](https://chromeenterprise.google/policies/#KeyPermissions), in which case the key can be used indefinitely.
        *
        * Keys generated on a specific `Token` cannot be used with any other Tokens, nor can they be used with `window.crypto.subtle`. Equally, `Key` objects created with `window.crypto.subtle` cannot be used with this interface.
        *
@@ -16461,6 +16461,13 @@ declare namespace chrome {
        */
       autofillCreditCardEnabled: types.ChromeSetting<boolean>,
 
+      /**
+       * If enabled, Chrome offers to automatically fill in the other data types. This includes travel and identity docs. This preference's value is a boolean, defaulting to `true`.
+       *
+       * @since Pending
+       */
+      autofillOtherDatatypesEnabled: types.ChromeSetting<boolean>,
+
       /**
        * If enabled, the password manager will ask if you want to save passwords. This preference's value is a boolean, defaulting to `true`.
        */
@@ -22739,10 +22746,11 @@ declare namespace chrome {
     ): runtime.Port;
 
     /**
-     * Sends a single message to the content script(s) in the specified tab, with an optional callback to run when a response is sent back. The {@link runtime.onMessage} event is fired in each content script running in the specified tab for the current extension.
+     * Sends a single message to the content script(s) in the specified tab. The {@link runtime.onMessage} event is fired in each content script running in the specified tab for the current extension.
      *
      * @chrome-returns-extra since Chrome 99
      * @param message The message to send. This message should be a JSON-ifiable object.
+     * @returns Promise that resolves with the response from the content script. If an error occurs while connecting to the specified tab, the promise will be rejected.
      */
     export function sendMessage(
 
@@ -22767,7 +22775,7 @@ declare namespace chrome {
     ): Promise<any>;
 
     /**
-     * Sends a single message to the content script(s) in the specified tab, with an optional callback to run when a response is sent back. The {@link runtime.onMessage} event is fired in each content script running in the specified tab for the current extension.
+     * Sends a single message to the content script(s) in the specified tab. The {@link runtime.onMessage} event is fired in each content script running in the specified tab for the current extension.
      *
      * @param message The message to send. This message should be a JSON-ifiable object.
      */
@@ -22793,7 +22801,7 @@ declare namespace chrome {
       },
 
       /**
-       * @param response The JSON response object sent by the handler of the message. If an error occurs while connecting to the specified tab, the promise will be rejected.
+       * @param response The JSON response object sent by the handler of the message.
        * @since Chrome 99
        */
       callback?: (

package/package.json

@@ -5,7 +5,7 @@
   "type": "module",
   "name": "chrome-types",
   "config": {
-    "build-hash": "8afb6bc26ad694fe"
+    "build-hash": "987217f230487276"
   },
   "repository": {
     "type": "git",
@@ -16,5 +16,5 @@
     "url": "https://github.com/GoogleChrome/chrome-types/issues"
   },
   "homepage": "https://github.com/GoogleChrome/chrome-types",
-  "version": "0.1.416"
+  "version": "0.1.418"
 }