[Q/A] How to re-open options when editing option.html?

[xmsz]

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

Expect:
reload options.html

Actully:
options.html close itself due to reload plugin

[louisgv]

This is an interesting thought. We will experiment a bit more with making sure the hash doesn't kill the option tab. However having a runtime that auto-open the option page is interesting... it might not be possible tho since the context after reload might be gone :-?...

[louisgv]

BTW @xmsz which version of plasmo are you using?

[louisgv]

Wait actually I just tested this, and if you're working with just the option.tsx file, the page should not close at all!

So yeah the question really is about the option.html override. I think this workflow is not really in our mind ;d.... i.e, you would change the html template every now and then but it's static by nature, so you can't really do much. You can try to inject a listener in the template that re-open with chrome.runtime.openOptionPage (like the good ol' live-reload script). But otherwise the idea should be to abstract everything to the react/tsx side.

[xmsz]

Repo: https://github.com/xmsz/demo-20220915

Only two files can case this crash

• options.tsx
• content.tsx

step:

1. npm i
2. npm run dev
3. install on chrome
4. open optionsPage on chrome extension detail page
5. modify code on options.tsx

[louisgv]

hmm, so the content script autoreload is causing this whole issue... ;d Will need to think of a way - perhaps sending more data downstream and making sure the root must be content-script, otherwise do not reload the extension...

ATM, the autoreloader reload without much discrimination on what changed - so this is where it need to be fixed

[louisgv]

moving this to bug report instead: #215