<em:targetApplication>
<Description>
<em:minVersion>1.5</em:minVersion>
<em:maxVersion>3.6.16</em:maxVersion>
</Description>
</em:targetApplication>
the only declaration who get the compatibility of some firefox addon or are there any other?
I'm trying for creating my first extension whith the declaration shown. When i install my addon firefox told me that the extension is not compatible with where installed version of the browser (3.6)
You also need the ID of the application. E.g. for Firefox:
<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<em:minVersion>1.5</em:minVersion>
<em:maxVersion>3.6.16</em:maxVersion>
</Description>
</em:targetApplication>
Update: It is difficult to tell why it does not work without seeing all the code. I suggest you read this tutorial.
Related
I have installed Mozilla firebox on my system but still, firebug doesn't work. Can anyone help which version of Mozilla Firefox should I install use firebug addon.
I think the latest version of Firebug is supported in Firefox version 30.0. The searched and getting a result like this.
The latest version of Firebug is 2.0.19 and works with Firefox 30.0
Actually it's sad to say that Firebug Support has been stopped by Firefox due to the launch of new version of Firefox browser Firefox Quantum, but the good news is that all the capabilities of Firebug are now present in current Firefox Developer Tools.
It is said elsewhere, that JV Twitter module is compatible with Joomla 1.5.
Unfortunately, the archive I got does not install.
The archive content is follows:
And the error message is "Error! Could not find a Joomla! XML setup file in the package.":
The content of XML file starts with:
<?xml version="1.0" encoding="utf-8"?>
<extension type="module" version="2.5" method="upgrade">
<name>JV Twitter</name>
<author>JoomlaVi! Project</author>
<creationDate>May 2014</creationDate>
<copyright>Copyright (C) JoomlaVi. All rights reserved</copyright>
<license>http://www.gnu.org/licenseses/gpl-2.0.html GNU/GPL or later</license>
<authorEmail>info#joomlavi.com</authorEmail>
<authorUrl>www.joomlavi.com</authorUrl>
<version>4.0.8</version>
<description>JV Twitter</description>
<files>
<filename module="mod_jvtwitter">mod_jvtwitter.php</filename>
<filename>helpers.php</filename>
<filename>jvtwitter.php</filename>
<filename>index.html</filename>
<folder>assets</folder>
<folder>libs</folder>
<folder>tmpl</folder>
<folder>fields</folder>
<folder>languages</folder>
</files>
<languages folder="languages">
<language tag="en-GB">en-GB.mod_jvtwitter.ini</language>
<language tag="en-GB">en-GB.mod_jvtwitter.sys.ini</language>
</languages>
<config>
and so on.
Does this mean that actually package is not compatible with 1.5? Or it is still possible to do something?
I've looked at the developer website and this module is only compatible with Joomla 2.5 and 3.x. It will not work for Joomla 1.5 as the XML structure and content is different in the 2 versions, so you will need to find an alternative.
I would strong suggest you think about migrating to Joomla 3.x very soon. It's more secure and has more features. You may have already noticed that not many developers still support Joomla 1.5
I'm trying custom elements in DART, using the belo registration, which has worked very well.
document.registerElement(CustomElement.tag, CustomElement)
After building the pub, the file worked fine in Chrome, but not with Firefox and Internet Explorer.
I got the below error in Firefox:
TypeError: $document.registerElement is not a function
and the following error in Internet Explorer:
SCRIPT438: Object doesn't support property or method 'registerElement'
any thoughts!?
You need to load the polyfills for browsers without native custom elements support.
in pubspec.yaml you need
dependencies:
web_components: any
and in your entry page you need a script tag like
<script src="packages/web_components/platform.js"></script>
I copied the navbar default sample from from the samples but without any changes it appears to be doing what I think is mobile format. The only thing I see is the brand tag to the left and the button to the right. My monitor is pretty big so it can handle the menu and it does when I view it online which you can visually see here. I can only assume that since I cut and paste from the demo code I have a setting somewhere else that is wrong but I have no idea where to look. I did make sure to run nuget and get the latest version of the code so I should match what is on the demo. Any ideas?
Update
The issue appears to be with VS2012 and debug mode. Using Visual Studio Development Server seems to be the problem. If I publish locally it works as expected. I thought it might be IE8 but realized it was VS2012 after I published the site.
Is there a way to work around this while using the debugger in VS2012?
Update 2
And somehow it is not working in IE8 again even after being published. Chrome seems to work fine. Must be something picky about IE8 that I need to code around.
Try to copy all the page html, then if it works cut unnecessary code.
Use this instead of your local bootstrap:
<!-- Latest compiled and minified CSS -->
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css">
<!-- Optional theme -->
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap-theme.min.css">
<!-- Latest compiled and minified JavaScript -->
<script src="//maxcdn.bootstrapcdn.com/bootstrap/3.2.0/js/bootstrap.min.js"></script>
Looks like this was an issue with IE8 all along. I didn't think it was a browser issue so I never looked for IE8 nav problems but here is a link that documents the issue.
Every time i Google i get the Chrome browser - grr! But I'm trying to understand this:
use another mechanism via the chrome module. See OS.File and/or the MDN File I/O snippets.
Where can i find documentation for this Firefox+Javascript module?
How to Append to a file in a Firefox add-on?
Updated my answer in that other question. I was talking about the SDK chrome module, which is just a way to access Components and with that the XPCOM services and components, so basically what every "old school" XUL add-on gets.