-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 1.49.14
-
Component/s: None
-
Environment:OS: mac os
node.js / npm versions:
-
None
-
Developer Tools
Problem Statement/Rationale
Find in Page (Ctrl+F / Cmd+F) only matches text that is currently rendered in the viewport. The documents list is virtualized, so only the rows scrolled into view exist in the DOM, and Electron's native find-in-page has nothing else to search. The same applies to collapsed nested fields, which also aren't in the DOM.
The problem isn't just the limitation — it's that it fails silently. Find reports 0 results (or a partial match count that changes as you scroll), so the reasonable conclusion is that the value doesn't exist in the collection. That makes Ctrl+F unreliable for its most common use: checking whether a value appears anywhere in the returned documents.
Request: either extend find to cover all loaded documents in the current result set, or surface clearly that the search only covers what's visible. A "find within results" control scoped to the query output would be even better.
No logs attached — this is a purely client-side rendering/search behavior with nothing written to the log file.
Steps to Reproduce
- Connect to any deployment and open a collection with a few hundred documents (or run a query returning enough rows to require scrolling).
- Note a distinctive string in a document well below the fold — e.g. one near the bottom of the loaded batch.
- Scroll back to the top of the list.
- Press Ctrl+F (Cmd+F on macOS) and search for that string.
Expected Results
Find locates the string and scrolls to the matching document, as find-in-page does in a browser. Failing that, Find indicates that its scope is limited to the visible rows so the empty result isn't misread as "not present."
Actual Results
No match is reported. The string is only found once the containing document has been manually scrolled into view. Match counts vary depending on scroll position, and there's no indication the search scope is partial.
Additional Notes
- Also reproduces in JSON view and with collapsed nested objects/arrays.
- Compass <version, from Compass → About>, <OS and version>
- Node.js / npm: N/A — packaged desktop app