override chrome://browser/skin/Toolbar.png chrome://browser/skin/lion/Toolbar.png os=Darwin osversion>=10

This breaks themes that try to reference Toolbar.png, since Firefox will look in the different location (in the lion subdirectory). Possible workarounds include using a different file name for the toolbar sprite and change all references in the theme, or adding a duplicate or similar file in the location Firefox expects to find it.

We haven’t decided on any solutions for this problem, but you can follow this bug if you’re interested in the outcome.

And since we’re talking themes, theme developers should read Wladimir’s post about making themes more like overlays and less like overrides. It’s a very interesting topic that was brought up at MozCamp and that I’d like to discuss it more in the future. Having feedback from theme developers is very important to give this idea some traction.

I made a presentation titled AMO, Add-on Developers and Editors (PDF version). It’s a very brief overview on who I am, what’s going on with AMO in terms of helping developers, and the editor community, with a call to action to anyone interested in joining the group. I was happy to realize that there were many developers in the audience, and some showed interest in becoming editors. For all of those interested, I’d look into the Add-on Policies docs and the Editors wiki page. There was also interest in localizing the Developer Hub content, which I think is an awesome idea. Having good documentation in our language is an important step we need to take if we want to increase developer adoption in our countries (I live in Costa Rica).

There was a lot of excitement around the idea of holding events that are more development-centric, like the Mozilla Add-on Workshops. There are already plans to hold one in Perú this year, and another one some time early next year. I’ll definitely be keeping an eye on those.

Thanks again to all of you who made MozCamp Chile possible!