The search functionality has changed a lot with the latest update(s).
It looks like this is mostly the default CodeMirror 6 search UI (screenshot below) showing through after the migration, with the web editor's styles applied.
Some of the new functionality could be great to have, but the UI/UX could be improved.
In particular:
next, previous, all, replace, and replace all don't immediately read as buttons or actions.
- It's not obvious what
all does without trying it.
- The search options (
match case, regexp, by word) feel visually mixed in with the navigation controls.
- Search and replace actions don't feel clearly grouped.
- It's not immediately obvious what
regexp does. Besides, it's a probably too advanced for most p5.js Web Editor users.
I'd suggest reverting to a simpler search tool, maybe with optional replace and replace all function.
Matching options could be hidden but discoverable, like on OpenProcessing:

The search functionality has changed a lot with the latest update(s).
It looks like this is mostly the default CodeMirror 6 search UI (screenshot below) showing through after the migration, with the web editor's styles applied.
Some of the new functionality could be great to have, but the UI/UX could be improved.
In particular:
next,previous,all,replace, andreplace alldon't immediately read as buttons or actions.alldoes without trying it.match case,regexp,by word) feel visually mixed in with the navigation controls.regexpdoes. Besides, it's a probably too advanced for most p5.js Web Editor users.I'd suggest reverting to a simpler search tool, maybe with optional
replaceandreplace allfunction.Matching options could be hidden but discoverable, like on OpenProcessing: