- #HOW TO GET JAVA PLUGIN FOR FIREFOX TO WORK CODE#
- #HOW TO GET JAVA PLUGIN FOR FIREFOX TO WORK WINDOWS#
Our install.rdf will look like this: Target FinderĬhrome://linktargetfinder/content/options.xul This is where you will have all the meta information about your extension, which versions of Firefox it supports and other assorted information.
#HOW TO GET JAVA PLUGIN FOR FIREFOX TO WORK CODE#
We begin with the intimidating code of install.rdf. What is needed to have a good base for your extension development, is to create the structure of the extension code. C:\extensions\ (Windows) or ~/Sites/linktargetfinder/ (Mac). In the case of our example, create a file named without any extension, and in it just point it to where you will have your code, e.g. Do that by creating a file with a unique name for you (this will have to be the same as you chose for your em:id value in your install.rdf file – more on that below). Instead of placing your code there, you can create a pointer file. In it, you will have code for all your installed extensions. In your development profile folder, you will find a folder named extensions. In that location, you will find all your Firefox profiles, and they will be named with letters and numbers, followed by a dot (.) and then your profile name, e.g. Open a terminal and type in CD ~/.mozilla/. There you will find your Firefox profiles, and they will be named with letters and numbers, followed by a dot (.) and then your profile name, e.g. Open the Terminal and type in CD ~/Library/Application\ Support/Firefox/profiles/.
#HOW TO GET JAVA PLUGIN FOR FIREFOX TO WORK WINDOWS#
In Windows 2000 and XP, open Explorer and go to C:\Documents and Settings\\Application Data\Mozilla\Firefox\Profiles and in Vista, go to C:\Users\\AppData\Roaming. The profile directory is where you will find all the settings for your Firefox profiles, including extension information. To do this, you must first find your profile directory: Find your profile directory Instead of constantly preparing and reinstalling your extension, there’s a simple way to add a pointer from your Firefox extensions directory to your code location. Point your Firefox extensions directory to your extension These aren’t necessary, but they might help you out. These are good to enable extension errors in the Firefox Error Console (Tools > Error Console), disable XUL caching and such. You can filter the existing settings, and if any of the below settings don’t exist, you can just create them. It will warn you about changing settings, but it’s ok since what you will do is only minor changes for development. Then enter about:config in the address bar. Open Firefox through the Profile Manager (process described above, or set the development profile as default during extension development). Choose Create Profile in the dialog and follow the steps. Open a terminal, use CD to navigate to your Firefox directory and then enter. Open the Terminal (located under /Applications/Utilities) and type in /Applications/Firefox.app/Contents/MacOS/firefox -profilemanager. In the run dialog, write firefox -P and press enter/click OK. Open the Windows Start menu and choose the Run option (on Vista, it might not be there – just press Windows key + R in that case). The steps to do this are: Profile manager on Windows In my case, I’ve created a new development profile named “dev”. The first step is to create a different profile in Firefox, since you will do some settings and changes that you probably don’t want for your regular profile. Then, there are some recommended things to do to prepare Firefox: Create a different development profile You need Firefox (duh) and basically whatever code editor you prefer.
What you need – setting up the developing environmentįirst, let’s start with setting up your development environment. The good part is that once you have done this, you have both an understanding of Firefox extension development as well as a blueprint for any extension you would want to develop in the future.
We will create a Firefox extension to find all links in the current web page, highlight those which have a target attribute and alert you how many links it found. If you are the developer of a legacy add-on, please refer to this page for resources to help you migrate to the current API. Please do not reference this article for extension development, as it is out-of-date. You can find reference documentation for the WebExtensions API on MDN. We encourage you to visit Extension Workshop to learn more about browser extensions and how you can build an extension for Firefox. Update: Firefox has used the WebExtensions API as its extension API since 2017.