I'm developing a firefox extension which has been working without any problems in firefox version 12.*.
Today I updated FF to version 13.0.1 and changed the install.rdf file accordingly:
<em:targetApplication>
<RDF:Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<em:minVersion>1.0</em:minVersion>
<em:maxVersion>13.0.*</em:maxVersion>
</RDF:Description>
</em:targetApplication>
But since then the extension won't be installed. The message "-Extension name- could not be installed because it is not compatible with Firefox 13.0.1" is displayed.
I used Netbeans' foxbeans plug-in to create the first dummy version of my extension (I used to be -and still am- a beginner in Firefox extension development), so the install.rdf and install.js files are automatically generated. Feel free to ask for more code if you think it could help.
Is there anyone else who has the same problem? Any possible explanations?
SOLVED:
It seems like this is a rather weird Firefox bug. I discovered that the problem was caused by an ampersand I had placed on the extension's description:
<em:description>Demokritos Labeling & Filtering Client's Firefox Extension</em:description>
If I change the above to:
<em:description>Demokritos Labeling and Filtering Client's Firefox Extension</em:description>
the extension gets installed normally.
It's a minor but rather odd bug and I should probably report it.
Do you have an updateURL in your extension?
There is an open bug that if your updateURL is incorrect, you'll get a version error:
https://bugzilla.mozilla.org/show_bug.cgi?id=740378
Related
I have a lot of data saved in XML files with XSLT to show the content properly in Firefox. But from today, Firefox doesn't interpret anymore the XSLT and shows a white page or the data in a block.
My current Firefox version is 68.0 (64-bit). Is there a bug with XSLT in the new version or is XSLT only disabled per default in Firefox 68.0?
As Tim C has pointed out in a comment, due to side effects of a security fix the use of <?xml-stylesheet href="foo.xsl" ..?> in XML documents loaded from the local file system is no longer working in Mozilla. The problem is reported as bug https://bugzilla.mozilla.org/show_bug.cgi?id=1565261 but it seems there is no intention to fix it as Chrome and other Chromium based browsers have stopped supporting XSLT referenced in XML documents loaded from the local file system long ago.
The discussions in the bug report, however, suggest that the setting privacy.file_unique_origin in about:config to false is a "workaround".
Keep in mind that it exposes you to the security problem whose fix disabled the use of XSLT referenced by xml-stylesheet processing instructions loaded from the local file system.
I get this error when I try to inline install my addon: This add-on could not be installed because it does not match the Add-on Firefox expected
I'm using this tutorial: https://developer.mozilla.org/en-US/docs/Installing_Extensions_and_Themes_From_Web_Pages
My extension is verified on AMO. This addon is a pure XML. I don't have any XPI file. And I'm pointing to this XML file in my inline install. The hash is OK (it's the same one that I got from the Firefox Developers page)
Can somebody help?
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.
It's possible?
Is there a way to install the plugin?
I've been searching trying to find a solution for this, but found nothing.
Edit: Without installing anything from Adobe.
Grab the "pdf.dll" from the latest Google Chrome version. (Download here from version 25.0.1364.172)
Put it in Chromium's install directory ("C:\Program Files\Chromium\Application" or "%appdata%/Chromium/Application/VersionNumberHere/")
Restart any running instance of Chromium.
Type "chrome://plugins" in Chromium, make sure the plugin is enabled and any other PDF plugin is disabled.
And test your browser in: http://www.google.com.br/search?q=pdf+test
Install Adobe Reader on the computer. The PDF will then display in Chrome.
Adding a Search Plugin for Firefox Via Extension is done using bundles, putting your .xml OpeSearch in /searchplugins/ directory and Firefox will automatically add them when the Extension is installed.
See https://developer.mozilla.org/en/Bundles and also my own question Including a Search Plugin in my Firefox Extension
Well, it worked fine, until i started using Firefox 6. It seems that Firefox 6 does not read the /searchplugins/ directory anymore and does not add the Search Plugin. It might be also Firefox 4 and 5, i jumped from 3.6 to 6 directly.
Any idea if this is a bug in Firefox 6?
Any idea how to by pass it and install the SearchPlugin Anyway?
I think that the only relevant difference between Firefox 3.6 and Firefox 6 (Firefox 4 actually) is that by default extensions are no longer unpacked on installation, instead they are placed into user's profile as XPI files. This works for most extensions but particularly search plugins won't work from an XPI file. Which is why you have to add the unpack flag to your install.rdf file:
<Description about="urn:mozilla:install-manifest">
<em:id>...</em:id>
<em:unpack>true</em:unpack>
...
</Description>