Justin Wasack

Thanks for clarifying @ACTCD The state for whether or not a userscript is disabled is stored in the extensions `manifest.json` file (**different from the webextension manifest**). That file really shouldn't...

Another note on this: The paradigm of using that manifest file was created before the WebExtension API was supported and before the extension was re-written to utilize that API. It...

> Maybe when the manifest format changes, we shouldn't overwrite it directly, but try to extract valid data from the old manifest and convert it to the new manifest to...

@jpillora Dang, I am very sorry that happened to you. I am assuming you used the default directory for saving your userscripts? You can look in `~/Library/Containers/` and search for...

@jpillora just checking in, were you were able to located your userscripts?

@jpillora Dang, I am sorry that happened. I am assuming you updated through the App Store, is that correct? What was the previous version? It's my understanding that macOS should...

This just happened to me. My scripts were located in a folder in my iCloud drive and I have 3 devices sharing those scripts (macbook, iphone and ipad). I was...

Another note, when this happened, I was having issues with iCloud in general. It was affecting Mail.app. I am not sure if this is related or not.

> maybe apple’s fault? I am thinking that could be the cause. It certainly seemed strange to me that it was only that one folder, which happened to be the...

@bheliot there are no plans to implement that key/val, but the lack of that metadata key shouldn't stop the usage of scripts. If my understanding is correct, that is a...