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

Edit: Nevermind, I just decided to release 3.7.0 as a stable release instead of making a second edition of the beta release, since I haven't really made risky changes and the first beta access had no issues with anyone using it.

Let's hope that it is indeed stable and won't introduce any new bugs - fingers crossed

Well, now I kind of regret not having had a chance to test the beta version, because I have a few comments for 3.7.0 (tested on pm 34.2.2)

1. If PM is open in a window less than 1320px wide, part of the content on the add-ons page overflows - pic

This is due to the size of the greasemonkey-sort-bar panel after adding new elements. It's worse if the localized version is used (and that's without translating new text; words in Russian and many other languages ​​are longer than in English) - pic

I would suggest either making the panel two rows, or creating two panels: keep the sorting panel at the top, and move "new user script" and so on to a new panel at the bottom of the view-port.

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 - pics

• The "Pages" section should be renamed to "User pages" or something similar - to more clearly indicate that it's not part of the original script;

• The "disabled this script rules and only use..." checkbox should be moved from the "Script-declarated" section to the "Pages" section - this would make more sense from a UI perspective;

• In the "Script-declared" section, the lists of sites for which the script is enabled are too narrow - any domain longer than 5 characters is simply truncated, and you have to hover over each line to get information that should be available at a glance; - pic

1. If I understand the idea of ​​the new "Options" window correctly, it's designed to provide all the important information about a script without opening the code, right? If so, I'd suggest moving the "Page" section to a new tab, like "Value", since it's not part of the script's basic information, but rather extends or replaces it.

2. I would like to ask you to move the text "gm-recover-orphans" to the DTD. Regardless of how rarely this link is likely to appear (I saw it three times during testing), leaving untranslatable text in the interface doesn't feel right.

Is that everything? I have a couple more feature requests, but those can wait. Oh, one more quick question - are you planning any text updates in the extension anytime soon, or can I create a PR with the translation update?

And thank you so much for taking on greasemonkey support. Even though I made some changes to my local copy, every time I've had to make a major change, I've looked at this pile of disparate code and given up.

Off-topic:

Off-topic: I think I have decided on the design choices and what will happen with the project:

• The UI will resemble how it currently look like on Pale Moon ("legacy" look); I have tested the chrome-like look on Pale Moon and it didn't look in-place at all, especially with other extensions in use. However, it'll have the same QoL features that exist on the upstream version, i.e. Dark mode, "Uncloak canonical names", etc...

Can I offer a few thoughts? I'm using a style to slightly change the ublock interface - pic

There are really only two changes:

• The window background isn’t pure white - it looks a little better with the default PM theme and much better with a dark theme;
• the icons are more contrasting - I don't know who decided that monotone gray-on-white/gray-on-gray icons are easy to read, but they were very, very wrong... And yes, I realize it looks pretty similar to ublock in Chrome, but I really didn’t copy it

of course kindly ask to not be pressured into the development and the maintenance of the extension, since not only it's the biggest project that can ever be taken on this platform, but I also maintain another extremely important extension as well.

Just ignore us) Since the current version of ublock legacy can't be called completely broken, you have no reason to rush.