tag:blogger.com,1999:blog-22783006.post1603248494731112395..comments2023-10-31T08:23:25.094-05:00Comments on HCI User Advocate: Missing Chrome keyboard shortcutsBenhttp://www.blogger.com/profile/02454786440233720457noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-22783006.post-85477255041763625252010-05-05T01:02:35.231-05:002010-05-05T01:02:35.231-05:00thx so much for information, btw 1 really fast wit...thx so much for information, btw <a href="http://community.gundarama.ac.id/jemiro1" rel="nofollow">1</a> really fast with google chrome :DJemirohttps://www.blogger.com/profile/12245680450451497680noreply@blogger.comtag:blogger.com,1999:blog-22783006.post-8245645357254901422010-01-21T23:42:13.399-05:002010-01-21T23:42:13.399-05:00Ideally Chrome would allow Linux users to enable &...Ideally Chrome would allow Linux users to enable "/" for find. Allow it to be enabled, but not a default would please Windows and Linux users as the Latter are very used to tweaking.<br /><br />Forcing Linux users to microsoft style ctrl-f, will keep most of us on firefoxUnknownhttps://www.blogger.com/profile/09302959813817385942noreply@blogger.comtag:blogger.com,1999:blog-22783006.post-74932528046653828892008-09-04T17:46:00.000-05:002008-09-04T17:46:00.000-05:00I think something to customize keyboard accelerato...I think something to customize keyboard accelerators would be reasonable if we could figure out a simple, powerful UI that wasn't confusing and didn't get in the way of the majority of users who didn't care.<BR/><BR/>In any case, please feel free to stop by http://dev.chromium.org/ and file bugs as you see fit. Input is always welcome.Peter Kastinghttps://www.blogger.com/profile/04331294514379362250noreply@blogger.comtag:blogger.com,1999:blog-22783006.post-84621764367925296312008-09-03T18:24:00.000-05:002008-09-03T18:24:00.000-05:00I'm glad to see these issues so well thought out. ...I'm glad to see these issues so well thought out. I'll have to wait and see over time if these choices are significant or not, but I agree that these do sound like reasonable choices given the trade-offs.<BR/><BR/>However, I still think the web is important enough that users still need a baked-in customization mechanism for their idiosyncratic use (or a plug-in architecture rich enough to support this). Then, the crazy unix-loving windows user can eek out that last bit of performance while the base solution offers something very good for most people.Benhttps://www.blogger.com/profile/02454786440233720457noreply@blogger.comtag:blogger.com,1999:blog-22783006.post-6984159047438712532008-09-03T17:20:00.000-05:002008-09-03T17:20:00.000-05:00As the primary developer of the Google Chrome Omni...As the primary developer of the Google Chrome Omnibox and one of the people who contributed to find-in-page in both Firefox and Google Chrome, I can reply to your missing shortcuts comments, although I don't know if I'll satisfy you :)<BR/><BR/>We're aware that Firefox uses tab to traverse the address bar dropdown, but in the Omnibox, tab frequently means "trigger a search on a particular site" -- this feature is sometimes called "Tab to Search". Because of this, we can't safely use tab for both actions, and in our testing, we've felt that tab-to-search is significantly more useful than selecting a non-default choice in the dropdown, so we prioritized that. We still do support arrowing through the list (as other browsers do), but our goal in the Omnibox is to minimize the number of times a user needs to select a non-default choice at all, so we hope this case occurs much less frequently.<BR/><BR/>As for find in page shortcuts, there are some problems with "/". Ctrl-f is a universal Windows shortcut for finding, whereas "/" is generally known only to users with a UNIX history, so for our Windows port it's not very discoverable. In Firefox, ctrl-f and / have subtle differences, and users used to Firefox' behavior would be frustrated if we did not replicate those differences -- yet those same differences have confused other users and led to numerous Firefox bugs in the past, so we wished to avoid this. Finally, some webpages (e.g. simple games) have JavaScript keypress handlers, and reserving "/" for "find in page" can break these pages. For all these reasons, we elected not to support "/". Hopefully the resulting burden is not too great; for touch typists, moving the left pinky to ctrl is about as bad as moving the right pinky to /.<BR/><BR/>As for launching links using just the keyboard, we agree that this is a convenience for users and would like to make some fixes in the future.Peter Kastinghttps://www.blogger.com/profile/04331294514379362250noreply@blogger.com