I had, in fact, gone through the bug trackers of both the Chrome and Chromium(issue 150) projects a while ago, but a recent re-reading got me back to the old fervor: Here was a dead simple feature that the core developers refuse to implement, and the only reason that I can see is that some webapps (read GMail) capture the slash for its own purposes and the browser doesnt want to get in the way.
The developers insistence in ignoring users who have been begging for the feature since its inception is reminiscent of the Pidgin vs Carrier saga. Its time to fork Chromium and include slash search, methinks.
Since so many people are asking for it, I thought somebody would have already forked it, but a google search did not turn up any such projects.
I also looked briefly at an extension that was written to overcome this limitation, but comments on the thread seem to indicate that a core implementation is still desired. Hence this idea. However, there are some really nice features in the extension that I'd borrow when implementing this.
Roadmap:
- V0.1: fork Chromium and change the keyboard mapping of search from ctrl-f to /
- V0.2: Make the switch configurable via options so that people can still switch back to ctrl-f behavior if needed
- V0.3: Blacklist support for sites that use slash for their own purposes (this from the typ-ahead extension)
Thoughts:
- I looked at the source briefly assuming that finding the keyboard map should be simple. I've not yet been able to.
- The build setup also seems pretty time consuming. I should probably setup on windows (being the first implementation and all, and probably the most users), but that entails setting up on VS Express - which seems like an excursion down the proverbial rabbit hole in itself.
No comments:
Post a Comment