[BUG] Auto-reload content-script needs to check context

[louisgv]

Discussed in #206

^{Originally posted by xmsz September 14, 2022}

1. open options.html
2. modify code
3. reload

Expect:
reload options.html

Actully:
options.html close itself due to reload plugin

[louisgv]

Wow this is much more annoying than I thought - if you have a content script, the reload screw up everything!

[chenka]

I found this issue too but on chrome://<extension-id>/path-to-file.html
When I save HTML the tab was closed, and I have to reopen it every time.
This behavior cause randomly, with no error on the terminal and sometime it just disappeared, I can update code and tab wasn't closed

[louisgv]

@chenka yup it's super annoying. I will prioritize fixing it this week, otherwise, it sucks to work on my own extension xD...

[louisgv]

Also with this fix, we will adding back react-refresh runtime as well which will provide HMR for static pages

[louisgv]

Will also need to think about this: https://github.com/parcel-bundler/parcel/blob/de1569572ab681bb6e90d2b330d002b5df7947ea/packages/runtimes/webextension/src/autoreload-bg.js#L10

[louisgv]

Hmm... the background sw is propagating thorough every pages, causing the socket hmr to double trigger... will need to figure out a way to determine if bgsw is running under the context of entry pages.

[louisgv]

We might need to disable bgsw socket, and only reserves the HMR reload to the pages and scripts.

[louisgv]

https://bugs.chromium.org/p/chromium/issues/detail?id=1271154#c68

[louisgv]

https://bugs.chromium.org/p/chromium/issues/detail?id=1309263