Name Description Size
descriptor-mixin.js A Descriptor represents a debuggable context. It can be a browser tab, a tab on a remote device, like a tab on Firefox for Android. But it can also be an add-on, as well as firefox parent process, or just one of its content process. It can be very similar to a Target. The key difference is the lifecycle of these two classes. The descriptor is meant to be always alive and meaningful/usable until the end of the RDP connection. Typically a Tab Descriptor will describe the tab and not the one document currently loaded in this tab, while the Target, will describe this one document and a new Target may be created on each navigation. 2710
descriptor-types.js List of all descriptor types. This will be expose via `descriptorType` on all descriptor fronts. 439
moz.build 434
process.js This flag should be true for parent process descriptors of a regular browser instance, where you can expect the target to be associated with a window global. This will typically be true for the descriptor used by the Browser Toolbox or the Browser Console opened against a regular Firefox instance. On the contrary this will be false for parent process descriptors created for xpcshell debugging or for background task debugging. 4859
tab.js DescriptorFront for tab targets. @fires remoteness-change Fired only for target switching, when the debugged tab is a local tab. TODO: This event could move to the server in order to support remoteness change for remote debugging. 10233
webextension.js Retrieve the WindowGlobalTargetFront for the top level WindowGlobal currently active related to the Web Extension. WebExtensionDescriptors will be created for any type of addon type (webextension, search plugin, themes). Only webextensions can be targets. This method will throw for other addon types. TODO: We should filter out non-webextension & non-debuggable addons on the server to avoid the isWebExtension check here. See Bug 1644355. 3745
worker.js 4173