Anatoli

> Perhaps this could be done in an encoding-agnostic way? Good idea. There could be multiple directives for this functionality, like `gzip_static on`, `lzma_static on`, etc.

I guess on update you could write a new file/dir, then atomically rename/replace the old one. If an atomic rename/move is impossible (e.g. multiple chunks), some form of a journal...

@EricWittmann, thanks for the explanation. OneOf could be a solution for this case, so :+1: for its support!

Same problem on Ubuntu 16.04, vscode 1.33.0. Just installed the extension, tried the simplest configuration and it hangs loading the script. Adding `"terminalKind": "debugConsole"` solves the problem.

> So what am I supposed to do here? Just ignore verification altogether and don't care about unexpected errors if administrators set invalid values using policies? For that I suppose...

At this time, how the administrators would provide a default configuration for your extension? You can configure FF with the policies almost completely, but the configuration for the extensions is...

@M-Reimer, thanks for this implementation, but I couldn't find a definition of the variables in the `manifest.json`. AFAIK, for the options to be definable via policies, they should be defined...

@M-Reimer, the link I put in the last comment was from the official Mozilla add-ons documentation site. Do you have an example of how you define the values in policies?...

So, something like this? ``` { "policies": { "3rdparty": { "Extensions": { "{4853d046-c5a3-436b-bc36-220fd935ee1d}": { "numberShowNumber": 25, "checkPage": true, "checkTab": true } } } } } ``` When do you plan...

Then I guess the vars with their default values are: ``` "showNumber": 25, "showTabMenu": false, "showPageMenu": false, "showPageMenuitem": false, "onlyCurrent": true, "showClearList": false, "restoreGroup": false, "groupTime": 200 ``` I have...