chrome-types 0.1.357 → 0.1.358

package/_all.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Fri Jun 27 2025 22:33:50 GMT+0000 (Coordinated Universal Time)
-// Built at 9cdecf0f71c6df902469a9015c8cff2e28f4ab27
+// Generated on Mon Jun 30 2025 22:33:56 GMT+0000 (Coordinated Universal Time)
+// Built at f16e1ddc09c516addedf6d80561d468136e2c4a2
 
 // Includes all types, including MV2 + Platform Apps APIs.
 
@@ -24072,6 +24072,32 @@ declare namespace chrome {
     ): void;
   }
 
+  /**
+   * `protocol_handlers` manifest key defintion. Protocol Handlers allow developers to let extensions register Custom Handlers for URL's schemes unknown to the Browser. This manifest key provides a similar behavior than the Web API implementing the Custom Handlers section of the HTML specification. https://html.spec.whatwg.org/#custom-handlers
+   *
+   * @since Pending
+   */
+  export namespace protocolHandlers {
+
+    export interface ProtocolHandler {
+
+      /**
+       * A string definition of the protocol to handle.
+       */
+      protocol: string;
+
+      /**
+       * A string representation of the protocol handlers, displayed to the user when prompting for permissions.
+       */
+      name: string;
+
+      /**
+       * A string representing the URL of the protocol handler (must be a localizable property).
+       */
+      uriTemplate: string;
+    }
+  }
+
   /**
    * Use the `chrome.proxy` API to manage Chrome's proxy settings. This API relies on the [ChromeSetting prototype of the type API](https://developer.chrome.com/docs/extensions/reference/api/types#type-ChromeSetting) for getting and setting the proxy configuration.
    *

package/index.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Fri Jun 27 2025 22:33:45 GMT+0000 (Coordinated Universal Time)
-// Built at 9cdecf0f71c6df902469a9015c8cff2e28f4ab27
+// Generated on Mon Jun 30 2025 22:33:51 GMT+0000 (Coordinated Universal Time)
+// Built at f16e1ddc09c516addedf6d80561d468136e2c4a2
 
 // Includes MV3+ APIs only.
 
@@ -18821,6 +18821,32 @@ declare namespace chrome {
     ): void;
   }
 
+  /**
+   * `protocol_handlers` manifest key defintion. Protocol Handlers allow developers to let extensions register Custom Handlers for URL's schemes unknown to the Browser. This manifest key provides a similar behavior than the Web API implementing the Custom Handlers section of the HTML specification. https://html.spec.whatwg.org/#custom-handlers
+   *
+   * @since Pending
+   */
+  export namespace protocolHandlers {
+
+    export interface ProtocolHandler {
+
+      /**
+       * A string definition of the protocol to handle.
+       */
+      protocol: string;
+
+      /**
+       * A string representation of the protocol handlers, displayed to the user when prompting for permissions.
+       */
+      name: string;
+
+      /**
+       * A string representing the URL of the protocol handler (must be a localizable property).
+       */
+      uriTemplate: string;
+    }
+  }
+
   /**
    * Use the `chrome.proxy` API to manage Chrome's proxy settings. This API relies on the [ChromeSetting prototype of the type API](https://developer.chrome.com/docs/extensions/reference/api/types#type-ChromeSetting) for getting and setting the proxy configuration.
    *

package/package.json

@@ -5,7 +5,7 @@
   "type": "module",
   "name": "chrome-types",
   "config": {
-    "build-hash": "d9222069473b6b63"
+    "build-hash": "379ab1744f2bb5fd"
   },
   "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.357"
+  "version": "0.1.358"
 }