![]() With no further communication by Andrews, userscript writers described the site as neglected and the official Greasemonkey site removed its front page link. Over the following year spam scripts became more common, server downtime increased and the install count bug remained. Prior to this, many of the "most popular scripts" as listed by the site had nominal install counts of zero. Nevertheless, he remained the sole admin of the site until a discussion about install counts began on 1 April 2013. In 2010, the last known admin Jesse Andrews posted that the site was in maintenance mode due to lack of time and asked for a new maintainer to volunteer. As the main script repository listed on Greasemonkey's official site, accumulated thousands of scripts per year. was open sourced in 2007 but the site later moved away from this code base. To accommodate the growing number of scripts, was founded by Britt Selvitelle and other members of the Greasemonkey community in late 2005. However, this criticism shifted its focus to other addons starting with the 2006 release of Adblock Plus. Greasemonkey was initially met with complaints by publishers for its ability to block ads. During this time, a Greasemonkey compiler was also developed for converting a userscript into a standalone Firefox extension. In July 2005, serious vulnerabilities were found in Greasemonkey by Mark Pilgrim, and fixed in the 3.5 version of Greasemonkey. By May 2005, there were approximately 60 general and 115 site-specific userscripts distributed for Greasemonkey. Boodman was inspired to write Greasemonkey after looking at a Firefox extension designed to clean up the interface of AllMusic, written by Adrian Holovaty, who later became a userscript developer. The Greasemonkey project began 28 November 2004, written by Aaron Boodman. Greasemonkey can be used for customizing page appearance, adding new functions to web pages (for example, embedding price comparisons within shopping sites), fixing rendering bugs, combining data from multiple web pages, and numerous other purposes. The changes made to the web pages are executed every time the page is viewed, making them effectively permanent for the user running the script. It enables users to install scripts that make on-the-fly changes to web page content after or before the page is loaded in the browser (also known as augmented browsing). Eventually.Greasemonkey is a userscript manager made available as a Mozilla Firefox extension. ![]() Some of the FF updates have been causing some item names to change, syntax?, whatever, which is a pain, but it will get figured out. In FF v55 I have a somewhat transparent navbar, tabs, new tab button, and toolbars with the default theme and using CTR. In Nighlty “Firefox – Spacious Blue Library” won’t work so I’ve modified the bookmark sidebar background color and will eventually make it darker and lighten up the text, maybe modify the line spacing also. In Nightly I’ve modified the tab width, urlbar, urlbar-zoom-button, star-button, searchbar, statuspanel, and menu items, it’s never ending. I’ve even moved to the dark side, to a small degree, and use css in Vivaldi. That said I’m using a ton of css in my FF browsers. ![]() I currently have 10 styles installed with 6 enabled (FF/WF) but use more in Pale Moon and almost all of the styles I couldn’t leave alone and have modified them from their default. I’m using Stylish in FF/Pale Moon/Waterfox so that I can use the style “Firefox – Spacious Blue Library” which won’t work in a webext. I’ve been using userChrome.css since FF v3, still a newbie, still learning! Even FF55 and FF56 broke some XUL Anonymous Please please please maintain a fork of FF52ESR or FF54 (the last firefox version that doesn’t break xul addons). If the palemoon or waterfox guys are browsing through here. I don’t even care for multiprocess Firefox as my computer has a faster enough cpu to chew through it. ![]() My workflow relies on so many XUL addons that switching to FF57+ will be a disaster. I suspect it won’t reach XUL parity couple of years from now, if it ever get there. I hope the Palemoon or Waterfox guys fork FF52 ESR or FF54 and just maintain security update for it until FF57+ get more advance api for its WebExtension. I had to revert back to FF56b12 and disabled auto update. I suspect it has to do with legacy addons problem. I could see it in the task manager, but the window doesn’t show up anywhere. I enabled legacy addons in about:config but the GUI doesn’t even show up after a restart. My Firefox Dev got updated to FF57b1 last night and all my worse nightmare came true.
0 Comments
Leave a Reply. |