Chrome extensions enabled by default

Good news for developers under Chrome. Starting from the closest, support for extensions will be activated in all Chrome developer builds under Windows of the 4.x line. Previously, you could activate extensions only from the command line. From now on, the feature will be enabled by default. In other words, extensions support for ordinary people (who use stable 2.x releases) has become a bit closer. It remains to finish a couple of APIs , roll back the security system and polish the interface to high Chrome standards.



Aaron Budman, the author of the famous Greasemonkey extension for Firefox, is developing this part of Google’s functionality. He developed an innovative platform for simply writing extensions using HTML and CSS. By the way, Mozilla is also working on a similar Jetpack platform for extensions to the Firefox browser.

Aaron invites everyone to install sample extensions from the catalog and look at it with my own eyes. You can put other extensions. Just remember that the security system has not yet been done, so install programs only from reliable sources.
')
Under Mac and Linux, extensions will also be enabled by default in the near future, but now they can be activated from the command line. For example, under Mac you need to enter the command “chrome: // extensions /” in the URL.

Recently published a new version of the documentation on extensions Chrome. About the latest changes in software interfaces written here .