Option to make programable buttons that auto inject code

Longely

Brief Summary

Feature to create programable buttons that injects the code automatically on each page you visit

Details:

Programable buttons are great. But I think in current state they are a bit limited. if they could auto inject code each time you visit a page they could replace alot of extensions. Im thinking you could have the choice when creating a button if its "auto run" or not.
and if you choose auto run, you would have a toggle when clicking the icon to turn it on or off.

Example of use case:

Dark mode, having dark mode that you need to apply after you allready got blinded isnt ideal, so it would be ideal if it just turned on when needed.

I played around with the dark mode code, and had it detect if system dark mode was on, and if the website i was visiting needed dark mode. That way if the code was auto injected i would automatically get dark mode webpages every time there was a need for it

I saw there is:

https://orionfeedback.org/d/3673-built-in-userscript-manager

So this is overlapping a bit, I guess the button would act as a quick way to turn it off or on.

you could also give the option to have the > built-in-userscript-manager create a button that can toggle it on or off.

Im open for thoughts on why one way would be better then the other, I am by no means an expert on this

Vlad

Longely What does the UI for managing the list of sites this runs on (or doesnt) look like? Is programmable button the best mechanism for this? Buttons by nature expects to be pressed. This does seem more like a feature for dedicated user scripts support, no?

Longely

Vlad

What does the UI for managing the list of sites this runs on (or doesnt) look like?

My idea was that the only UI it had was a toggle to turn on/off, to begin with at least.
So running all the time unless you turn it off

super quick sketch disregard proportions and missing text:

Buttons by nature expects to be pressed.

Yes, and that would still be the case, it would just act more like Compatibility mode or Privacy button, so something that has more the nature of extensions. Icon with options when pressed

This does seem more like a feature for dedicated user scripts support, no?

yes and no, as mentioned you could also see this as a way to request an option to have a button/icon for dedicated user scripts in the toolbar.

and I feel like programable buttons and dedicated userscripts are allready overlapping in functionality. so the question is if its beneficial to have 2 different places/UI for them.

But as said im by no means an expert on userscripts functionality and what people use them for, so idk if theres something im missing.

minte

Programmable button scripts are really useful but having to click them can get really repetitive/annoying when you find yourself clicking it everytime you visit a certain website.

I think it'd be useful to add triggers on programmable buttons to "run" when certain urls are loaded for example.

Some examples I can think of:

A website you visit often is hardcoded to light mode, so you click your Dark Mode programmable button every time you visit. You could instead add a setting to autorun the Dark Mode script when the website URL is visited.
You don't log into YouTube / clear your login cookies, but you want to view age-restricted videos a lot. You have the bypass age-restriction userscript loaded onto a programmable button, but it could instead be set up to run every time you open a YouTube video, which would unlock the video if it was restricted.
You have a button to alter the CSS styling of a website to suit your needs. A website you visit a lot needs this every time you visit, so you could set it up to automatically run when you visit the site.

The way I see this implemented is through an option within the programmable button Run Code settings where you can specify site(s) which should autorun the script on load.

A caveat is that if a user has a button dedicated solely to automatic triggers, they would no longer have a need to have the button in the toolbar in the first place, as it's never clicked. They couldn't hide it either, as to my knowledge, the button is only set up once it is placed on the toolbar, and removing it removes the data associated with it.
A possible alternate implementation would be to have custom scripts live in a menu somewhere else, but you can argue that it becomes a completely separate feature from programmable buttons. This also becomes really similar to popular extensions like tampermonkey, etc. I would definitely prefer if Orion handled automatic userscripts natively, and it doesn't seem like too big of an ask given the current functionality of programmable buttons.

Extending this even further, it would be really nice if Orion could natively handle custom stylesheets / CSS for specified websites in a similar way, but this is probably an ask for a separate suggestion.