Remember: file and vote on bugs! It’s how we know what we need to work on. If it’s not, you’ll need to find a creative workaround or wait for the relevant bug to get resolved. Under certain circumstances, like with RES, this might be acceptable. This keeps the script from blowing up, but it means that addURLToHistory will silently fail until Bug 1208334 gets resolved. You must explicitly mark your add-on as compatible with Firefox by adding an applications key to your manifest.json.
#Firefox bugzilla download install#
Download and install a Nightly build of Firefox.Your input will be crucial in helping Mozilla figure out which APIs to prioritize and initially support. That said, if you have a Chrome extension or a cross-browser add-on, now is a great time to experiment with WebExtensions and provide feedback. This is a sneak peek, not something you should plan on deploying. This means that it may take a while before we’re ready to support complex add-ons that rely on unique browser features, but we’ll get there eventually.īecause everything here is still very early and experimental, you’ll need to use a Nightly build of Firefox if you want to follow along.
Our first releases will be focused on building a foundation of basic, well-supported, cross-browser APIs. If you want to use RES, you should install the supported version from AMO.įirst, I want to stress that WebExtensions are a long-term, multi-year project. Note: The authors of RES are excited about WebExtensions and plan to officially port their add-on, but this is not that. Here’s what I learned, and what you can do today to prepare your own add-ons for the transition. Specifically, I tried to port the Chrome version of the popular, open-source “ Reddit Enhancement Suite” (RES) to Firefox. After reading last month’s “ Let’s Write a Web Extension,” I was inspired to try and port a real-world add-on to a WebExtension.
0 kommentar(er)
