{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib42ou265rf6657quiuehzgrt4eqydre4wfyqcehg4nf55mwefn64",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mnaxdm3yo7d2"
  },
  "path": "/viewtopic.php?t=33298&p=275068#p275068",
  "publishedAt": "2026-06-01T20:17:48.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> ...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...\"\n\nI 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?\n\n\n> Although I'm a bit skeptical on making the panel in two rows, possibly making the page look a bit...bulky.\n\nThis is just a quick prototype, so...\nThe 2-row panel really doesn't look very good. - pic\n\nBut the 2 panels don't look that bad. - pic\n\n> > 2) There are a few issues with the new \"Options\" window:\n> - 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\n>\n> 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.\n\nThere's no need to make such sacrifices  Just trust llm less - it's enough to change\n\nCODE:\n\n\n    .prefs-meta-value { width: 0; min-width: 0;}\n\non\n\nCODE:\n\n\n    .prefs-meta-value { min-width: 1px;}\n\npic\n\nIn 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.\nAlternatively, you can simply avoid setting \"flex=1\" for the <description> element - you have a hard-coded window size that cannot be changed, and manually calculating the width isn't that difficult.\nAlso, you don’t need to use <window> for #greasemonkey-script-preferences. You can use <dialog> and set the window size via css (as is done for #greasemonkey in install.css)\n\n\n> ...and I should just try not to compact everything in one place and just make tabs for each.\n\nAgain, here's a quick prototype - pic's\n\nI think it looks pretty good, and we can add other features to the \"User Preferences\" tab if desired.\n\n\n> 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.\n\nAlright, I'll try to gather my thoughts and my edits together into a coherent proposal in a couple of days ))\n\n* * *",
  "title": "Add-ons • Re: Working on a Greasemonkey fork for Pale Moon",
  "updatedAt": "2026-06-01T20:17:48.000Z"
}