<?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: /: Find on page in Firefox</title>
	<link>http://www.zeigen.com/shortcuts/2007/08/13/find-firefox/</link>
	<description>Windows keystrokes and keyboard tricks and tips that you can use to save time</description>
	<pubDate>Wed, 08 Feb 2012 18:31:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Charlie Arehart</title>
		<link>http://www.zeigen.com/shortcuts/2007/08/13/find-firefox/#comment-5270</link>
		<pubDate>Sun, 13 Jan 2008 00:17:06 +0000</pubDate>
		<guid>http://www.zeigen.com/shortcuts/2007/08/13/find-firefox/#comment-5270</guid>
					<description>Thanks as always for the tips.

About this use of / in FF, this is interesting. I notice that this is different from Ctrl-F in a couple of ways. First, it doesn't let you do a next/prev (as the other find does). Instead, once it finds, it stops. If you hit enter, it doesn't repeat the find (as in Ctrl-F). Also, hitting / again doesn't repeat the find, and unlike Ctrl-F, it doesn't show in the find field the value last used, so you have to type it again. Finally, curiously, even if you do type the text again, it doesn't find the "next" value. It finds the same value just found (if any). It's as if it doesn't advance the cursor beyond the found text. 

None of these are annoyances, just differences that may have advantages if you understand them. For instance, since  it "just stops" and can't be repeated, then if what is found is text in a hyperlink, the find with / actually selects the hyperlink, so you can just hit enter to execute the link. Using Ctrl-F, you'd have to hit escape first (to remove the option for doing next/prev). 

Naturally, another difference is that the / naturally won't work while typing in a text field, so you have to use Ctrl-F in that case.</description>
		<content:encoded><![CDATA[<p>Thanks as always for the tips.</p>
<p>About this use of / in FF, this is interesting. I notice that this is different from Ctrl-F in a couple of ways. First, it doesn&#8217;t let you do a next/prev (as the other find does). Instead, once it finds, it stops. If you hit enter, it doesn&#8217;t repeat the find (as in Ctrl-F). Also, hitting / again doesn&#8217;t repeat the find, and unlike Ctrl-F, it doesn&#8217;t show in the find field the value last used, so you have to type it again. Finally, curiously, even if you do type the text again, it doesn&#8217;t find the &#8220;next&#8221; value. It finds the same value just found (if any). It&#8217;s as if it doesn&#8217;t advance the cursor beyond the found text. </p>
<p>None of these are annoyances, just differences that may have advantages if you understand them. For instance, since  it &#8220;just stops&#8221; and can&#8217;t be repeated, then if what is found is text in a hyperlink, the find with / actually selects the hyperlink, so you can just hit enter to execute the link. Using Ctrl-F, you&#8217;d have to hit escape first (to remove the option for doing next/prev). </p>
<p>Naturally, another difference is that the / naturally won&#8217;t work while typing in a text field, so you have to use Ctrl-F in that case.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

