Rob Wu
Rob Wu
That is not possible through the extension API. You can move the menu item as follows: **Disclaimer: This is an advanced hidden feature of Firefox; use at your own risk.**...
This is on my to-do list, but it has a low priority. Pull requests are welcome.
When I published this module, Firefox's support for Chrome-style buttons was bad. Now the situation has significantly been improved, so I recommend to use the built-in `sdk/ui` modules instead. Firefox...
In your background/main script: ``` browserAction.sendMessage( ... some JSON-serializable object ... ); // or, if you want to get a reply: browserAction.sendMessage( ... some JSON-serializable object ... , function(response) {...
1. `lib/browser-action-jplib-data.js` is auto-generated using `build.js` from https://github.com/Rob--W/browser-action-jplib/tree/master/data to fix https://github.com/Rob--W/browser-action-jplib/issues/1. Looking over the Addon review guidelines, I guess that your add-on got rejected because of "Obfuscated, minified or binary...
@paracetamolo Have you included a link to this issue / the source code? According to the review guidelines, your add-on should be passed up to an admin reviewer in case...
The SDK indeed supports loading resource files, but **not** from third-party libraries. To comply with the review rules, you _could_ copy the files from https://github.com/Rob--W/browser-action-jplib/tree/master/data to your extension's resource directory,...
> You can get the source code for my primitive extension here: Where?
Cannot reproduce on ArchLinux using: - Firefox Nightly 30.0a1 - Addon SDK version 1.15 (`1de7d0d1dfbda3adfd68b2157fb6f2f3fd9bbedf`) - toolbarwidget-jplib 1.3.3 [4ff24e9b3a49a6e284fe8dec82ce5f9911f32150](https://github.com/Rob--W/toolbarwidget-jplib/tree/4ff24e9b3a49a6e284fe8dec82ce5f9911f32150) - browser-action-jplib 0.2.4 (aab25cf0e4a6be00699b7689e8f3844b9ca977d1) What I did: ``` bash cd /tmp...
Can't reproduce with Firefox 28.0b4 either, on Linux and Windows. Did it "work" because you tested with Nighly, or did switching to a new Firefox profile solve your issue?