Don't crash when a custom search panel doesn't have a field named 'search'.
Make sure replacements are announced to screen readers.
It is now possible to disable backslash escapes in search queries with the literal option.
Make the wholeWords option to highlightSelectionMatches default to false, as intended.
Make sure search matches are highlighted when scrolling new content into view.
The selection-matching extension now accepts a wholeWords option that makes it only highlight matches that span a whole word. Add SearchQuery.getCursor
The SearchQuery class now has a getCursor method that allows external code to create a cursor for the query.
Fix a bug that caused the search panel to start open when configuring a state with the search() extension.
searchConfig is deprecated in favor of search (but will exist until next major release).
The new search function is now used to enable and configure the search extension.
Make selectNextOccurrence scroll the newly selected range into view.
The search option matchCase was renamed to caseSensitive (the old name will continue to work until the next breaking release).
openSearchPanel will now update the search query to the current selection even if the panel was already open.
Client code can now pass a custom search panel creation function in the search configuration.
The getSearchQuery function and setSearchQuery effect can now be used to inspect or change the current search query.
The search panel will no longer show the replace interface when the editor is read-only.
Add userEvent annotations to search and replace transactions.
Make sure the editor handles keys bound to findNext/findPrevious even when there are no matches, to avoid the browser's search interrupting users.
Add a Symbol.iterator property to the cursor types, so that they can be used with for/of.
selectNextOccurrence will now only select partial words if the current main selection hold a partial word.
Explicitly set the button's type to prevent the browser from submitting forms wrapped around the editor.
Make highlightSelectionMatches not produce overlapping decorations, since those tend to just get unreadable.
Make sure any existing search text is selected when opening the search panel. Add search config option to not match case when search panel is opened (#4)
The searchConfig function now takes a matchCase option that controls whether the search panel starts in case-sensitive mode.
Make sure to prevent the native Mod-d behavior so that the editor doesn't lose focus after selecting past the last occurrence.
Initialize the search query to the current selection, when there is one, when opening the search dialog.
Add a searchConfig function, supporting an option to put the search panel at the top of the editor.
Fix a bug where the first search command in a new editor wouldn't properly open the panel.
New command selectNextOccurrence that selects the next occurrence of the selected word (bound to Mod-d in the search keymap).
The search interface and cursor will no longer include overlapping matches (aligning with what all other editors are doing).
The package now exports a RegExpCursor which is a search cursor that matches regular expression patterns.
The search/replace interface now allows the user to use regular expressions.
The SearchCursor class now has a nextOverlapping method that includes matches that start inside the previous match.
Basic backslash escapes (\n, \r, \t, and \) are now accepted in string search patterns in the UI.
Fix an issue where entering an invalid input in the goto-line dialog would submit a form and reload the page.
Update dependencies to 0.18.
The package now also exports a CommonJS module.
First numbered release.