| accessibility.js |
|
18164 |
| addon |
|
|
| animation.js |
If the AnimationsActor was given a reference to the WalkerActor previously
then calling this getter will return the animation target NodeFront.
|
7017 |
| array-buffer.js |
A ArrayBufferClient provides a way to access ArrayBuffer from the
devtools server.
|
713 |
| blackboxing.js |
|
519 |
| breakpoint-list.js |
|
535 |
| compatibility.js |
|
529 |
| css-properties.js |
The CssProperties front provides a mechanism to have a one-time asynchronous
load of a CSS properties database. This is then fed into the CssProperties
interface that provides synchronous methods for finding out what CSS
properties the current server supports.
|
5997 |
| descriptors |
|
|
| device.js |
|
724 |
| frame.js |
|
786 |
| heap-snapshot-file.js |
|
720 |
| highlighters.js |
|
1340 |
| inspector |
|
|
| inspector.js |
Client side of the inspector actor, which is used to create
inspector-related actors, including the walker.
|
9516 |
| layout.js |
In some cases, the FlexboxActor already knows the NodeActor ID of the node where the
flexbox is located. In such cases, this getter returns the NodeFront for it.
|
3966 |
| manifest.js |
|
687 |
| memory.js |
Save a heap snapshot, transfer it from the server to the client if the
server and client do not share a file system, and return the local file
path to the heap snapshot.
Note that this is safe to call for actors inside sandoxed child processes,
as we jump through the correct IPDL hoops.
@params Boolean options.forceCopy
Always force a bulk data copy of the saved heap snapshot, even when
the server and client share a file system.
@params {object | undefined} options.boundaries
The boundaries for the heap snapshot. See
ChromeUtils.webidl for more details.
@returns Promise<String>
|
3624 |
| moz.build |
|
1330 |
| network-content.js |
|
775 |
| network-parent.js |
Client side for the network actor, used for managing network requests.
|
852 |
| node.js |
Client side of a node list as returned by querySelectorAll()
|
17218 |
| object.js |
A ObjectFront is used as a front end for the ObjectActor that is
created on the server, hiding implementation details.
|
14258 |
| objects-manager.js |
|
814 |
| page-style.js |
PageStyleFront, the front object for the PageStyleActor
|
3581 |
| perf.js |
@typedef {import("perf").BulkReceiving} BulkReceiving
|
2623 |
| preference.js |
|
881 |
| private-properties-iterator.js |
|
1641 |
| property-iterator.js |
A PropertyIteratorFront provides a way to access to property names and
values of an object efficiently, slice by slice.
Note that the properties can be sorted in the backend,
this is controled while creating the PropertyIteratorFront
from ObjectFront.enumProperties.
|
1898 |
| reflow.js |
Usage example of the reflow front:
let front = await target.getFront("reflow");
front.on("reflows", this._onReflows);
front.start();
// now wait for events to come
|
914 |
| responsive.js |
The corresponding Front object for the Responsive actor.
|
819 |
| root.js |
Retrieve all service worker registrations with their corresponding workers.
@param {Array} [workerTargets] (optional)
Array containing the result of a call to `listAllWorkerTargets`.
(this exists to avoid duplication of calls to that method)
@return {object[]} result - An Array of Objects with the following format
- {result[].registration} - The registration front
- {result[].workers} Array of form-like objects for service workers
|
10669 |
| screenshot-content.js |
|
794 |
| screenshot.js |
|
751 |
| source.js |
A SourceFront provides a way to access the source text of a script.
@param client DevToolsClient
The DevTools Client instance.
@param form Object
The form sent across the remote debugging protocol.
|
2558 |
| storage.js |
|
1893 |
| string.js |
|
1711 |
| style-rule.js |
StyleRuleFront, the front for the StyleRule actor.
|
10060 |
| style-sheets.js |
The corresponding Front object for the StyleSheetsActor.
|
1010 |
| symbol-iterator.js |
A SymbolIteratorFront is used as a front end for the SymbolIterator that is
created on the server, hiding implementation details.
|
1411 |
| target-configuration.js |
The TargetConfigurationFront/Actor should be used to populate the DevTools server
with settings read from the client side but which impact the server.
For instance, "disable cache" is a feature toggled via DevTools UI (client),
but which should be communicated to the targets (server).
See the TargetConfigurationActor for a list of supported configuration options.
|
1098 |
| targets |
|
|
| thread-configuration.js |
The ThreadConfigurationFront/Actor should be used to maintain thread settings
sent from the client for the thread actor.
See the ThreadConfigurationActor for a list of supported configuration options.
|
785 |
| thread.js |
Creates a thread front for the remote debugging protocol server. This client
is a front to the thread actor created in the server side, hiding the
protocol details in a traditional JavaScript API.
@param client DevToolsClient
@param actor string
The actor ID for this thread.
|
6582 |
| tracer.js |
|
724 |
| walker.js |
Client side of the DOM walker.
|
15367 |
| watcher.js |
Retrieve the already existing WindowGlobalTargetFront for the parent
BrowsingContext of the given BrowsingContext ID.
|
7123 |
| webconsole.js |
A WebConsoleFront is used as a front end for the WebConsoleActor that is
created on the server, hiding implementation details.
@param object client
The DevToolsClient instance we live for.
|
3062 |
| worker |
|
|