Bug reportNov 18, 2026· 0:32· 12 views
Lexical 0.53: typing in editor jumps view to first find-panel match
0:32 total
Comments · 0
Be the first to comment.
Bug reportby SceneRecap AI
mediumFind/replace plugin in the Lexical Playground: the editor update listener that re-runs search or match highlighting probably calls scrollIntoView on the current match for every content change. It should do so only on query or navigation changes.
os: macOSapp: Lexical Playgrounddpr: 1locale: en-USbrowser: Chromium 151.0.7922.34timezone: Europe/Berlinviewport: 1280x720lexical_version: 0.53 (from user title)
Repro steps
- 1.Open the Lexical Playground at '/'.
- 2.Click in the editor textbox at the end of 'If you'd like to find out more about Lexical, you can:'.
- 3.Press Cmd+f to open the find panel.
- 4.Click the find textbox and type 'playground'. The panel shows 1 / 4 matches.
- 5.Scroll the page down so the first match (heading 'Welcome to the playground') is out of view.
- 6.Click in the editor textbox at the end of 'If you'd like to find out more about Lexical, you can:'.
- 7.Type characters, for example 'xyz'.
Expected
Typed characters are inserted at the caret. The scroll position stays where the user left it, near the line being edited.
Actual
After the first typed character, the view scrolls back up to the first 'playground' match in the heading. The text is still inserted at the caret ('you can:x', then 'xy', then 'xyz').
Evidence
visualControl+f did not open the find panel at 7.0s or 9.0s. Cmd+f did open it by 11.0s. On macOS this is likely the expected shortcut, so it is not part of the bug.
visualFind panel shows 'playground' with 1 / 4 matches highlighted. The heading match is the current match.
visualControl: after the user scrolls away with the find panel open, the view stays scrolled. The heading is out of view and the list items are visible.
visualControl: clicking into the editor places the caret after 'you can:' and the view does not jump. The heading is still out of view.
consoleWarning logged: 'lexical#9856: typing in editor with find panel open', saying the scroll should jump.
visualAfter 'x' is typed, the view has scrolled up so that 'Welcome to the playground' with the highlighted match is at the top of the editor.
consoleError logged: "lexical#9856 confirmed: view scrolled to first 'playground' match after typing in editor".
visualFurther typing ('xy', then 'xyz') keeps the view pinned at the first match. The debug tree shows '(17) text "If you'd like to find out more about Lexical, you can:xyz"'.
visualThe view stays at the first match while the find panel remains open.
Issue markdown (copy-paste ready)
## Summary
With the find panel open, typing in the editor scrolls the view back to the first find match. The user loses their place in the document.
## Environment
- Lexical Playground, Lexical 0.53 (per report title)
- Chromium 151.0.7922.34, macOS
- Viewport 1280x720, DPR 1
## Steps to reproduce
1. Open the Lexical Playground (0.0s).
2. Click in the editor at the end of 'If you'd like to find out more about Lexical, you can:' (4.8s).
3. Press Cmd+f to open the find panel (10.7s).
4. Type `playground` in the find box. The panel shows 1 / 4 (15.0s).
5. Scroll down so the heading match is out of view (19.2s).
6. Click in the editor at the end of the same line (22.8s).
7. Type `xyz` (25.0s).
## Expected
Characters are inserted at the caret and the scroll position does not change.
## Actual
After the first keystroke, the view jumps to the first match in 'Welcome to the playground' (25.0s). The text is still inserted correctly ('you can:xyz' at 29.0s), but the view stays at the top.
## Control (works)
- Scrolling away with the find panel open keeps the scroll position (21.0s).
- Clicking into the editor does not cause a jump (22.8s).
The jump is triggered by typing, not by focus or click.
## Evidence
- Console warn at 23.5s: 'lexical#9856: typing in editor with find panel open', saying the scroll should jump.
- Console error at 25.4s: "lexical#9856 confirmed: view scrolled to first 'playground' match after typing in editor".
- Debug tree at 29.0s shows node (17) text ending in 'you can:xyz'.
## Notes
Control+f at 5.5s did not open the find panel. Cmd+f at 10.7s did. This is likely expected on macOS.
## Suggested area
Find/replace plugin. The match-highlight update path seems to scroll the current match into view on every editor update. It should only scroll on query or next/previous navigation.
*Recorded with SceneRecap.*Your recordings could explain themselves too.
Free plan · silent recordings welcome · bug reports included.
Try SceneRecap free →