2008-09-13 / 19:40 / dave

Since waxing poetically about chrome, I’ve hit a few more snags. So now… THE BACKLASH!

A futile search

Chrome find example

“Find in page” doesn’t search text I entered! So when I’m, say, editing my WordPress posts, I can’t search within the edit box. I know, I know another reason to actually get APP working

This turns out to be a known bug with WebKit: Bug #269

The problems with bookmark keywords

I loved Firefox’s bookmark keywords. If you’re not familiar, you basically assign a keyboard shortcut for a bookmark. For instance I assigned “rlike” to the Reddit upvote bookmarklet so I could vote without touching the mouse (well, mouse nub on the Thinkpad). It’s Ubiquity lite.

Chrome separates bookmarks (static, no keywords) from “Search Engines”, which seems like a strange design decision. I’d prefer them to be integrated or to at least allow the magic Omnibox to search through your local bookmarks. It is the Omnibox after all.

Adding search engines also has some problems. Primarily, { isn’t allowed, which pretty much kills javascript bookmarklets. The second is a minor UI issue: there’s no quick visual feedback for failed input. Hence:

  • Bug 2238: Add search engine dialog doesn’t allow “{” (open curly brace); can interfere with javascript
  • Bug 2239: Add Search Engine dialog: green checkmark icons indicate success even for failed input

Well do something about it

Turns out Chromium doesn’t build under Visual Studios Express, but that’s an ordeal for another post.