UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Steps to reproduce the problem:
1. Have a node.js debugging session
2. Select Search (CTRL+SHIFT+F)
3. Write e.g. "console" into the search text field.

What is the expected behavior?
I'd expect that "Debugger.searchInContent" command from the inspector protocol is called for loaded scripts.

What went wrong?
Scripts content is requested instead, via Debugger.getScriptSource command.

Did this work before? N/A 

Chrome version: Chromium	69.0.3497.81 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit) Revision	032b3ca19e9af20182f9bd03deefc0faf4695558-refs/branch-heads/3497@{#869}  Channel: stable
OS Version: Ubuntu 16.04
Flash Version: Shockwave Flash 31.0 r0

What is the searchInContent command for in the inspector protocol, if it's actually not used for searching?

Tested also with chrome-devtools-frontend.appspot.com where DevTools (Chrome 71) are available.