Okay, so, this is less a bug and more an unanticipated side effect of a design choice. However, I wanted to log this as a potential issue.
When a site is overloaded, Search may be disabled. If this happens, CTRL + F disables a user’s ability to find a post within a thread they’ve loaded, even if they’ve already loaded a longer thread.
I realize that pressing CTRL + F a second time will default to browser search.
However, as a future consideration, consider disabling the CTRL + F capture if the site is under extreme load. It effectively does nothing and the double-tap of F is not intuitive as a solution.