Skip to content

{ Tag Archives } amo

Porting a Chrome extension to WebExtensions in half a step

A coworker contacted me today about the Unbias Me extension. It’s a set of simple userscripts that hide profile pictures and names in sites like LinkedIn and GitHub, where unconscious bias can affect your behavior toward women and other groups. She wanted to know if we could have an add-on like this for Firefox. I […]

Also tagged , , ,

Interview with Extension.Zone

I was recently approached by Extension.Zone for an interview. I was pleasantly surprised to see a new website dedicated to browser-agnostic reporting of add-ons. Then I was just plain surprised that .zone is now a thing. Anyway, the interview is up here. There are some interesting questions about what makes the Firefox add-on ecosystem different […]

Also tagged , ,

The complex AMO review process

The add-on review process on AMO is fairly complicated, and can get very overwhelming if you need to look at it close enough that you must understand file and add-on statuses. AMO admins, devs, and reviewers are usually the ones who have to worry about this stuff and there aren’t good docs for it. Since […]

Also tagged , ,

Should we fix Personas?

This post is about Personas, also known as lightweight themes, not Browser ID, now known as Persona (naming is fun!). Also, these are just my thoughts, not an official position of Mozilla or the Add-ons Team. I think we skipped a step when we graduated Personas from Mozilla Labs and implemented them as a Firefox […]

Also tagged , , , , ,

All green!

Today we reached a very significant milestone. This is a screenshot of the AMO Editors dashboard, which we use to track the status of the AMO review queues. For the first time since I can remember, we are all green! What does this mean? It means that all add-ons currently waiting in the queues have […]

Also tagged , ,

Keeping add-ons compatible in the rapid release process

I began this discussion in the newsgroups today. Keeping add-ons compatible in the rapid release process. It is mostly aimed at Mozilla developers, but this should interest add-on developers just the same. We’re establishing a better system to communicate breaking changes, which should make it easier and quicker to identify what needs to be added […]

Also tagged , , , ,

Version numbers and add-on breakage

Gerv started a fairly intense discussion about the new rapid release cycle, from the perspective of browser versions and their meaning. As expected, many have replied that the discussion is silly and version numbers are meaningless. This is true for most software developers, and it should be true for most web developers. In software, we […]

Also tagged , , ,

Back from Beijing

I returned on Sunday from Beijing, where I presented at the Mozilla Developer Conference (warning: all-Mandarin page). Twice, in fact. I made a presentation about the Add-ons World (available here), and ended up stepping in for Paul Rouget, who couldn’t make it. His presentation on HTML 5 is really great and it didn’t take much […]

Also tagged , , ,

Testing add-on startup performance

Our add-on performance initiative is getting lots of attention for, lets say, various reasons. There have been objections about transparency and our testing methods, so I decided to add something valuable to the discussion and document my own testing process. I revisited my old add-on performance article and noticed that the contents of the Measuring […]

Also tagged , , ,

Firefox 4 Add-on Compatibility presentation

I’m presenting about Firefox 4 Add-on Compatibility at the Mozilla Summit a little later today. Here are the slides in PDF version for all of those interested. Firefox 4 for Add-on Developers For now, this is a pretty good reference if you want to start supporting the Firefox 4 betas in your add-ons. I’ll be […]

Also tagged , ,