foxy / chrome-type-ahead Goto Github PK

This might be an intentional security measure, but it would be nice if this worked on other extension pages.

This extension does not appear to find anything that is within embeded content.

For example, try using the extension to find the word "mage" on the following page: http://ggoatgaming.com/tierlist/

"mage" does not appear on the page itself, but within the embedded spreadsheet, it appears 6 times.

What steps will reproduce the problem?
1. Browse to several pages in one tab to create a history
2. Press backspace to "go back" in history

Instead of going back in the history, nothing happens.

*

Let me also add that a timeout would be nice, say after 30 seconds the search 
string length is set to "0".

Original issue reported on code.google.com by [email protected] on 16 Dec 2009 at 9:42

When an element that isn't an input element BUT has contenteditable, type-ahead-find receives the input when that element should receive it.

Discovered when trying to implement https://yaireo.github.io/tagify/ on a site

Loading https://www.w3.org/TR/xmlschema-0/ with the search setting saved as 'links only', typing 'xml' will highlight text that isn't a hyperlink.

In Firefox, double-byte characters such as Chinese, Japanese and Korean characters can be input into the Quick Find edit box if the corresponding IME is selected for that edit box.

But there is no edit box, or any way to select IME's, for Type-ahead-find, which makes finding double-byte characters impossible.

The icon of this extension is not visible in Vivaldi browser toolbar, nor it appears among the “hidden extensions”. The only way to reach its options in Vivaldi is by opening the Extensions page vivaldi://extensions/.

I make a Google Sites homepage with all the links I commonly visit for work. chrome-type-ahead used to work on this page, but it seems to have broken recently.

If I type in an HTML element with the contentdeditable attribute set, type-ahead-find ist triggered and the browser searches for the text instead of editing the content of the HTML element. If contentdeditable is set, type-ahead-find should treat the element like an input or textarea instead. HTML snippet looks like this, for example: <h1 contenteditable>foo</h1>

The code seems to check for the contentdeditable attribute already, so I don't get why it doesn't work. I don't really know Javascript, so sadly I'm not able to contribute a patch.

Thanks for this reat plugin!

On this page, using the extension to search for "unincorporated" on my Chrome on Mac causes the page to scroll off to the left of the window and I can't scroll it back. The only way I am able to get it back is to click the "English" link at the top. Chrome's built-in find doesn't have this problem.

P.S. Thanks for making this extension!

The extension seems to want to find text in the usual way when Google Earth. But it's impossible to type in a location in the search box of Google Earth. When I deactivate the extension, it goes back to normal enabling typing in the search bar.