Searching File Via Ctrl+F Is Very Slow

[cavepappy]

I'm not sure what the proper course of action for something like this is (or if it's really even an issue for most), but the issue is as follows:

I have a ~5mb file that when searched via Ctrl+F becomes unresponsive for the first few characters because it's trying to immediately give me results for each character as I type it. I don't need to know where all of the 'A's are in the file, but it's delaying my search because it's going to try to find them all anyway.

Example:
Open XmlNotepad > Load File > Move to XSL Output Tab
Press Ctrl+F > Begin Typing "Example"
Program hangs on the first 'E' until it's searched the entire document for 'E', then I need to type to the next letter.
It does get quicker with each letter since it has the added context of only looking for strings that begin with an 'E', but it does inhibit workflows when having to wait.

I'm sorry if this isn't the proper place to put something like this, but thank you all the same.

[lovettchris]

This find feature is implemented by the "WebView" actually, which can either be the default WebViewBrowser component or the new WebView2 component (you can set this in the View/Options, scroll to the bottom and select WebView2). If WebView2 is available you will see it mentioned in the status bar when you click the Transform button as follows:

The web browser is not supposed to hang when you fill in the Find string. The act of typing and finding should be completely decoupled and operate asynchronously. Perhaps you specific HTML output is triggering some bug in the browser. Do you see the same problem when you open the transform output in a standalone Edge browser?

[cavepappy]

Ah okay, thank you for that! I was able to get it changed it over to the WebView option, but it does seem to take offense to the data I'm trying to load haha.

I was able to get the search to let me enter an entire word before it tries to look through the document so I think that works well enough for me (though the window itself does become rather laggy, but that may be due to the file not having an XLST transform - unfortunately one wasn't provided to me - so it's relying on the default, and in Edge it's acting pretty much exactly the same way.

I did try opening the output in Edge, and it's acting pretty much exactly the same way. It's fine if you'd like to close this since changing the web browser version seemed to do the trick. Thanks!