ACTCD

@masklinn Yes, that's what we're going to do.

> Wouldn't this go against compatibility with userscripts that work in, say, Violentmonkey? This "compatibility" is broken and deprecated by upstream and we cannot resolve it. > Can't it be...

 `@match` may conflict with the `metadata` block, ending the comment early. Does not affect actual functionality and injection, but can cause problems in code editors or other scenarios.

I've at least seen that a dark icon is automatically generated in iOS 18 and it doesn't look bad?

I don't know, they are still beta versions and it's impossible to determine if the release version will produces a regression to the features of iOS 18.

@JohnnyFireOne I don't know what changes they made, at least I confirm it works in iOS 18. Anyway. The good news is that I have followed the latest guide to...

@JohnnyFireOne Please try the latest beta version and see if it works as expected: https://github.com/quoid/userscripts/releases

For example, this is a simple parser implementation in the browser runtime: ```js const cssText = ` userstyle-metadata { --name: "NewStyle-aefwe6zy"; --description: "This is your new file, start writing code";...

And it could also be expanded to: ```css userstyle-metadata { --name: "NewStyle-aefwe6zy"; --description: "This is your new file, start writing code"; --match: ""; --match-2: "*://*/*"; --match-3: "*://*.foo.bar/*"; --version: "1.0.0"; --download-url:...

Sorry, I checked the relevant code but I have no clue why `v0.0.0 (0)` is showing. This is actually a bit weird, since `CURRENT DIRECTORY` displays correctly. I have absolutely...