| Age | Commit message (Collapse) | Author |
|---|
|
I was getting an error sending to a null `target`. At first I thought I
should send the tab reload message to the last extension instead of the
first extension. But I later discovered that the inactive service worker
isn't even in the list of targets from `Target.getTargets`. Not sure
what to about this one. Is it possible to wake up the service worker
since we know its ID/URL?
|
|
Move the `isDebug` check to a function so we don't have to put
conditions everywhere.
|
|
|
|
There was a problem reloading the tab from an MV2 extension, and
reloading the extension after the first time. Looks like I needed to
cancel the context in order to be able to evaluate other statements in
the background page.
|
|
There may be multiple instances of the same extension ID. Ensure all of
them are reloaded.
|
|
No change.
|
|
Call getTargets only once, not each time we want to reload an extension.
This hasn't resolved the wonkiness I'm seeing with reloading multiple
extensions, unfortunately.
|
|
|
|
Turns out this is what was closing the extension background page
DevTools window. We shouldn't run the context cancel function.
|
|
Trying to set things up to not get targets again when reloading the
current tab.
|
|
Trying to make it so you can reload the tab only once after reloading
all extensions.
This still works for a single Manifest V3 extension, but I'm having
trouble getting a Manifest V2 extension to reload properly.
|
|
|
|
Get rid of the `return` so we reload more than the first extension.
|
|
|
|
|
|
|
|
Make the tab reload work based on the flag instead of always reloading.
|
|
Condition printing debug output on the presence of this flag.
|
|
Add our own errors and return these instead of logging them.
|
|
Run the reload on multiple extensions.
|
|
|
|
Move everything to our library.
|
|
|
|
Don't make this a public API. I'd rather do something simple and bad to
get this finished quickly.
|
