| Age | Commit message (Collapse) | Author |
|---|
|
Get the extension IDs from the Native Messaging host and reload the
specified extensions. Also reload the current tab.
Turns out this doesn't work the way I expected. It does disable and
re-enable the extension, but it doesn't reload the extension as with
`chrome.runtime.reload()`. This means the specified extension isn't
reloaded with the latest code changes.
Unfortunately, it looks like there's no API to do what I want, and
unless there's some magic in the `chrome.debugger` API I'll have to give
up on this project.
|
|
Send hard-coded extension IDs to the companion extension to tell it to
reload them. Start an event loop to keep the native host running
indefinitely.
We'll then be able to send extension IDs from a command line client to
the native host over a Unix domain socket IPC.
|
|
Use the reverse DNS name in the manifest to ensure that it's unique.
|
|
Add Native Messaging host manifest. Use a temporary path until we come
up with an install script that can reference a more permanent path.
|
|
Allows us to get a permanent extension ID that we can refer to for
Native Messaging (ID: pacpdcpgfbpkdpmhfaljffnfbdanmblh).
Generated the key with:
$ openssl rsa -in key.pem -pubout -outform DER 2>/dev/null | openssl base64 -A && echo
Using the explanation provided by Rob W
(https://stackoverflow.com/users/938089/rob-w) on Stack Overflow:
https://stackoverflow.com/questions/23873623/obtaining-chrome-extension-id-for-development/23877974#23877974
|
|
|
|
|
