# CTRL + F when site is under extreme load

**URL:** <https://meta.discourse.org/t/ctrl-f-when-site-is-under-extreme-load/129517>\
**Category:** UX\
**Created:** [September 25, 2019, 9:59pm UTC](https://meta.discourse.org/t/ctrl-f-when-site-is-under-extreme-load/129517 "2019-09-25T21:59:03Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Heather\_Dudley](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heather_dudley/32/151925_2.png) [@Heather\_Dudley](https://meta.discourse.org/u/Heather_Dudley)\
**Post date:** [September 25, 2019, 9:59pm UTC](https://meta.discourse.org/t/ctrl-f-when-site-is-under-extreme-load/129517/1 "2019-09-25T21:59:03Z")

</div>

Okay, so, this is less a bug and more an unanticipated side effect of a [design choice](https://meta.discourse.org/t/discourse-taking-over-ctrl-f/16190). 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.

 ![image](https://global.discourse-cdn.com/meta/original/3X/2/2/2293b6fe6ded0261c88d728f781b2a93e7c7f19a.png)

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.

---

_[View the full topic](https://meta.discourse.org/t/ctrl-f-when-site-is-under-extreme-load/129517)._