content-process-jsprocessactor-startup.js |
We can't spawn the JSProcessActor right away and have to spin the event loop.
Otherwise it isn't registered yet and isn't listening to observer service.
Could it be the reason why JSProcessActor aren't spawn via process actor option's child.observers notifications ??
|
1093 |
frame-helper.js |
Force creating targets for all existing BrowsingContext, that, for a given Watcher Actor.
@param WatcherActor watcher
The Watcher Actor requesting to watch for new targets.
|
12128 |
moz.build |
|
509 |
process-helper.js |
Return the list of all DOM Processes except the one for the parent process
@return Array<nsIDOMProcessParent>
|
3241 |
service-worker-helper.js |
"chrome-event-target-created",
"webnavigation-create",
"chrome-webnavigation-create",
"webnavigation-destroy",
"chrome-webnavigation-destroy",
"browsing-context-did-set-embedder",
"browsing-context-discarded",
"ipc:content-initializing",
"ipc:content-created",
|
6788 |
service-worker-jsprocessactor-startup.js |
We can't spawn the JSProcessActor right away and have to spin the event loop.
Otherwise it isn't registered yet and isn't listening to observer service.
Could it be the reason why JSProcessActor aren't spawn via process actor option's child.observers notifications ??
|
1098 |
worker-helper.js |
Force creating targets for all existing workers for a given Watcher Actor.
@param WatcherActor watcher
The Watcher Actor requesting to watch for new targets.
|
4325 |