Skip to main content

Installing Userscripts in Firefox, Opera, Chrome

Want to install a userscript on your browser. Go no further. Here are simple instructions and caveats for installing Userscripts in Firefox, Opera, Chrome. If you want to author your own scripts, here is a beginner's tutorial.


Google Chrome:
imageChrome has built in support for userscripts from Chrome 4 release. All you have to do is to navigate to the userscript. Like from userscripts.org, or from a custom web hosted .user.js file, hit the link and you will see a warning (like below) to proceed cautiously. Scripts are auto managed under Tools>Extensions. You could update or delete them from chrome:extensions

Note: Not all userscripts work in Chrome. Chrome deliberately does not load @require and @resources entries from userscripts. So the author should have developed the script from a chrome user's perspective.

Firefox:

Although,userscripts saw the light of the day @ firefox first, Firefox still does not have a native support for them. You have to Install Grease Monkey extension. However all scripting features are available.

After that, it is similar to Chrome. Just navigate to the url of the .user.js file and Grease Monkey will pick it up and install it.

Advanced script management is provided by Grease Monkey extension. Manual available here

Opera:
Opera 11 also has built in support for userscripts. But installation and management is manual. You download the .user.js file manually and install in a specified folder. This folder location can be set under Settings > Advanced > Content > JavaScript Options. Manual here.

image    image

Some scripts might not work, although Opera makes every effort to full support of user scripts

Safari and Internet Explorer:

There seems to be no direct way to get userscripts to work in Safari or IE. But there is hope for hackers. Some 3rd party tools help you achieve the effect of userscripts. But you may have to run them at your own risk.

Popular posts from this blog

Javascript: Convert Strings to Binary (and representing in a nerdy way!)

I follow those GoogleDevelopers Videos . Sometime back, in one of the presentations on GoogleIO, there was this interesting string of dots at the bottom of each page of the presentation . They looked like random big and small dots. A similar bunch of dots were also on the T-shirt of a presenter was wearing in another presentation . While it seemed something in the pattern, I could not find what it was. Finally, another presenter cleared the matter that those dots are just binary representation of "GOOGLEIO" (So much for advertizing Google IO, Impressive!). So I wanna do it. Takes me back to days of those DSP classes at school. Nerdy me had to churn some old brain cells. I remember those first programming language classes in Pascal and C when you were asked to do fibonacci series and converting a binary string to ascii codes. That *experience* came handy here: Check it out! Text to Binarize: For those who came to copy the javascript code to convert string to binary,

MySql Copying Table Structures.

Some times you need to copy only table structures across databases. This article describes two ways of doing it. If the whole database schema need to be exported, mysqldump is very effective. A --nodata flag will dump all tables' schema. Like this. mysqldump --nodata -p -u username databaseName But if you want to copy a specific table, individually, you could use "create table like" feature. You could create it even from a different database. However it must be on the same mysqld instance. Like this. create table newtable like oldtable; --Or from a table in other database create table mytable like otherdatabase.tablename;

javascript maxlength for textarea with \r\n breaks in java (esp Firefox)

Textareas allow new lines to enter. These are represented by \n (1) or \r\n (2) characters. But when you save to DB you have a limit to certain length of chars. There is no maxlength attribute in HTML that will stop you from entering data. This is generally acomplished by Javascript. You do a onkeyup hook and stop event or trim after textarea.value.length > maxlength. There are many other solutions out there.. But.. Here is the problem that most of those solutions overlook, How do you deal with the count on \n and \r\n representations. Lets first see how it matters. If the text entered has new lines, the length is calculated differently in Firefox and IE. When you enter a Text like 01234 567890 You expect the textarea.value.length to be 11. (10 chars + new line).On the backend, however, java would recieve it as 12 chars (10 chars + \r\n) (this is irrespective of FF or IE). So you are effectively saving 12 chars to DB. Worse yet, IE seems to figure textarea.value.length as 12 (