Toggle on/off userscripts for specific websites

[KamilTheDev]

Is it possible to toggle on/off a userscript only for a specific website? Seems I can only toggle a script for ALL websites only.

For example, I have a dark-mode script that runs on all websites. However, I'd like to turn it off for just some specific websites.

It'd be nice if there'd be an extra button to "turn script on/off for just this website". I know I can manually edit the script to @exclude, but it's not very intuitive.

If this is already a feature, please let me know how. Thanks.

[quoid]

@KamilTheDev

I know I can manually edit the script to @exclude, but it's not very intuitive.

As you guessed, this is how you would do that. Could you explain why you don't think it is intuitive to do this?

[KamilTheDev]

It's much more convenient and fast to "toggle on/off for this website" in just a single button press. Especially for iOS.

Dark-mode script as one example: I'm doing a quick google search, come across a website that doesn't work well with dark mode (or I prefer in light mode). Being able to toggle it off for that website quickly, and continue normal browsing.

Right now, I have to:

1. Copy current URL (annoying if I had something already in clipboard)
2. Leave Safari
3. Open code editor and select the specific Userscript file
4. Type out "@exclude" and paste URL, and cut off anything after the domain

Disrupts my browsing, and takes me over 10 seconds.
Now, with a button that toggles the script for current website, it'd take less than a second without leaving Safari.

Overall, a more user-friendly experience. Also, when there's a userscript update, it could overwrite my custom @exclude's.

Even a small green/red circle to act as the button toggle for current website would suffice. Example:

Hope you consider it. Thanks.

[quoid]

@KamilTheDev thanks for clarifying and providing examples.

I can see how this could be beneficial. Right now there's a lot of pending development tasks, but once 4.1 ships out I will certainly keep this in mind for one of the next minor version releases, if there's a viable approach to it.

[KamilTheDev]

Another idea, is that the "Matched Userscripts List for current page" act as the current website toggle, and the "all scripts view" (folder button on iOS) act as the global toggle. This is the behaviour I was expecting when I first used it.

Either way, thanks for taking my feedback. Looking forward to it.

[quoid]

Matched Userscripts List for current page" act as the current website toggle, and the "all scripts view" (folder button on iOS) act as the global toggle.

That's a cool idea.

I reckon this task will take a lot of consideration and thought. For example, there's no "all scripts view" in desktop, how is handled there? Is there a way to keep functionality as is while implementing a new interaction for this specific task? Will it be clear to the user what's going on? etc...

I really do think this would be a valuable feature addition, but I want to make sure it doesn't add any ux confusion.

[sixiansheng]

我也需�这个功能，

[ACTCD]

Another idea, is that the "Matched Userscripts List for current page" act as the current website toggle, and the "all scripts view" (folder button on iOS) act as the global toggle. This is the behaviour I was expecting when I first used it.

Either way, thanks for taking my feedback. Looking forward to it.

I don't think this is the solution, it adds to the confusion.

I think maybe the only correct way to implement this is the one like other extensions that adds a user-level exclusion list and overrides the script itself.

The discussion here is whether this added complexity is worth it.

For example we could add a button "Disable for this site" and add a *.example.com to the user-level exclusion list, but this means the granularity may not be clear enough.

So maybe the better approach is still for the user to maintain an own version of the user script.

[ACTCD]

And I also think "Dark-mode script" is not a suitable use case here, because:

• It is better suited as a standalone extension rather than a user script (I think)

• It requires earlier injection (document-start) or additional control and complexity

• It sometimes should be enabled or disabled individually even in different paths of the same website