- Ya
- 2 Septemba 2026, 05:09 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 92321ca
The search at the top of a chat window marked every occurrence of the query and then scrolled to exactly one of them — the newest — with nothing to say how many others there were and no way to reach them. A member searching a conversation for an invoice number could see the word highlighted three screens up and had no control that would take them to it. It now behaves as the find bar it already resembles: a counter reading "3/12", an arrow toward the older messages and one toward the newer, Enter and Shift+Enter for the same two moves, and the hit being stood on drawn in solid amber against the yellow of the rest. Landing on the newest hit is unchanged, so a member who only ever typed a query and read the result sees what they always did, now with the count beside it. Two decisions underneath are worth spelling out. Hits are counted per occurrence rather than per message, and against the words the bubbles actually draw — the translation where a message has one, which the old search did not do. The counter and the marks are two views of one list produced by a single scan (findOccurrences, shared with the highlighter), so "12" is always exactly the number of marks on screen. Two scans that disagreed even slightly would leave arrows landing on nothing. paged: messages arrive at the bottom while a search is open and older pages land at the as "result 3" would quietly become a different message. It follows that "1 of 3" at the oldest hit does not mean there is nothing older — only that nothing older has been fetched — so stepping back from there asks for the previous page and lands on what it brings, the same move the list already makes when somebody scrolls to the top. It wraps to the newest only once the server has run out, or after five pages have arrived carrying no hits at all: one press of an arrow must not be able to walk a years-long conversation back to its first message. The toolbar's resting geometry is untouched. The counter and arrows appear with the query rather than with the field, because they cost about sixty pixels and an empty search box has nothing to count.