Move the install button to the top of the warning

[olivertzeng]

Or leave it in the settings where the user can either leave the button at the bottom or move to the top

[ACTCD]

For remotely installed third-party user scripts, you should at least read the relevant metadata carefully, and I guess that's why it was originally designed at the bottom.

[olivertzeng]

I think it should be an option to actually be able to move it to the top, since violentmonkey puts that button on the top as well Sent from Proton Mail for iOS Message ID: ***@***.***>

[ACTCD]

@quoid, what do you think about this?

[quoid]

you should at least read the relevant metadata carefully, and I guess that's why it was originally designed at the bottom.

Yep and this is my preference.

@olivertzeng You didn't include any rationale above so I am unsure why you would want the change. I don't think this ui tweak is worth a setting, but maybe if you have some strong rationale you can share it could change minds.

[olivertzeng]

you should at least read the relevant metadata carefully, and I guess that's why it was originally designed at the bottom.

Yep and this is my preference.

@olivertzeng You didn't include any rationale above so I am unsure why you would want the change. I don't think this ui tweak is worth a setting, but maybe if you have some strong rationale you can share it could change minds.

It's just that I'm too used to the violentmonkey style, it feels much comfortable having that UI tweak.
But regarding to safety measures, we need to put the button on the bottom by default but change it in user preference for the users who uses violentmonkey
Also, users are actually anticipated to review the code or at least the reputation of a script before installing a js script

[quoid]

Ok, so your rationale boils down to the fact that a different app does it this way and you’ve grown accustomed to that pattern. That is understandable, but it's not compelling enough for me to personally advocate for changing the UI. Different apps make different UI decisions all of the time, and mirroring another one doesn’t automatically make for a better experience for all users.

In this case, I think that the UX impact of the change would be minimal and have some minor security cost. The button in question isn’t one that I reckon users encounter frequently, and scrolling a few hundred pixels takes milliseconds. Introducing a setting or reworking the layout for something so minor feels like unnecessary work to me.

If there's high demand, however, I'd capitulate.

[olivertzeng]

I understand

Maybe make this stay open but label it as low priority

[ACTCD]

Thanks @quoid's comments. I personally share the view that it is not worth introducing a new "settings item" for this purpose.

But no matter what, we attach great importance to user experience and convenience. Just like the purpose of the extension.

We don't want anything to be a one-sided decision by the developer. Unless that involves issues of basic principle and safety that we can't compromise on.

With the question itself, I think that maybe we won't actively implement that feature or setting. But there is a workaround there to implement it in the future.

It depends on:

• Custom extension color scheme #777

In fact this involves a similar discussion behind the scenes about giving users a higher degree of convenience and freedom.

Anyway, when this feature was introduced, it actually allowed you to inject any CSS into the extension pages itself, so you would be able to adjust the position of the elements with custom CSS code.

I think this should take care of your preference issue.

[ACTCD]

I have to mention that the extension itself is completely open source and you can build your own version of the extension at any time, so if you have a strong preference and want to customize or modify something, you'll always be able to do so. As long as it complies with the open source license agreement, that won't create any problems. Every developer is free/libre.