I have found a Greasemonkey script which works fine in Firefox but not in Chrome, which is my preferred browser. I have tried to fix it myself but without luck. I have posted. How do I fix it? Update: (from OP comment) Got it working by contacting the developer of TamperMonkey. With the newest beta of TamperMonkey and a modification of the script it works.
An additional issue noted: It seems that Chrome forbids the direct access to the anchor's href attribute (in some cases). However if the href attribute is retrieved via getAttribute everything works fine.
'wm.r.briscoe #answer-1033745 said' IF they DON'T fix this. I'm leaving, will just have to screw with Chrome again I'm afraid I have to agree. Greasemonkey worked for me for over 10 years and with this forced update, all my userscripts stopped working. I guess I could downgrade to get it working again or put some effort to migrate my userscripts. But in that case, I might as well switch to Chrome, where I'm not getting crippled with these user-crippling changes.
'the-edmeister #answer-1033763 said' Sorry for your issues, but all Legacy extensions are deprecated in Firefox 57. But there are many WebExtensions available for old Legacy extension replacements. Unfortunately though, not all Legacy extensions can be rewritten as WebExtensions, Here is a WebExtensions version of Greasemonkey: I know you're trying to help, but this isn't helpful at all. Greasemonkey was already updated. Define hatful. It's my userscripts that have disappeared. @wm.r.briscoe I get the feeling that you think the people answering questions here are developers or Mozilla employees. The people that answer questions here are users just like you, volunteering their time.
If you want to leave feedback for Firefox developers, go to the Help menu and select Submit Feedback. If you have a question, it would be best to, where volunteers can get more details about your setup. @moz4bugs Looking at the, it doesn't look like losing scripts is common for the update.
They say the update will break some scripts, but I don't see anything about losing scripts. Try asking in the GM forum. '@wm.r.briscoe' I get the feeling that you think the people answering questions here are developers or Mozilla employees. The people that answer questions here are users just like you, volunteering their time. If you want to leave feedback for Firefox developers, go to the 'Help' menu and select 'Submit Feedback'. If you have a question, it would be best to start a new thread, where volunteers can get more details about your setup.
'@moz4bugs' Looking at the greasemonkey website, it doesn't look like losing scripts is common for the update. They say the update will break some scripts, but I don't see anything about losing scripts. Try asking in the GM forum at https://groups.google.com/forum/#%21forum/greasemonkey-users. Chris Ilias @moz4bugs Looking at the, it doesn't look like losing scripts is common for the update. They say the update will break some scripts, but I don't see anything about losing scripts.
Try asking in the GM forum at From what I found browsing through the GreaseMonkey forums, it was because I was using local GreaseMonkey scripts and local file access is not allowed anymore with the new Firefox version. That leaves me wondering why users are left out in the dark about that.
I can't imagine that there aren't many other people using own-made scripts for GreaseMonkey. 'Chris Ilias #answer-1034344 said' '@moz4bugs' Looking at the greasemonkey website, it doesn't look like losing scripts is common for the update. They say the update will break some scripts, but I don't see anything about losing scripts. Try asking in the GM forum at From what I found browsing through the GreaseMonkey forums, it was because I was using local GreaseMonkey scripts and local file access is not allowed anymore with the new Firefox version. That leaves me wondering why users are left out in the dark about that. I can't imagine that there aren't many other people using own-made scripts for GreaseMonkey. Just a quick update regarding the bug, it turns out that you can update to Firefox 57 and the old scripts are getting transferred to the new GreaseMonkey, but not all scripts last time I checked.
I'm looking to be able to use all of my pci lanes, and looking at these 2 boards. Tiger direct has a deal going on with the 3930k and the sabertooth board, but I have use ROG boards in the past and really like them. So, what is the difference, and what do you guys think? Asus rampage iii black edition. I would like to know all of your opinions and let me know which would be the better deal.
Splinter cell blacklist deluxe edition skidrow games. Players can define their personal play styles and be rewarded for those choices. Assault players rely on instincts and frontal blow to deal with a situation. Ghost players want to remain undetected. Cities as he races against the clock to find out who’s behind this devastating threat. Own Your Play Style Splinter Cell Blacklist builds on the stealth roots of the franchise, while exploring new directions to embrace the realms of action and adventure.
It looks like the GreaseMonkey devs are working hard to get everything working again after the last Firefox update caused this breakage. But now I hear that Mozilla is pushing unwanted extensions like 'Mr Robot' to users, so I'm not moving to the new version yet: https://support.mozilla.org/en-US/questions/1194583.
WikiHow's mission is to help people learn, and we really hope this article helped you. Now you are helping others, just by visiting wikiHow. World Possible is a Nonprofit Organization with a mission to connect offline learners to the world's knowledge. They work to ensure that anyone can access the best educational resources from the web anytime, anywhere, even if they do not have an Internet connection. Click below to let us know you read this article, and wikiHow will donate to World Possible on your behalf. Thanks for helping us achieve our mission of helping everyone learn how to do anything.
Greasemonkey Install Script
I've got a Greasemonkey script for Firefox. The script includes this meta-block and some lines of code. I want to update my script on the server and then automatically update the browser's scripts. The requireSecureUpdates option is off. What am I doing wrong?
My 1.meta.js // UserScript // @name Ibood autosubmit // @include // @include // @include. // @version 1.1 // @require // @grant GMaddStyle // @downloadURL // @updateURL // /UserScript. Two problems:. Currently, your 1.meta.js is: // UserScript // @name Ibood autosubmit // @include // @include // @include.
// @version 1.7 // @require // @grant GMaddStyle // @downloadURL // @updateURL // /UserScript Note the leading spaces? Greasemonkey cannot handle leading spaces for its due to a design limitation 1. The current script version seems to be 1.8, but the meta file has version 1.7. For small scripts, that you host on your own website, don't even bother with the @updateURL setting. That's there mainly to conserve bandwidth, especially on sites like.
With no @updateURL setting, Greasemonkey will just use/check whatever's set by @downloadURL. This saves you extra maintenance work (and possible SNAFU's like this one). Finally, on an unrelated note, don't use @include.! Using @include.:. Slows down your browser. Can cause unwanted side effects. Causes conscientious users to refuse to install your script.
Specifically, this bit in the GM source file, parseScript.js: var gAllMetaRegexp = new RegExp( '^// UserScript( s S.?)^// /UserScript', 'm').
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |