

That’s an important information because it’s a complete other statement to say Firefox wants what’s possible in Chrome or Firefox will support more than Chrome. Mozillas announcement says that parity with Chrome is a goal for the first version but Mozilla says explicitly that Firefox will support *more* than Chrome in the future. In the same spririt, you only mention that Mozilla wants parity with Chrome. I wonder why you only mention the negative side. I know that because there was at least on add-on developer who commented here on ghacks and said he will publish *more* add-ons in this year and not less. That will bring a lot of new add-on developers to Firefox.Ģ) There are other developers which will develop *more* extensions *because* of WebExtensions.
#Theme for mozilla firefox 49.0 pro#
And: one plus pro of WebExtensions is the big API compatibilty with extension for other browsers. But Australis also brought new great extensions and new developers. There are still many great add-ons and there still will be a lot of great add-ons in the future. Is this statement not a bit biased? Yes, some developers announced that but:ġ) That’s not new at all, every year some developers stop developing extensions for Firefox and every year new developers starts developing extensions for Firefox. > Some developers announced already that they will quit developing add-ons for Firefox, others criticized Mozilla for making the cut early as some APIs are still in development, and others might never make the cut. Now You: What's your take on the development? You can check out the engineering plan for the future of Firefox theming here. It wants feature parity with google Chrome themes, make sure that lightweight themes don't regress startup and browser window opening times, and that themes may also manipulate Firefox about pages. Mozilla set a number of goals besides that. These themes will be layered on top of the default Firefox appearance, so you can create a trivial theme that just changes one property, or a complex theme that changes all of them.

Theme developers will be able to control a variety of styles on these properties (such as colors, icons, and background images), and Firefox will ensure the manifests are supported in a stable and well-documented way across future releases and UI updates.

#Theme for mozilla firefox 49.0 full#
Mozilla plans to implement popular full theme capabilities so that they become available to lightweight theme designers.Īt its core is a JSON manifest, mapping defined property names to the underlying UI elements. Mozilla's plan is to extend the capabilities of lightweight themes in the browser. This meant that lightweight themes got the bulk of exposure which in turn meant more installs by users. While compatibility or sheer numbers is certainly one reason for that, one should note that Mozilla put the focus on lightweight themes on AMO and when it talked about themes.
