Require /; don't grab all keypresses

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Hit 'r' (for Refresh) on a Google Reader page-- just one example

What is the expected output? What do you see instead?
The keystroke should go through to the page and refresh Reader. Instead, the 
extension takes the input and begins searching. Find-as-you-type should have an 
option to only work if it's specifically activated. I know I can put sites 
where this is an issue into the blacklist, but it would be easier to have a 
single option rather than maintaining the list.

What version of the product are you using? On what operating system?
I'm using Type-ahead-find version 0.3.6, on Google Chrome 10.0.648.151 for OS X.

Original issue reported on code.google.com by bbeyenhof on 24 Mar 2011 at 6:53

[GoogleCodeExporter]

Isn't "Options -> Direct search state -> disabled" what you are asking for?

Original comment by tokland on 24 Mar 2011 at 6:58

[GoogleCodeExporter]

Ah, I suppose it is. What that does isn't well-documented (but then again, I 
didn't try it, either).

Original comment by bbeyenhof on 24 Mar 2011 at 7:03

[GoogleCodeExporter]

No, it's not documented (well, there is the video: 
https://www.youtube.com/watch?v=1XsmQuMFbpY&feature=player_embedded)

but options are this way, look and test.

Google Reader probably won't work either well with the extension, I'd recommend 
just blacklisting it.

Original comment by tokland on 24 Mar 2011 at 7:06

• Changed state: Invalid

[GoogleCodeExporter]

It actually seems to work fine with that option disabled. I don't think I'd 
ever try to search on those pages, though... the JS would probably prevent me 
from doing so.

Original comment by bbeyenhof on 24 Mar 2011 at 7:11

[GoogleCodeExporter]

Issue 118 has been merged into this issue.

Original comment by tokland on 8 Apr 2011 at 7:48