The explorer steals input when any object is selected while working in the script editor.
It won’t capture input like hitting the delete key, but if you hit keys like Ctrl + D, it will duplicate what is currently selected.
I believe this strange input behavior is responsible for issues in my game without me realizing it.
Expected behavior
My inputs should be captured by the script editor and not the explorer.
I can reliably replicate this, particularly with any keybinds that use the Ctrl key. However, my issue in particular is with Ctrl + F, and, unlike in the video above, even after deselecting an object, the script editor does not react to Ctrl + F, unless I close a script (can be either the affected one or a different script, similar fix to [Temporary Fix] Select, Move, Scale, and Rotate permanently grayed out after opening scripts).
Notably, however, Ctrl + Shift + F will work regardless.
Having this weird issue as well
Staff redirected me here so I’ll leave this in here 
I was experiencing the same issue with CTRL + F to realize that it kept opening the find menu in the last script that’s open. Closing the last script and trying again keeps opening the find menu in the newest last script.
I believe some Studio update was pushed yesterday relating to user input, and these are just symptoms of it.
As of right now, it seems like this has been fixed in a patch, along with another bug relating to the script editor.