Confirmed users
673
edits
DevTools/Features/Debugger: Difference between revisions
Browser protocol integration.
mNo edit summary |
(Browser protocol integration.) |
||
| Line 54: | Line 54: | ||
== Basic Protocol Support == | == Basic Protocol Support == | ||
Basic implementation of the [[Remote Debugging Protocol]]. | |||
=== Protocol Transports === | === Protocol Transports === | ||
| Line 73: | Line 73: | ||
=== Actor registration API === | === Actor registration API === | ||
* Including maintenance of the actor tree. | * Including maintenance of the actor tree. | ||
=== Client API === | |||
* With appropriate client-side transport support. | |||
=== Debugging compartments === | === Debugging compartments === | ||
* The debugger must be in a separate compartment from the debuggee, some sort of sandbox/new global-and-compartment for hosting a given thread's debugging actors. | * The debugger must be in a separate compartment from the debuggee, some sort of sandbox/new global-and-compartment for hosting a given thread's debugging actors. | ||
== Browser Protocol Integration == | |||
Firefox-specific integration of the remote protocol. | |||
=== Root Actor === | |||
=== Content Tab Contexts === | |||
* Will need to maintain a list of compartments needing debugging for the document tree loaded in the tab. | |||
* Manage lifetimes and notifications related to navigation. | |||
* Tabs exposed as a thread-like actor (or maybe with an immediate child for the main thread running in that tab?) | |||
=== Chrome Context === | |||
* For debugging firefox. | |||
=== WebWorker/ChromeWorker === | |||
* Related to inter-thread dispatch above. Likely to require some platform work on webworkers to get them to load the debug protocol implementation on startup? | |||
__NOTOC__ | __NOTOC__ | ||