Fixing Search (CTRL+F) Doesn't Auto-Update After Content Changes Dyna… #3368
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…mically
This PR fixes an issue where the search match counter does not update dynamically when content is modified. It also ensures that the counter resets correctly when switching between files in the CodeMirror editor.
Fixes #issue-#3367
Changes:
Add a change event listener to detect content modifications and restart the search
p5.js.Web.Editor.-.Google.Chrome.2025-03-06.17-32-56.mp4
Issue Addressed:
Search results do not auto-update when new content is added.
Search match counter does not reset when switching between files.
Includes improvements from another pending PR #3362 that fixes a similar issues-#3361 & #2125
npm run lint
)npm run test
)develop
branch.Fixes #123