chrome-types 0.1.325 → 0.1.326

package/_all.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Thu Dec 12 2024 13:34:32 GMT+0000 (Coordinated Universal Time)
-// Built at 5d57323b9458e03eef51fe0ccc353e0fc286f545
+// Generated on Thu Dec 19 2024 22:31:08 GMT+0000 (Coordinated Universal Time)
+// Built at e8668587e870d154809902cf139af2984249728e
 
 // Includes all types, including MV2 + Platform Apps APIs.
 
@@ -12369,7 +12369,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 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 can be used by extensions allowlisted in that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 134+) 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 134 and can be used by extensions allowlisted through that same policy to unwrap other keys.
        *
        * 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.
        */
@@ -12378,7 +12378,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 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 can be used by extensions allowlisted in that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 134+) 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 134 and can be used by extensions allowlisted through that same policy to unwrap other keys.
        *
        * 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.
        *
@@ -22570,7 +22570,7 @@ declare namespace chrome {
     export function getAll(
 
       /**
-       * @param permissions The extension's active permissions. Note that the `origins` property will contain granted origins from those specified in the `permissions` and `optional_permissions` keys in the manifest and those associated with [Content Scripts](https://developer.chrome.com/docs/extensions/content_scripts).
+       * @param permissions The extension's active permissions. Note that the `origins` property will contain granted origins from those specified in the `permissions` and `optional_permissions` keys in the manifest and those associated with [Content Scripts](https://developer.chrome.com/docs/extensions/develop/concepts/content-scripts).
        */
       callback?: (
         permissions: Permissions,
@@ -24744,6 +24744,7 @@ declare namespace chrome {
      * Retrieves the JavaScript 'window' object for the background page running inside the current extension/app. If the background page is an event page, the system will ensure it is loaded before calling the callback. If there is no background page, an error is set.
      *
      * @chrome-returns-extra since Chrome 99
+     * @deprecated Background pages do not exist in MV3 extensions.
      * @chrome-disallow-service-workers
      */
     export function getBackgroundPage(): Promise<Window | undefined>;
@@ -24751,6 +24752,7 @@ declare namespace chrome {
     /**
      * Retrieves the JavaScript 'window' object for the background page running inside the current extension/app. If the background page is an event page, the system will ensure it is loaded before calling the callback. If there is no background page, an error is set.
      *
+     * @deprecated Background pages do not exist in MV3 extensions.
      * @chrome-disallow-service-workers
      */
     export function getBackgroundPage(
@@ -34524,9 +34526,9 @@ declare namespace chrome {
       excludeGlobs?: string[];
 
       /**
-       * The list of ScriptSource objects defining sources of scripts to be injected into matching pages.
+       * The list of ScriptSource objects defining sources of scripts to be injected into matching pages. This property must be specified for ${ref:register}, and when specified it must be a non-empty array.
        */
-      js: ScriptSource[];
+      js?: ScriptSource[];
 
       /**
        * Specifies which pages this user script will be injected into. See [Match Patterns](https://developer.chrome.com/extensions/develop/concepts/match-patterns) for more details on the syntax of these strings. This property must be specified for ${ref:register}.

package/index.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Thu Dec 12 2024 13:34:27 GMT+0000 (Coordinated Universal Time)
-// Built at 5d57323b9458e03eef51fe0ccc353e0fc286f545
+// Generated on Thu Dec 19 2024 22:31:03 GMT+0000 (Coordinated Universal Time)
+// Built at e8668587e870d154809902cf139af2984249728e
 
 // Includes MV3+ APIs only.
 
@@ -8489,7 +8489,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 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 can be used by extensions allowlisted in that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 134+) 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 134 and can be used by extensions allowlisted through that same policy to unwrap other keys.
        *
        * 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.
        */
@@ -8498,7 +8498,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 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 can be used by extensions allowlisted in that same policy to unwrap other keys.
+       * Only non-extractable keys can be generated. The supported key types are RSASSA-PKCS1-V1\_5 and RSA-OAEP (on Chrome versions 134+) 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 134 and can be used by extensions allowlisted through that same policy to unwrap other keys.
        *
        * 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.
        *
@@ -17315,7 +17315,7 @@ declare namespace chrome {
     export function getAll(
 
       /**
-       * @param permissions The extension's active permissions. Note that the `origins` property will contain granted origins from those specified in the `permissions` and `optional_permissions` keys in the manifest and those associated with [Content Scripts](https://developer.chrome.com/docs/extensions/content_scripts).
+       * @param permissions The extension's active permissions. Note that the `origins` property will contain granted origins from those specified in the `permissions` and `optional_permissions` keys in the manifest and those associated with [Content Scripts](https://developer.chrome.com/docs/extensions/develop/concepts/content-scripts).
        */
       callback?: (
         permissions: Permissions,
@@ -19478,6 +19478,7 @@ declare namespace chrome {
      * Retrieves the JavaScript 'window' object for the background page running inside the current extension/app. If the background page is an event page, the system will ensure it is loaded before calling the callback. If there is no background page, an error is set.
      *
      * @chrome-returns-extra since Chrome 99
+     * @deprecated Background pages do not exist in MV3 extensions.
      * @chrome-disallow-service-workers
      */
     export function getBackgroundPage(): Promise<Window | undefined>;
@@ -19485,6 +19486,7 @@ declare namespace chrome {
     /**
      * Retrieves the JavaScript 'window' object for the background page running inside the current extension/app. If the background page is an event page, the system will ensure it is loaded before calling the callback. If there is no background page, an error is set.
      *
+     * @deprecated Background pages do not exist in MV3 extensions.
      * @chrome-disallow-service-workers
      */
     export function getBackgroundPage(
@@ -27330,9 +27332,9 @@ declare namespace chrome {
       excludeGlobs?: string[];
 
       /**
-       * The list of ScriptSource objects defining sources of scripts to be injected into matching pages.
+       * The list of ScriptSource objects defining sources of scripts to be injected into matching pages. This property must be specified for ${ref:register}, and when specified it must be a non-empty array.
        */
-      js: ScriptSource[];
+      js?: ScriptSource[];
 
       /**
        * Specifies which pages this user script will be injected into. See [Match Patterns](https://developer.chrome.com/extensions/develop/concepts/match-patterns) for more details on the syntax of these strings. This property must be specified for ${ref:register}.

package/package.json

@@ -5,7 +5,7 @@
   "type": "module",
   "name": "chrome-types",
   "config": {
-    "build-hash": "7b1988601b06716b"
+    "build-hash": "9b273d7270847598"
   },
   "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.325"
+  "version": "0.1.326"
 }