In the same style as our other extensions, we attempt to keep it simple and useful. After installing the extension a new Xmarks button is added to your Chrome toolstrip. If this is your first extension, Chrome will display the tool strip at the bottom of your browser.

Clicking the button for the first time will start the Xmarks setup wizard (the same wizard that you see after installing Xmarks on Firefox, IE, or Safari). The difference you'll probably notice is the funky URL bar at the top. This is caused by a bug in Chrome itself and will hopefully be fixed soon. (A list of other known issues is available on our wiki page.)

After successfully setting up your account, clicking the Xmarks button will bring up the main Xmarks settings dialog. It's nearly identical to the Xmarks for Firefox settings window, although it's currently missing some of our newer features like Restore, Profiles, and Discovery. Restoring older sets of bookmarks can still be done by logging into your Xmarks web account.

The advanced settings tab gives you full control over the encryption settings for your log-in and bookmark data. Here you can also trigger a manual upload or download of your bookmarks to/from your Xmarks web account.

As mentioned before, our goal is to make Xmarks for Chrome as streamlined and smooth as Xmarks for Firefox. We're not quite there yet, but the alpha test has already helped us identify and fix a few key issues. We're excited to get the rest of the alpha testers in. Thanks for your patience!
Thanks for the update, can't wait to try it ;)
ReplyDeleteThank you for the info :D
ReplyDeleteI'm looking forward to it.
ReplyDeleteCurrently testing the plugin and loving it.
ReplyDeleteCan't wait for password support in Chrome & Xmarks for Opera.
I was waitng for xmarks to use chrome forever :) after beta I am not going to use firefox I guess :)
ReplyDeleteabout time ;)
ReplyDeletethis is great!
hi there!
ReplyDeleteany info about the fix version ?
I'm feeling more confident about the extensions implementation on the Chromium Linux, so I've submitted request to enter the alpha test. I realize that it may not be long before it's opened up to more people, but I figured "what the heck?".
ReplyDeleteAnyway, I'm just waiting now. I figure there'll be a few hiccups when I do finally start testing (what with two alpha products, it's something you should expect. XD ), but nothing a little bug jostling won't fix. ;)
p.s.: it seems smilies are "float:left"ed (css), or something like that. Perhaps a rule such as "img.smiley {float:none;}" where all smiley <img>es have class="smiley"?
ReplyDeleteNote: If < and > aren't converted, they should be "less than" and "greater than" characters. ()
Sorry about the multiple comments. The last one was a suggested solution. I presume the problem is there is a rule which makes all <img>es float:left, so that they are on the left of the text (I assume only meant to effect the images in the blog post itself).
ReplyDeleteAs an alternative to the solution I propose above, you could just modify the css rule to "div.postwrapper img {float:left}" or "div.entry > img {float:left}" (if you only want to effect images which are in the entry itself), and leave out the above proposed rule. I suppose this is all up to your web-designer to decide, though.