Nils Maier

This works for me...

Do the settings actually stay the same (unchecked) after you a) reload the tab b) reload the extension (disable and enable again) and c) restart the browser?

It's hard to fix this without being able to reproduce this, of course. But I think I found an issue that could in theory cause this in certain browser configurations...

I committed ^ something that may or may not fix the issue. At least it shouldn't break anything else. It would be great if you could comment on whether this...

yes, the files in libs get transpiled from typescript into javascript that a browser actually understands, bundles up and placed into a few large javascript files in `bundles`

And you cannot just modify the xpi anyway, as the browser will check for a valid signature from mozilla and any changes would turn the signature invalid,

You don't need to build at all if you just `yarn`, `yarn watch` + `yarn webext`

So what I guessed might be the cause wasn't actually the cause. I'm out of ideas for now.

Well, the one other bug report I marked duplicate of this one. Other than that, nobody reported the issue, not here or not by emailing me.

Sounds like #159