The teams behind Google Chrome, Apple Safari, Mozilla Firefox and Microsoft Edge browsers have banded together to improve extensions, the add-ons you can download to customize the software. 

The teams unveiled a discussion and development forum at the World Wide Web Consortium, or W3C, dedicated to developing standards for extensions. The forum, the WebExtensions Community Group, gives engineers a place to build a unified and more secure core foundation for extensions. The main aim is to make it easier for developers to write extensions because a shared standard will help bridge differences between browsers.

There’s not yet a public timeline for publishing a draft of the standard or building it into browsers.

Extensions are crucial to browsers on PCs. The bits of software can block ads, integrate with password managers, strip out code that tracks you on the internet and find coupons as you put items into your shopping cart. What is more, one extension lets users replace photos of Donald Trump with cats.

Google’s Chrome is the most widely used browser in the world. But differences among browsers mean it’s less likely that an extension developer will support other browsers. Standardization should align browsers to reduce developers’ difficulties. There will still be differences among browsers, but the community group plans to ensure a common core of abilities.

The Chrome browser modernized extensions by adopting some of the same technologies, JavaScript and Cascading Style Sheets used to display web pages. Firefox and more recently Safari have followed Chrome’s lead. Edge also tapped into Chrome’s extension when Microsoft adopted Chrome’s open-source Chromium technology.

The news comes from the Apple developers conference WWDC where Apple announced it was embracing Chrome’s extension approach in Safari, despite significant differences in packaging extensions for Safari remain. The idea of standardizing extension technology has been around for years.

Opera, another browser maker, tried to unify extension technology when it adopted Chrome’s extension approach in 2010. One thing that won’t change is how you get your extensions. Each browser maker has its own extensions download site, as well as procedures for vetting them.

Several aspects of the technology are up for discussion, according to the browser extension group’s charter. The group hopes to set programming interfaces that are compatible with today’s extensions as much as possible, that doesn’t slow website performance, that doesn’t hurt privacy and that beef up security to “reduce the harm compromised or malicious browser extensions can do.”

Compatibility is the top priority on the list. The group’s charter commented that it should be relatively straightforward for developers to port extensions from one browser to another and for browsers to support extensions on a variety of devices and operating systems.

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Nikoleta Yanakieva Editor at DevStyleR International