<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Using the keyboard with Google Chrome</title>
	<link>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/</link>
	<description>Windows keystrokes and keyboard tricks and tips that you can use to save time</description>
	<pubDate>Thu, 17 May 2012 20:51:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: ChromeConvert</title>
		<link>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-70325</link>
		<pubDate>Fri, 11 Jun 2010 02:47:33 +0000</pubDate>
		<guid>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-70325</guid>
					<description>I'm posting this info wherever I can find FAYT threads:

If you want to have this feature (find as you type/FAYT) ENABLED IN CHROME BY DEFAULT, go to
http://code.google.com/p/chromium/issues/detail?id=150 and read #4 for why it's not.  

Then star ( = vote for) the issue, tell everyone who wants FAYT enabled by default to star it, and install tokland's extension as an awesome workaround for the time being: https://chrome.google.com/extensions/detail/cpecbmjeidppdiampimghndkikcmoadk

Also, please join my group on LinkedIn, start a Facebook group, tweet about it, or do something to spread the word:  http://www.linkedin.com/groups?gid=3111816&#38;trk=myg_ugrp_ovr</description>
		<content:encoded><![CDATA[<p>I&#8217;m posting this info wherever I can find FAYT threads:</p>
<p>If you want to have this feature (find as you type/FAYT) ENABLED IN CHROME BY DEFAULT, go to<br />
<a href="http://code.google.com/p/chromium/issues/detail?id=150" rel="nofollow">http://code.google.com/p/chromium/issues/detail?id=150</a> and read #4 for why it&#8217;s not.  </p>
<p>Then star ( = vote for) the issue, tell everyone who wants FAYT enabled by default to star it, and install tokland&#8217;s extension as an awesome workaround for the time being: <a href="https://chrome.google.com/extensions/detail/cpecbmjeidppdiampimghndkikcmoadk" rel="nofollow">https://chrome.google.com/extensions/detail/cpecbmjeidppdiampimghndkikcmoadk</a></p>
<p>Also, please join my group on LinkedIn, start a Facebook group, tweet about it, or do something to spread the word:  <a href="http://www.linkedin.com/groups?gid=3111816&amp;trk=myg_ugrp_ovr" rel="nofollow">http://www.linkedin.com/groups?gid=3111816&amp;trk=myg_ugrp_ovr</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: estephen</title>
		<link>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12936</link>
		<pubDate>Sat, 06 Sep 2008 04:33:50 +0000</pubDate>
		<guid>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12936</guid>
					<description>To do "find next" just press Ctrl+G or F3. To find previous, Ctrl+Shift+G, or Shift+F3.

Actually, just Ctrl+F, search text, Enter and keep hitting Enter works too.</description>
		<content:encoded><![CDATA[<p>To do &#8220;find next&#8221; just press Ctrl+G or F3. To find previous, Ctrl+Shift+G, or Shift+F3.</p>
<p>Actually, just Ctrl+F, search text, Enter and keep hitting Enter works too.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Erik</title>
		<link>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12864</link>
		<pubDate>Fri, 05 Sep 2008 06:02:27 +0000</pubDate>
		<guid>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12864</guid>
					<description>I noticed a minor typo - the hard refresh shortcuts are written right now as ctrl+r or ctrl+f5, when in reality it should read ctrl+shift+r or ctrl+f5.

Also, I'm curious if anyone knows how to do "next" from the keyboard after doing ctrl+f.  I've been searching everywhere, tried every ctrl/alt+key combo I could think of... nothing</description>
		<content:encoded><![CDATA[<p>I noticed a minor typo - the hard refresh shortcuts are written right now as ctrl+r or ctrl+f5, when in reality it should read ctrl+shift+r or ctrl+f5.</p>
<p>Also, I&#8217;m curious if anyone knows how to do &#8220;next&#8221; from the keyboard after doing ctrl+f.  I&#8217;ve been searching everywhere, tried every ctrl/alt+key combo I could think of&#8230; nothing
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hasrh S</title>
		<link>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12711</link>
		<pubDate>Wed, 03 Sep 2008 13:11:53 +0000</pubDate>
		<guid>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12711</guid>
					<description>There was a snag while accessing music online on www.esnips.com
None of the files played. I wonder if this categorizes as a bug. But yeah did report the problem to the techie guys using bug reporter thing.</description>
		<content:encoded><![CDATA[<p>There was a snag while accessing music online on <a href="http://www.esnips.com" rel="nofollow">www.esnips.com</a><br />
None of the files played. I wonder if this categorizes as a bug. But yeah did report the problem to the techie guys using bug reporter thing.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: estephen</title>
		<link>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12684</link>
		<pubDate>Wed, 03 Sep 2008 00:48:35 +0000</pubDate>
		<guid>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12684</guid>
					<description>Interesting. I'm not a big user of slash myself (even though I understand why Unix users have it more ingrained due to the prominence of slash search with more and most editors). But I can definitely relate to where you're coming from.

With Chrome, your closest workaround is to type Ctrl+F, type the text, then click the link. That is a pain.

I've submitted this page as a "bug" to the Chrome team, so hopefully they'll check it out and add support before release.</description>
		<content:encoded><![CDATA[<p>Interesting. I&#8217;m not a big user of slash myself (even though I understand why Unix users have it more ingrained due to the prominence of slash search with more and most editors). But I can definitely relate to where you&#8217;re coming from.</p>
<p>With Chrome, your closest workaround is to type Ctrl+F, type the text, then click the link. That is a pain.</p>
<p>I&#8217;ve submitted this page as a &#8220;bug&#8221; to the Chrome team, so hopefully they&#8217;ll check it out and add support before release.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: slacy</title>
		<link>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12677</link>
		<pubDate>Wed, 03 Sep 2008 00:27:18 +0000</pubDate>
		<guid>http://www.zeigen.com/shortcuts/2008/09/02/using-the-keyboard-with-google-chrome/#comment-12677</guid>
					<description>There are still a few "killer features" that firefox has above Chrome, and "find as you type" or "press / to find" is absolutely in that list for me.

I routinely navigate websites in Firefox by typing the text of the link, and then pressing enter to visit that link.  Not being able to do this means having to mouse down to the link and click.  Its a *huge* difference.</description>
		<content:encoded><![CDATA[<p>There are still a few &#8220;killer features&#8221; that firefox has above Chrome, and &#8220;find as you type&#8221; or &#8220;press / to find&#8221; is absolutely in that list for me.</p>
<p>I routinely navigate websites in Firefox by typing the text of the link, and then pressing enter to visit that link.  Not being able to do this means having to mouse down to the link and click.  Its a *huge* difference.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

