processing / processing/p5.js-web-editor
Ctrl+F glitchy when switching between files
Open
Nobody has claimed this yet.
Area:Editor
Bug
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 1.7k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 8
Description
-
p5.js version: 1.5.0
-
Web browser and version: Chrome, Firefox, and Edge, most recent
-
Operating System: Windows 11
- Go to this link and go to sketch.js
- Ctrl+F and type "test". Notice there are 4 instances of "test"
- Switch to new.js and press the "next" (down arrow) on the Ctrl+F bar
- Notice it always says 0/4 (it should say 1/2 and 2/2 I assume)
- Type another "test" in new.js and hit the down arrow
- Notice it says there are now 7 instances of "test" (it should say 3 I assume)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked sketch and reproduce the Ctrl+F behavior in sketch.js and new.js using the issue's steps. Start by tracing how the find bar handles a file switch, then verify that match counts and navigation are recalculated for the active file; done means each file reports and navigates through only its own matches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100