I’ve been writing about WebExtensions development on my blog. I’ve kept those posts over there because they’re short one-offs that I think would be too noisy for this blog and its wide audience.
That’s why I’m giving you this quick overview of what I’ve been writing so you can give them a closer look if you’re interested. The first two posts might interest you if you’re an add-on developer curious about WebExtensions. The second two are more meta, and touch on documentation, code review, and how we’re trying to shape the developer experience.
- Using WebExtensions to communicate between iframes. I wrote an example extension that extracts data from sub-frames in a content document. It shows how to activate content scripts for iframes and how to set up communication between them.
- Porting a Chrome extension to WebExtensions in half a step. How I took a content script Chrome extension and ported it to Firefox by just adding a little bit of metadata. Andy was quick to point out in the comments that there are plans to remove the need for that step and allow porting with no effort whatsoever.
- Some notes on WebExtensions discovery. This was an informal investigation I did around getting started as an add-on developer, and which entry points are favored by the most popular search engines.
- WebExtensions and code review. Explains which security issues often come up during add-on review for traditional extensions and some steps we could take to mitigate these issues for WebExtensions.
Let us know if there’s any topic around WebExtensions or other add-on development you want us to cover.