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
This page is nearly 1500 pages long in print-preview. (I looked just to get that figure.) When I try to search this page, the browser totally locks up, is marked as "not responding," and turns pale. I'm not really sure how long it gets stuck like this because I get impatient and kill the process.
If I disable FindBar, the regular built-in search works without issue.
I acknowledge this is probably my own fault for trying to use an enhanced search with fancy visuals, but we can also look at this as an opportunity to figure out optimization for extremely long pages.
The text was updated successfully, but these errors were encountered:
Yeah, it has a little trouble handling huge pages like that. Improving that is already on my to-do list, although I don't know when I'll be able to do it.
BTW it's probably not the page being huge, but having a lot of matches, as in the thousands. Usually the add-on handles well a few matches even in long pages like that.
I would like to add my vote to this. On a page such as this one, which isn't even particularly long, the native FF search for, say, g takes place instantly, while FBT, even with 'Highlight all matches by default', 'Show highlights grid in the scrollbar' and 'Show sights on current hit / all hits' disabled - which should mean it is doing nothing more than the native search - brings the browser to a halt.
What's worse, if I type greasemonkey right away, FBT should directly search for the whole word instead of starting its search with g which is gonna lock up the browser.
Here's a fun test case for you: http://faculty.washington.edu/rturner1/AustraLearn_GBR.mht
This page is nearly 1500 pages long in print-preview. (I looked just to get that figure.) When I try to search this page, the browser totally locks up, is marked as "not responding," and turns pale. I'm not really sure how long it gets stuck like this because I get impatient and kill the process.
If I disable FindBar, the regular built-in search works without issue.
I acknowledge this is probably my own fault for trying to use an enhanced search with fancy visuals, but we can also look at this as an opportunity to figure out optimization for extremely long pages.
The text was updated successfully, but these errors were encountered: