I want to install http://mozilla.github.io/shumway/extension/firefox/shumway.xpi in GeckoFX 45. How do it ?
Sadly because Firefox extensions are largely based around the interface and working of Firefox's UI, not just the Gecko interface, I don't think it would be possible at all currently to install extensions or .XPI files.
If you still need this, or anyone else:
https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox?as=u&utm_source=inproduct
At the bottom:
Override add-on signing (advanced users)
You can temporarily override the setting to enforce the add-on signing requirement by changing the preference xpinstall.signatures.required to false in the Firefox Configuration Editor (about:config page). Support is not available for any changes made with the Configuration Editor so please do this at your own risk.
Related
We are wanting to move our intranet users from IE to Firefox but we have some places where we want to be able to open local (or network) files or directories.
I have found quite a few references in Stack Overflow and otherwise but most of them are quite old and none of the old techniques seem to work with the current version of Firefox Quantum (v68 at the time of writing).
The Local Filesystem Links extension seems to work well but I would rather not rely on an extension, particularly one that also requires installation of an addon module, if possible.
Can anybody tell me how to access the local filesystem from a webpage in Firefox by just changing settings in about: config? Or is this just not possible anymore?
I am hoping to get something like <a href="file://///networkdrive/directory"> working if possible
I posted this question on the Mozilla support pages too and got the following solution from jscher2000 which I post here in case it is useful to others
Your timing is excellent, there is now a Policy/GPO way to do this as of Firefox 68. No extension required. See:
+ LocalFileLinks policy configuration: https://github.com/mozilla/policy-templates#localfilelinks
+ Customizing Firefox Using Group Policy (Windows)
+ Customizing Firefox Using policies.json
There also is an old school method which is backwards compatible and doesn't require an extension. It involves adding some lines to an optional user.js file (in the user's current Firefox profile), but which might be more conveniently deployed through an Autoconfig file (in the program folder). Those are both files Firefox reads at startup.
// == FILE URI LINK POLICY (checkloaduri) ==
// Create policy enabling http: or https: pages to link to file:
user_pref("capability.policy.policynames", "filelinks");
user_pref("capability.policy.filelinks.checkloaduri.enabled", "allAccess");
// Sites to which the policy applies (protocol://hostname protocol://hostname)
user_pref("capability.policy.filelinks.sites", "http://example.com http://intranet");
I tried the old school method and that worked perfectly
Our IT team have now added the policy and it is working for us but I had to do the following to get the directories to open in Windows Explorer rather than in a webpage within Firefox.
In about:config I added 2 preferences
network.protocol-handler.expose.file – set this to false
network.protocol-handler.external.file – set this to true
I am trying to build my own version of Firefox with slight UI changes and by adding some addons(extensions) to the build.
I have downloaded the source code from repo. Where would I start to achieve this?
Which all codes hold the UI structuring? Where do I put my addon xpi files?
PS: I tried to read the Mozilla documentation. Its either kinda outdated or I am not really getting it? A detailed insight would be much appreciated.
Addons
To do this, simply place the extensions in the distribution/extensions
directory in the application's distribution directory.
Here are the extension
https://dxr.mozilla.org/aviary101branch/source/browser/extensions
Flags In firefox
https://dxr.mozilla.org/aviary101branch/source/browser/config/mozconfig
Do more with themes
https://dxr.mozilla.org/aviary101branch/source/themes/modern
https://dxr.mozilla.org/aviary101branch/source/browser/themes
For Editing you may need XUL
https://www.xul.fr/tutorial/
Components
Go here and customize every component you need
https://dxr.mozilla.org/aviary101branch/source/browser/components
I'm trying to get my extension (using Firefox Addon SDK 1.17) to work on SeaMonkey (2.30). After modifying install.rdf to allow my extension to be installed, I can see SeaMonkey accepted the extension. However -- my extension's button isn't visible anywhere in the UI. I am using sdk/ui/button/toggle. I have also tried require("sdk/ui").ActionButton but that doesn't seem to do anything either.
What do I need to do to make sure my extension can render a button into SeaMonkey's toolbar?
Looks like the answer is that SeaMonkey does not officially support the Addon SDK yet. Support is planned for SeaMonkey 2.33
There are a couple of options:
patch the sdk to allow support on seamonkey.
copy the button code from the sdk into your add-on, mark it as supporting seamonkey, and use that, possibly uploading the code to npm as a third party module.
With the release of Firefox 25 we saw a huge improvement in their development tools. SO much so that I'm rather excited to try them out over Firebug.
However I can't see how to turn on Sass debugging, which is currently working in Firebug. I've looked in all the settings that are offered within the development settings.
I'm hoping I'm wrong and it is currently supported.
With Firefox 29 the support for Sass and LESS files was introduced.
Taken from https://hacks.mozilla.org/2014/02/live-editing-sass-and-less-in-the-firefox-developer-tools/
You have to right-click in the Rules section and activate Show original sources option:
Now CSS rule links will show the location in the original file, and
clicking these links will take you to the source in the Style Editor.
From there you can go on to the Styles Editor and edit your Sass/LESS file. Functionality needs Source Maps enabled!
The best suitable way to debug Sass in Firefox seems to be FireSass.
https://addons.mozilla.org/en-US/firefox/addon/firesass-for-firebug/
In Firefox this code can install a new addon:
Components.utils.import("resource://gre/modules/AddonManager.jsm");
AddonManager.getInstallForURL("http://www.foo.com/test.xpi", function(aInstall) {
// aInstall is an instance of {{AMInterface("AddonInstall")}}
aInstall.install();
}, "application/x-xpinstall");
I used it for a custom updater and works very well. Now I was wondering if is there something similar for Chrome extensions?
If you look at chrome.management API - it has all kinds of extension manipulation functions with the notable exception of extension installation. This is definitely intentional, Chrome developers don't want to allow writing "custom updaters" (something that could be easily misused).
There is only a limited solution to install extensions via chrome.webstore.install() - you get the same "service" as any website. You have to add a <link> tag to your background page like this:
<link rel="chrome-webstore-item" href="https://chrome.google.com/webstore/detail/..." />
You can call chrome.webstore.install() then and the user will be presented with a confirmation prompt. Installing extensions not present in the Web Store isn't possible, same goes for silent installations.