Confirmed users
673
edits
DevTools/e10s: Difference between revisions
Jump to navigation
Jump to search
→DevTools e10s Work
| Line 38: | Line 38: | ||
==== Further Analysis ==== | ==== Further Analysis ==== | ||
* Get the remote debugging protocol server running in content | * Get the remote debugging protocol server running in content processes, and listing tabs hosted in that process. Should be able to manually connect a debugger to a specific content process (over TCP) and debug that without involvement from the chrome process. | ||
* Figure out and build the transport layer between the chrome and | * Figure out and build the transport layer between the chrome and content protocol implementations (IPDL?). | ||
== Implementation == | ==== Implementation ==== | ||
* Get tab attach to work over the chrome/content boundary. | * Get tab attach to work over the chrome/content boundary. | ||
* Get cross-navigation debugging to work correctly when the new | * Get cross-navigation debugging to work correctly when the new location is hosted in a new content process (in the meantime we will treat that as a tab close). | ||
== Web Console == | == Web Console == | ||