mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-13 23:17:57 +00:00
8b61dab657
Currently, Jetpack uses two sandboxes for each content script - one for the content script itself, and another for SDK machinery. And we end up getting Xrays between the sandboxes, even though they're same-origin (generally with an nsEP) because Jetpack sandboxes use |wantXrays: true| to get same-origin Xrays. Object Xrays cause all sorts of communication problems between the sandboxes. Irakli says we don't actually need the separate sandbox anymore since we've removed the proxy layer, so let's just get rid of it. |
||
|---|---|---|
| .. | ||
| app-extension | ||
| bin | ||
| examples | ||
| lib | ||
| python-lib | ||
| test | ||
| .gitattributes | ||
| .gitignore | ||
| .hgignore | ||
| .hgtags | ||
| LICENSE | ||
| mapping.json | ||
| package.json | ||
| README | ||
Add-on SDK README ================== Before proceeding, please make sure you've installed Python 2.5, 2.6, or 2.7 (if it's not already on your system): http://python.org/download/ Note that Python 3 is not supported. For Windows users, MozillaBuild (https://wiki.mozilla.org/MozillaBuild) will install the correct version of Python and the MSYS package, which will make it easier to work with the SDK. To get started, first enter the same directory that this README file is in (the SDK's root directory) using a shell program. On Unix systems or on Windows with MSYS, you can execute the following command: source bin/activate Windows users using cmd.exe should instead run: bin\activate.bat Then go to https://developer.mozilla.org/en-US/Add-ons/SDK/ to browse the SDK documentation. If you get an error when running cfx or have any other problems getting started, see the "Troubleshooting" guide at: https://developer.mozilla.org/en-US/Add-ons/SDK/Tutorials/Troubleshooting Bugs ------- * file a bug: https://bugzilla.mozilla.org/enter_bug.cgi?product=Add-on%20SDK Style Guidelines -------------------- * https://github.com/mozilla/addon-sdk/wiki/Coding-style-guide