UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Open any file in the Dev Tools Source File Editor
2. Identify a line that has more than 1001 characters (minified JS/CSS is a good place to look. Try xkcd.com/1361)
3. Identify a word that occurs more than once, but only after the first 1001 characters of the line (try 'bool')
4. Place your cursor on that line, and SLOWLY start typing that word.
5. Notice that Find *selects* the word once it finds it, moving the edit cursor beyond the word. Thus, as you continue to type the rest of the word, "Find" locates future instance of the word instead of the first instance you were on.

What is the expected behavior?
Find should match the first word that it comes across as the user is typing it, and not jump to other instances of the word.

What went wrong?
Find jumps to other instances of the word as the user types it (when it finds a word after the first 1001 characters). Ths is because  after 1001 characters, Find starts selecting the words (instead of highlighting), and thus moves the edit cursor after the end of the word.

There might actually be two bugs here (or not):
  1. Find selects matches after 1001 characters (leading to jumping to other instances of the word)
  2. Selecting a word moves the cursor to the end of the word

Did this work before? No 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: OS X 10.11.4
Flash Version: