Find bar doesn't search for certain words on some pages

[iG8R]

Find bar doesn't search for certain words on some pages

[hoothin]

You can double click the word frame in search input to change its behaviour.

[hoothin]

Thanks for report. It's a know issue, cause that's not a actual text node, but a css text.

I could load the text from github and highlight with a special code, but that's too ugly.
I will fix it after I have a good idea.

[hoothin]

Use regExp like /gpu/ /GPU/

[hoothin]

You can get only exact word if you input 'GPU', without 'NoGPU' 'YesGPU'

[iG8R]

Is it possible to add an option for the search panel to work the same way as the standard search panel in the browser, that is, not distinguishing between exact and compound words?

[hoothin]

I've updated to change content from str to /str/i automatically if your input text has no space.

[iG8R]

Thanks a lot.

[iG8R]

Another issue.

[iG8R]

Thanks a lot.

[hoothin]

I tried to add support for these situation. But there may be some additional bugs introduced.
I have tested it for a while now and welcome to give it a try.

[iG8R]

I apologize, in my previous post I didn't provide a link to the page where I took the screenshot.
https://github.com/Ixiko/AHK-libs-and-classes-collection/blob/master/classes/class_LoadPictureType.ahk

[hoothin]

Sorry I didn't count the scroll bar. You can try again.

[iG8R]

SearchJumper-FindBar-github-Video_2023-11-06_150939.webm

[hoothin]

Thanks for test & report, I didn't test switching with enter. It's fixed now.

[iG8R]

Thanks for work.

SearchJumper-FindBar-github-2-Video_2023-11-07_064924.webm

[iG8R]

In addition to the fact that the number of found words on the page changes, also note that every now and then SearchJumper misses, not exactly hitting the word with a crosshair, and sometimes, as it were, thinks halfway to the word.

[hoothin]

It's ordinary behaviour and as same as build-in find in page of firefox. Github is build with React and the dom will refresh when you scroll even though the page seems to be unchanged.

[iG8R]

OK, I got it.

[iG8R]

Is there a way to search by entire phrase rather than by words?

SearchJumper-FindBar-github-3-Video_2023-11-07_091518.webm

[hoothin]

$o or $c. Like $c+Github Copilot. You can see detail when you hover mouse on the input bar.
I think it's a nice idea to add whole phrase through "add words" window.

[iG8R]

Is it possible make it switchable, like the "Pin search text" and "Sidebar to locate" icons on the right?

[hoothin]

Sorry, but I don't like the switchable function of sth like "case sensitive", "whole phrase".
What about ignore delimiter when input phrase contains space?

[iG8R]

It’s just that with such a switch it would be convenient to switch between searching for the entire phrase and words individually. For example, the user initially enter github copilot and find the entire phrase; if they need to find individual words, click on the icon and a search for individual words occurs. If the entire phrase will be searched only if the delimiters contain spaces, then in order to search by words, you will need to manually remove the delimiters.
At the same time, separators can be used to indicate that when switching to word search mode, words will be searched individually or jointly.
For example, the phrase about+ignore delimiter+when input will initially be searched in its entirety, switching to a word search will search about ignore delimiter when input. If about +ignore delimiter +when input was entered, i.e. there will be a space before +, then switching to a word search will search for about ignore when delimiter input.

[iG8R]

Another page with a Find bar bug.
https://habr.com/ru/articles/548064/
search query: general.smoothScroll.durationToIntervalRatio

[hoothin]

It's not a bug, the words are in different elements. To join all the text node for finding cross element will cost much CPU time. So I ignore this situation.

[iG8R]

Then there is a situation where the user cannot be 100% sure when using the Findbar that all occurrences of what they are looking for have been found.

[iG8R]

For example, as it happened to me - I clicked on a link from Google and saw that SearchJumper did not highlight any words, then I manually called the Findbar and still without success. After that, I decided to just check with the standard Firefox search just in case, and it turned out that the necessary keywords were indeed on the page.

[iG8R]

Is it possible to make an option to make the functions
Highlight keywords on the search engine results page
Highlight keywords on the page opened by click on the search engine
work in the following way - when finishing a search in the search engine or opening the page from the search engine, so that the search words are not immediately highlighted, but only when the Findbar is brought up, then the words from the search query are already present in it and highlighted on the page?

[hoothin]

It's now supported.