Add-ons • Re: Working on a Greasemonkey fork for Pale Moon

...and maybe make the "New User Script" label behave like the one that exist on Violentmonkey, Giving you the choice of either going to Greasyfork or OpenUserJS, or create a userscript on your own - possibly shortening the label to just "New..."

I also considered the drop-down menu option, but I think it adds an unnecessary step. In my opinion, it’s better to just remove the "get user script" button (and the corresponding items in the Greasemonkey button’s drop-down menu) and include a list of sites where scripts can be found in the readme. If we start listing every possible script source site in the UI, where will we stop?

Although I'm a bit skeptical on making the panel in two rows, possibly making the page look a bit...bulky.

This is just a quick prototype, so... The 2-row panel really doesn't look very good. - pic

But the 2 panels don't look that bad. - pic

1. There are a few issues with the new "Options" window:

• I saw in the code that you tried to fix the problem of content overflowing the window edges when lines are too long, but it doesn't seem to have worked - here's what I get for the test example

Honestly, that was the one mechanism where I was having a hard time the most in designing. I might just accept the defeat and just put a scroll-side at the bottom, in case if that issue were to happen.

There's no need to make such sacrifices Just trust llm less - it's enough to change

CODE:

.prefs-meta-value { width: 0; min-width: 0;}

on

CODE:

.prefs-meta-value { min-width: 1px;}

pic

In xul, when attempting to set an element's size to 0/0px, the value resets to "auto". flex hacks rarely work correctly with -moz-box. Alternatively, you can simply avoid setting "flex=1" for the element - you have a hard-coded window size that cannot be changed, and manually calculating the width isn't that difficult. Also, you don’t need to use for #greasemonkey-script-preferences. You can use and set the window size via css (as is done for #greasemonkey in install.css)

...and I should just try not to compact everything in one place and just make tabs for each.

Again, here's a quick prototype - pic's

I think it looks pretty good, and we can add other features to the "User Preferences" tab if desired.

Feature requests are also welcome into the extension and I would much rather for every single point you'd have or anyone that have for me to just type them all to me - I'm not really fond of releasing a new version of the extension every week and would much rather fix as much as I can in one release and then release a new version, when necessary, every couple of weeks or something.

Alright, I'll try to gather my thoughts and my edits together into a coherent proposal in a couple of days ))