All
Represents a fictional (unsafe) target with access to all possible domain APIs in all targets.
Every target supports only a subset of the protocol domains. Since these subsets are not clearly defined by the protocol definitions, the subset available in each target-specific interface is not strictly guaranteed to cover all the domains that are effectively supported by a target.
This interface is an escape hatch to provide access to all domain APIs in case some domain is missing in the target-specific interface. It should be used with care, only when you know for sure that the domains you are using are effectively supported by the real attached target, otherwise you'll get runtime errors.
This interface is generated to match the latest Chrome DevToolsProtocol definitions. It is not stable for inheritance, as new properties can be added without major version bump when the protocol changes.
Properties
(undocumented in the protocol definition)
(undocumented in the protocol definition)
Audits domain allows investigation of page violations and possible improvements.
Defines commands and events for Autofill.
Defines events for background web platform features.
The Browser domain defines methods and events for browser managing.
(undocumented in the protocol definition)
A domain for interacting with Cast, Presentation API, and Remote Playback API functionalities.
This domain is deprecated - use Runtime or Log instead.
This domain exposes CSS read/write operations. All CSS objects (stylesheets, rules, and styles) have an associated id used in subsequent operations on the related object. Each object type has a specific id structure, and those are not interchangeable between objects of different kinds. CSS objects can be loaded using the get*ForNode() calls (which accept a DOM node id). A client can also keep track of stylesheets via the styleSheetAdded/styleSheetRemoved events and subsequently load the required stylesheet contents using the getStyleSheet[Text]() methods.
(undocumented in the protocol definition)
Debugger domain exposes JavaScript debugging capabilities. It allows setting and removing breakpoints, stepping through execution, exploring stack traces, etc.
(undocumented in the protocol definition)
(undocumented in the protocol definition)
This domain exposes DOM read/write operations. Each DOM Node is represented with its mirror object that has an id. This id can be used to get additional information on the Node, resolve it into the JavaScript object wrapper, etc. It is important that client receives DOM events only for the nodes that are known to the client. Backend keeps track of the nodes that were sent to the client and never sends the same node twice. It is client's responsibility to collect information about the nodes that were sent to the client. Note that iframe owner elements will return corresponding document elements as their child nodes.
DOM debugging allows setting breakpoints on particular DOM operations and events. JavaScript execution will stop on these operations as if there was a regular breakpoint set.
This domain facilitates obtaining document snapshots with DOM, layout, and style information.
Query and modify DOM storage.
This domain emulates different environments for the page.
EventBreakpoints permits setting JavaScript breakpoints on operations and events occurring in native code invoked from JavaScript. Once breakpoint is hit, it is reported through Debugger domain, similarly to regular breakpoints being hit.
Defines commands and events for browser extensions. Available if the client is connected using the --remote-debugging-pipe flag and the --enable-unsafe-extension-debugging flag is set.
This domain allows interacting with the FedCM dialog.
A domain for letting clients substitute browser's network layer with client code.
(undocumented in the protocol definition)
This domain provides experimental commands only supported in headless mode.
(undocumented in the protocol definition)
(undocumented in the protocol definition)
(undocumented in the protocol definition)
(undocumented in the protocol definition)
(undocumented in the protocol definition)
This domain allows detailed inspection of media elements
(undocumented in the protocol definition)
Network domain allows tracking network activities of the page. It exposes information about http, file, data and other requests and responses, their headers, bodies, timing, etc.
This domain provides various functionality related to drawing atop the inspected page.
Actions and events related to the inspected page belong to the page domain.
(undocumented in the protocol definition)
Reporting of performance timeline events, as specified in https://w3c.github.io/performance-timeline/#dom-performanceobserver.
(undocumented in the protocol definition)
(undocumented in the protocol definition)
Runtime domain exposes JavaScript runtime by means of remote evaluation and mirror objects. Evaluation results are returned as mirror object that expose object type, string representation and unique identifier that can be used for further object reference. Original objects are maintained in memory unless they are either explicitly released or are released along with the other objects in their object group.
This domain is deprecated.
Security
(undocumented in the protocol definition)
(undocumented in the protocol definition)
The SystemInfo domain defines methods and events for querying low-level system information.
Supports additional targets discovery and allows to attach to them.
The Tethering domain defines methods and events for browser port binding.
(undocumented in the protocol definition)
This domain allows inspection of Web Audio API. https://webaudio.github.io/web-audio-api/
This domain allows configuring virtual authenticators to test the WebAuthn API.