Not many users understood why the Google Chrome development team decided to operate with lots of switches to manage some functionality of the web browser. Users who wanted to turn on the extension engine had to launch the web browser with a parameter, the same is true for userscript support, bookmark syncing and dozens of other switches that are available as launch parameters. The reason for this method of testing is not clear to most users who think that Google could also add options to enable or disable these features in the web browser’s settings which would make it more comfortable.
There are some launch parameters that are used more often than others. The parameter to enable extensions is definitely in the top list especially with the recent increase in extensions that get released for the Google browser.
Google finally made the decision to turn on extensions by default in all Google Chrome dev releases that are released in the future (Google Chrome 4.x). Users of the latest stable release of the web browser (Google Chrome 2.x) and those of the development builds of Google Chrome 3.x are still stuck with either no extension support at all or the need to enable it by launching Google Chrome with the command line parameter.
It is also not clear if the developers will enable extension support by default when they release Google Chrome 3 final.
Read Related Posts
-
Google Chrome Extensions Manager
-
Google Chrome And Firefox Extensions Differences
-
Google Chrome Gestures Extension
-
Google Chrome Adblocker
-
Google Chrome 3 Adds Better Extension And Themes Support
-
Add Bookmarks Button In Google Chrome Address Bar
-
5 Google Chrome Extensions For Google Services
-
Google Chrome Session Saver Extension
Anything has to be better than the overhyped Mozilla “No response”, “Freeze”, “Crash” Firefox!!!
Firefox is “thankfully” on its way out. People are jumping ship on Firefox now. Its had its day.
Firefox 4.0 has to be a game changer or its heading down.