Justin Wasack

@joedrew thanks for reporting this > seems to suggest that script-src-elem falls back to script-src, so maybe a simple extra if condition [in content.js](https://github.com/quoid/userscripts/blob/be3ad85c77bc036fff2bb69de40ca12a80adf75f/extension/Userscripts%20Extension/Resources/content.js#L129) would fix it? That sounds like...

Also if you could share a simplified example of the userscript that is failing that would be useful. I really just need the metadata, so the content of the code...

should be resolved in https://github.com/quoid/userscripts/commit/ad38891a1d70c43f2358e134473efd5ee83c5eb6

@SunBK201 Can you share more info? Why do you believe this is the case? Is there a code level issue? What have you experienced? Does it only affect the keyboard...

@SunBK201 Thank you very much for the video. I am trying to reproduce this on my machine, but not having luck. Edit: see next response

@SunBK201 Ok, I can see the problem, I believe. Can you you verify the following? **Did you create this userscript in an external editor and then drag it into your...

@SunBK201 thanks for confirming, will fix this bug. For now, if you keep `filename` and `@name` value the same, this bug should not appear.

> To disable editor warning put this inside .vscode/settings.json This also no longer seems to work for me, but at one point it did. `"svelte.plugin.svelte.compilerWarnings"` no longer seems like a...

@rogerfar does that disable the editor (VSCode) warnings for you?

@Ohyenno > To disable vscode warning: .... That does not silence the vscode (`Version: 1.72.1 (Universal)`) warnings any longer for me, nor does editing project level settings at `.vscode/settings.json`.