Tumblr 101: Tips And Tricks To Get Started
Facebook Plunges Again
New tabbed bookmark manager lands in Google Chrome developer channel
The bookmark manager in-a-tab feels is a much more logic implementation on tabbed browsers, and it's been a feature of Opera for quite some time. You can still drag-and-drop to rearrange, sort, import, and export your bookmarks like you could with the native manager.
Along with the manager, the new build includes improvements to Chrome's autofill and translate features.
Download the dev channel build of Google Chrome and take it for a spin -- or check out my previous post to see the bookmark manager in action.
Comments
7
Subscribe to commentsToby AdamsMar 27th 2010 4:54AM
But where are the favicons?
flexMar 27th 2010 5:40AM
You can even Run extensions in incognito!! All you have to do is go to the extension manager and check the box which says "allow this extension to run in incognito" This is awesome.
k7of9Mar 27th 2010 3:30PM
All I ask of Google is a simple button on my toolbar to access my bookmarks in a dropdown menu. The only way to actually access my bookmarks is to open the bookmark manager or have a bookmarks bar open _all the time_..
I know there are extensions for this but they all work or look bad.
Lee MathewsMar 27th 2010 3:31PM
Posted this last year -- Chrome has built-in support for this!
http://www.downloadsquad.com/2009/09/01/how-to-add-a-bookmarks-button-to-your-google-chrome-toolbar/
William WolfMar 27th 2010 7:17PM
Hear, Hear. That is one of the main reasons I don't use chrome. I know of the little hack that can add one but it seems to simplistic. The add-ons do not seem much better either. I've got things I don't want others to see so I can't really use the Bookmark Bar. A simple button with the advancements of say a Firefox Bookmark button would benefit me the most.
k7of9Mar 28th 2010 2:21AM
Lee that's brilliant, I had no idea that was possible. Thanks a bunch!
minibarMar 27th 2010 1:14PM
i thought that chrome was moving away from a bookmarks model and toward a more searchy model, so i don't see the point of this.
this is not my highest chrome dev priority (it's ok), but i'm still trying to wrap my mind around the chrome architecture.