I made an addon to Dektop Firefox using addon-sdk. now i want to launch it into firefox mobile(fennec) in android. I am using android 4.0.3 emulator. I have installed mobile firefox browsers(almost all versions) in it. im trying to install my addon to mobile firefox using addon-sdk. in this step i am getting different types of errors.
1.some addons installed with disable mode, but not working enable/disable option.
2.for some addons, i am getting "addon installed,restart required" option, but after restart, addon not visible in addon manager
please, provide atlesat one working way, to develop and install firefox addons(any simple) in fennec(any version) in andoid (any emulator/any mobile).
Thanks,
You are asking the wrong question. Any version of Firefox Mobile supports extensions, no problems here. However, its user interface is very different from the desktop Firefox which means that extensions built for the desktop Firefox usually won't work without adjustments. So the correct question would be:
Which version of the Add-on SDK supports Firefox Mobile?
You need Add-on SDK 1.5 or higher. When running cfx you will have to use --force-mobile command line flag to make sure that your extension is marked as compatible with Firefox Mobile. There will still be limitations however, most SDK modules currently don't support Firefox Mobile. Add-on SDK 1.8 lists the following modules as supporting Firefox Mobile:
page-mod
page-worker
request
self
simple-storage
timers
Wladimir is correct, and I would only add that we are working on expanding module support on native Fennec. If you want to play with some additional Fennec features in an SDK-based add-on right now, you can get access to the NativeWindow and BrowserApp objects Fennec implements by using this code in a module:
let utils = require('api-utils/window-utils');
exports = {
BrowserApp: utils.activeBrowserWindow.BrowserApp,
NativeWindow: utils.activeBrowserWindow.NativeWindow
};
The documentation for these objects is on MDN:
https://developer.mozilla.org/en/Extensions/Mobile/API/BrowserApp
https://developer.mozilla.org/en/DOM/window.NativeWindow
Related
We're trying to display a website via JxBrowser but this webpage says that:
one of the following plugin must be used : Silverlight, Html5, MPEG-DASH in MSE
The webPage in question is generated by MediaSite
I've read that Silverlight is not supported, but what about the others? and how to load them through JxBrowser ???
Some help would be great, even just hints to know where to search..!
Thanks.
I've read that Silverlight is not supported
Yes, Silverlight is not supported since JxBrowser 6.4 due to the fact that Chromium engine dropped the NPAPI plugin support at all.
but what about the others? and how to load them through JxBrowser ???
As far as I know HTML5 is not a Chrome plugin and is WEB standart is supported by JxBrowser by default including HTML5 audio/video.
JxBrowser supports regular Google Chrome plugins, which were installed in your system through installer. If you properly install such Chrome plugin in your system and Google Chrome recognizes this plugin, then it is expected that JxBrowser recognizes and uses this plugin as well when it is necessary.
Please note, than displaying multimedia content in JxBrowser might be different comparing to Google Chrome, due to the fact that Chromium doesn't have some codecs enabled by default. Please take a look at the article for details.
Are there any ways to simulate ionic hybrid apps on Windows 7 without using MacOS or virtual machine such as VMware/virtual box?.
Specifically, I read ionic documents and references and tried to apply sim-ios & sim-deploy on Windows 7. However, on Windows, sim-deploy seems not supported.
and the information I am looking for related to this is pretty much out-dated.
NO..., To simulate a app you need Xcode installed which you cannot on windows, You can get away with browser testing using Chrome built in browsers but that's about it.
I had the same issue when I wanted to Deploy a IOS app on windows
I was developing GWT application but as I came to know google doesn't support GWT developer plugin for Google Chrome now, provide me any other method to test my application of GWT
SuperDevMode is the new way of debugging GWT applications.
If you want to use the older GWT developer plugin then you can if you use an older browser. The latest version of Firefox that can be used is version 24. IE 11 works fine too.
GWT Development Mode will no longer be available for Chrome sometime
in 2014, so we improved alternate ways of debugging. There are
improvements to Super Dev Mode, asserts, console logging, and error
messages.Read Note
for more information about super dev mode
I am looking to use Chrome Bluetooth API's to run on Chromium Embedded Framework. Would like to know will it work? Thanks.
CEF does not support Chrome packaged apps. Chrome extensions API is not supported and without it a packaged app would be just a bundle of a javascript code running on a web page. If that's the case with your packaged app then you could make it work in CEF.
I am using Windows XP SP2 and Chrome (version 9.0.597.19) but every time I run gwt in developer mode I see:
"Development Mode requires the Google Web Toolkit Developer Plugin..."
No matter how many times I install it.
How can it be that gwt developer mode is not running in google's own chrome in xp sp2?? This is outrageous??!! It is working in FF but is very slow.
Do you have Click-to-activate-plugins enabled in Chrome? I had, and I had to click on the little puzzle piece in the URL-bar and select that all plugins may run on 127.0.0.1.
Google Web Toolkit plugin is for Firefox 3.5.x and 3.6.x and
probably Google Chrome 7. I'm also using Chrome (version 9.0.597.19) which doesn't support GWT plugin
I was having this same problem. Every time I clicked "Download the GWT Developer Plugin
For Chrome" it would start to load and then just stop without anything happening. Eventually I opened the link in a new tab and got a captcha with this message:
"Our systems have detected unusual traffic from your computer network. This page checks to see if it's really you sending the requests, and not a robot."
Maybe you are having the same problem?