You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like when I select a tab and go to it, the text I was searching for should be 'found': highlighted and within the current frame. Maybe connect to the regular 'find' feature?
The text was updated successfully, but these errors were encountered:
Actually, if QFind's working correctly, it should jump to the 'next' occurrence of the search text after activating the target tab.
Each time you click the same result in the result list, QFind should (ahem) jump to (and highlight) the next occurrence in the tab with wrap-around. It invokes the native browser window.find function, which is different from Chrome's find box.
Though I want to do it, overriding/hooking the built-in Chrome find box is impossible according to all reasonable web searches on the subject. (ref1, ref2 -- I'm still looking for a clean way to extend the built-in ctrl-f behavior)
I just pushed a new version, 0.0.0.10, that has a 'Popout' window feature that allows you to click on results repeatedly in a persistent window, thus allowing a crude "find next" feature. More refinements to come.
Seems like when I select a tab and go to it, the text I was searching for should be 'found': highlighted and within the current frame. Maybe connect to the regular 'find' feature?
The text was updated successfully, but these errors were encountered: