Search Changelog Block for React

Edit RELEASES at the top of the file, newest first: each has a version, a date as an ISO day, a title, a summary and a kind. The count line, the empty state and the placeholder read from the array. To search more fields, add them to the string in matches.

The title, the sentence, the version and the kind's name, ignoring case and accents, matching the typed text anywhere in them, so "token" finds a release whose sentence mentions tokens and "v2.8" finds two releases. Matched words are marked in the title and the sentence in a low-strength tint of your foreground colour.

While the block is on the page, / focuses the field, unless you are already typing in a field or an editor. Escape inside the field clears it and keeps focus there. The field announces its shortcut (aria-keyshortcuts), and the key hint is hidden on a phone, where there is no keyboard. The count under the field is a polite status ("3 of 8 releases"), so a screen reader hears the result of each change.

No. The results and an unseen copy of all eight releases share one grid cell, so the cell is as tall as the full list whatever you type. With no match the empty state names the typed words and offers a Clear search button, which also returns focus to the field. A layout check will report the rows changing as the list narrows; that is the search working.

Yes in look and behaviour. Clear and Clear search are plain buttons with an onClick.

The field is full width and the key hint is hidden; each row stacks the version above the title. In a right-to-left layout the field, the rows and the count mirror, and versions, dates and counts keep their reading order.