Skip to Content

Google Chrome for Mac (finally) gets Extension support

Exciting news for Mac-using Chrome lovers: the latest dev-channel build of Google Chrome (finally) includes support for extensions, among other new features. Similar to Firefox Add-ons, Chrome Extensions allow 3rd-party developers to add new functionality to the browser. There's a decent collection of Extensions available already at Google's Extensions Gallery, although not all of them will work with the Mac version. Interested developers can dive into the documentation on creating new extensions.

Additional features include built-in support for bookmark syncing, as well as the ability to "pin" tabs with just their favicon showing. It seems like a big jump in bringing the Mac version of Chrome up to feature parity with other platforms, which is great to see. Remember, these features are in the bleeding-edge dev channel, you won't find them (yet) in the main (likely more stable) beta download.

Side note: there's a continuing issue with Chrome on my MacBook Pro where most common web fonts show up garbled. It's only (apparently) fixable by restarting the font server (atsutil server -shutdown) before launching, but returns soon after. It might be related to FontAgent Pro, or maybe something horribly wrong with my font cache (which has been cleared and rebuilt with no results), I'm not sure. Until this one is fixed, I'm starting Chrome with a shell script that stops and then pings the font server before launching Chrome. It's not a pretty solution, and I sincerely hope I see a fix for this one soon. If you've got a solution, sound off in the comments!

[via Lifehacker]



Categories

Software

Exciting news for Mac-using Chrome lovers: the latest dev-channel build of Google Chrome (finally) includes support for extensions, among...
 

Add a Comment

*0 / 3000 Character Maximum

22 Comments

Filter by:
bangler

Just because extensions haven't been enabled by default doesn't mean they weren't working… They've worked in Chromium for the Mac for a long time now, simply by setting the '--enable-extensions' (and optionally '--enable-userscripts') flags at startup. Really no giant new step here… Extensions have been working reliably for me for quite some time.

January 11 2010 at 8:57 AM Report abuse rate up rate down Reply
Jargon

It seems to be caused by a font conflict when upgrading to Snow Leopard.

The fix is going into Font Book, looking for conflicting fonts (they have a yellow alert triangle), and deleting or disabling the conflicting copy.

January 09 2010 at 7:05 PM Report abuse rate up rate down Reply
chris.odonnell13

It does seem like Chrome is really taking its time to get up and running properly on Mac.

January 09 2010 at 2:39 PM Report abuse rate up rate down Reply
Norman

One LAST comment, i now know why i got it wrong.

Adblock + really doesn't show the "add to chrome" button, all other extensions i wanted do it.

Can someone tell me why?

http://www.chromeextensions.org/appearance-functioning/adblock/

January 08 2010 at 7:05 PM Report abuse rate up rate down Reply
Norman

Sorry, it worked now, i didn't recognize the small image on the bottom that asked to download, i'm used to see a big external popup in the middle of the screen instead of this small sentence.

And the "developer blabla" is written there always (omg so late, my english sucks).

Thnx for telling anyway, now safari is my 2nd class browser :D

January 08 2010 at 6:56 PM Report abuse rate up rate down Reply
Norman

I have 4.0.288.1 dev.

Do i need a workaround that you didn't describe? The google extensions page doesn't let me install but tells me i need chrome 4.0 or higher (or something like that):

January 08 2010 at 6:52 PM Report abuse rate up rate down Reply
Norman

Extensions also don't work for me here, used the link in the comments for the latest developer version. What could be the cause?

January 08 2010 at 6:30 PM Report abuse rate up rate down Reply
Nicola D'Agostino

Like Ben and Sean in the comments at the moment I use and recommend using Chromium, which has proven no less stable than Chrome's dev channel (while also being much more advanced).

nda

January 08 2010 at 5:18 PM Report abuse rate up rate down Reply
Sean Schraeder

Brett,

Duh! Thanks, that was it! I thought about a theme causing the issue before but I didn't think that was the problem because the build I had installed didn't suffer from it. I reset to default theme and now I am using the latest build. Thanks again!

January 08 2010 at 4:46 PM Report abuse rate up rate down Reply
Sean Schraeder

Like Ben, I use Chromium and have been loving it. If you think the dev channel builds are cutting edge, the hourly/daily updates to Chromium will make your early adopter heart flutter.

Here is the official source for mac builds, make sure you scroll to the bottom of the page for the lastest release...

http://build.chromium.org/buildbot/snapshots/chromium-rel-mac/

One thing that annoys me though is that starting with build 34474 they made the title bar blue instead of mac-like gray. Anyone know how to change it back in the newest builds??

January 08 2010 at 4:05 PM Report abuse rate up rate down Reply
1 reply to Sean Schraeder's comment
Brett Terpstra

Actually, the default build still has a grey bar. Sounds like you might have (inadvertently) installed the Classic theme from Google?

https://tools.google.com/chrome/intl/en/themes/theme_classic.html

January 08 2010 at 4:19 PM Report abuse rate up rate down Reply
Buy an ad here

Hot Apps on TUAW

Tweets

© 2012 AOL Inc. All Rights Reserved.