Added infrastructure needed for ChromeAlive Finder #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch feels a bit too rough for a PR, but it doesn't seem to break any existing functionality, so it's probably a good time to get us back on the same branch.
One of the big changes is that communications between core/extension and Devtools private API no long users the bridges/messenger code. Instead a new hero-plugin-module called DevtoolsBackdoorModule.ts uses injected-scripts.
The old messenger/bridges code was left in, but most of this can now be ripped out -- it's now only being used to register tabs between background script and core + hideTabs.
The ChromeAlive Finder window is mostly operational but not really usable -- lots of UI issues + it's not displaying any query selectors. However, you can...