Connect with us

NEWS

Chrome’s Match Case Button Arrives Fifteen Years Late

Chrome Canary is testing Match Case on Find in Page, a toggle Google declined in 2011, plus new arrows that skip matches already on screen.

Published

on

Chrome Canary is testing a Match Case toggle on Find in Page, a control Google declined to put in the UI in 2011.

The same test bar adds Previous outside view and Next outside view arrows, which skip every hit already on screen. Researcher Leopeva64 posted both controls from desktop Canary on October 28 and October 30, 2026. Google has not named a date for Chrome stable.

An Aa Toggle Lands on Chrome’s Find Bar

Chrome’s built-in search still treats capitals and lowercase as the same thing. Search for Web and the bar lights up web and WEB. Search for an acronym and you walk through every casual use of the same letters.

Canary’s new control is an Aa button on that bar. With Match Case off, the default, a hunt for T on the sample line “This is some text with a link.” still returns 1/4 hits. Turn Aa on and Blink reruns the query with match_case set, and the count drops to 1/1, only the capital T in This. The button sits between the usual next control and the close icon, drawn as a blue pill when it is pressed.

Leopeva64, who watches Chrome Canary builds, put the toggle next to Edge’s existing control. “Just like in Edge, this button lets you restrict search results to match your exact uppercase and lowercase letters,” he wrote.

The clip is from a desktop Canary find bar, not from Chrome stable and not from Chrome on a phone. Ordinary Previous and Next arrows still step through one match at a time. Aa only changes which strings count as a match.

Google Refused That Control in 2011

The wait is fifteen years, counted from the day Google’s UI leads said no. On April 6, 2011, a Google engineer wrote on a Chromium find-in-page bug that the extra options would be nice to have, and that the team was not willing to add them to the UI at that time. The underlying ticket, opened February 2, 2011, asked whether Chrome needed case-sensitive search of the kind Firefox already showed, and whether find should respect diacritics.

The engine did not stay empty. Blink’s find pipeline already accepted a case flag, and Chrome’s own bar kept forcing that flag off. In July 2018 a comment on the public ticket noted that case-sensitive search was already implemented in Blink. A later write-up of the same gap said the engine work landed in 2018, including a whole-word option, and that Chrome still had no switch for either one.

On February 1, 2017, a separate request asked Chromium to case-sensitive options for the find dialog. That filing stayed open while Edge drew a Match Case control and while commenters said they opened Firefox when they needed to grep a long spec. On October 23, 2026, screenshots of the Aa toggle were attached to the old find-in-page bug, with the search rerun as soon as the button is pressed.

THE FIND-IN-PAGE WAIT

  1. February 2, 2011: Chromium issue 40518349 is filed on find-in-page case and diacritics.
  2. April 6, 2011: A Google engineer writes that UI leads will not add those options to the bar.
  3. February 1, 2017: Issue 41298878 asks again for a case-sensitive find control.
  4. 2018: Blink already supports match_case; Chrome’s find bar still keeps it off.
  5. October 23, 2026: Before-and-after shots of an Aa Match Case toggle land on the old bug.
  6. October 30, 2026: Leopeva64 posts the Match Case button in desktop Chrome Canary.

The 2011 no was a UI choice, not a missing search library. Canary is finally showing a switch the renderer could already honor.

What Firefox and Edge Already Offer

Firefox has shipped a Match Case control on its Find bar for decades, and users can pin that mode on through a hidden setting. Edge already shows a Match Case button, which is the comparison Leopeva64 used when he posted the Chrome Canary build. Chrome stable still has neither that toggle nor a skip-visible control, so the Aa button is catch-up even as the new arrows are not.

Firefox also offers Highlight All and Whole Words on the same bar, plus a quick find that opens with the slash key. Edge’s find options have included Match Case, whole word, and diacritics. Chrome’s Canary bar, in the builds Leopeva64 posted, adds case matching and the skip arrows and does not show a whole-word switch.

People who live in Firefox can set Firefox Match Case as the default by changing accessibility.typeaheadfind.casesensitive. A value of 0 keeps the button off, 1 leaves Match Case on, and 2 uses an automatic mode that follows whether you typed a capital. Chrome’s new Aa button, in the Canary shots, starts off and has to be pressed per search.

FIND CONTROLS BY BROWSER

Browser Match Case Skip visible hits Whole word
Chrome stable No No No
Chrome Canary (test) Yes (Aa) Yes No
Microsoft Edge Yes No Yes
Firefox Yes No Yes

DevTools in Chromium browsers already search with case matching if you open Inspect and hunt the DOM. That path is a debugger, not Ctrl+F, and it is how a lot of Chrome users have faked a case filter without installing anything.

Off-Screen Matches Get Their Own Arrows

The second Canary change is the one other desktop browsers still lack. Standard next and previous walk every highlighted string, including the ten copies sitting in the paragraph you can already see. Previous outside view and Next outside view ignore that cluster and land on the first match above or below the current viewport.

Chromium engineer S Ganesh wired that skip into Find in Page under bug 570465258, a feature request filed October 6, 2026, that asked for a way to jump to the next match outside the viewport. The code review, CL 8619536, reached the bug on October 27, 2026, 21 days after the request. It names logs, tables, and navigation headers as the pages where stepping through every visible hit is slow. If every match is already on screen, the skip falls back to the adjacent hit.

When searching pages with dense or repeated text (such as logs, tables, or navigation headers), cycling through every visible match inside the current viewport with Find in Page is slow and repetitive.

S Ganesh, Chromium engineer, CL 8619536

Leopeva64 posted the arrows two days after that review note, on October 28, 2026. “These buttons let you jump directly to the next match below your current view or jump back to the previous match above your current view, completely skipping results already visible on screen,” he wrote, with a Canary recording of the jump.

HOW THE SKIP IS WIRED

  • Previous and Next: Step one match at a time, including hits already in view.
  • Outside view arrows: Skip the current screen and open the first match above or below it.
  • Alt+Enter: Keyboard skip forward; Shift+Alt+Enter skips backward.
  • Ctrl+Enter: Still activates a matched link, so it was left alone.

The skip is the useful half of this Canary drop for anyone who reads API docs, build logs, or a news page that repeats one proper noun in a sidebar. Case matching filters the set. The extra arrows move through that set without clicking the same sentence to death.

Whole Word and Regex Remain Extension Territory

Match Case in the official bar will cut the need for a third-party overlay when the only want is exact capitals. It will not replace the rest of those add-ons. Blink already documents a match_case flag in Blink’s find options, and that struct still defaults the flag to false. Chrome never exposed whole-word matching on the same bar, even though older notes said the engine could do that too.

The Chrome Web Store still sells that missing layer. SuperSearch, billed as VS Code find for Chrome, lists regex, whole word, Match Case, find-in-selection, and iframe search, and it shows 20 users. Find Lite, updated August 5, 2025, lists case-sensitive search, whole word, regex, and a gutter of hits; the store page shows 343 users and a 2.8 score from 10 ratings. Find Lite’s own copy still says Chrome’s built-in search cannot even tell case apart. Other listings over the years, including FindR, have appeared and vanished.

Those user counts are small because most people never need regex on a web page. The people who do, developers and anyone grepping a spec, have been the ones bouncing to Firefox or to DevTools. Native Aa removes one reason to install a overlay. It does not give Chrome a whole-word toggle, a regex box, or a diacritics switch of the kind Edge has already shown.

Why Match Case Is Still Stuck in Canary

Both tools are in desktop Chrome Canary only. The skip is gated by kFindInPageSkipViewport, which lands disabled by default in the code. Google has not said when either control will reach Chrome stable, and Canary UI is allowed to change or disappear before a milestone.

The find bar is a strange place for Chrome to move slowly. It is the shortcut people actually hit, on long pages, while the browser’s public energy sits on Gemini side panels and other Canary extras. One of those extras already lets a user copy a tab group’s links in one click. The find-bar work is smaller, older, and aimed at a habit that never needed a model.

WHAT WE KNOW

  • Where it runs: Desktop Chrome Canary only, as posted on October 28 and October 30, 2026.
  • Match Case: An Aa toggle, off by default, reruns the current query with match_case on.
  • Skip visible: Previous outside view and Next outside view, plus Alt+Enter and Shift+Alt+Enter.

WHAT IS UNCONFIRMED

  • Stable timing: Google has not named a Chrome stable milestone for either control.
  • Whole word: No Canary shot shows a whole-word button next to Aa.
  • Android and iOS: The posted builds are desktop; there is no mobile find-bar demo.

Until a stable build ships the Aa button, Ctrl+F in Chrome still folds WEB into web. The skip arrows, if they survive Canary, will be the first find control in this round that Firefox and Edge cannot copy from an old playbook.

Harry is the editor of IAQABA, an independent publication he owns and runs. A decade in journalism, beginning as a reporter and now as the editor of his own titles, has left him with a clear test for what deserves a story: it has to change what a reader knows or decides, and it has to rest on something he can point to. That rules out recycled press releases, forecasts with no data behind them and rumours that no document supports. It leaves room for a great deal, and the site covers news, business, science and technology alongside sports, entertainment and lifestyle, with travel, auto and gaming given the same standard rather than lighter treatment. Sources are primary wherever possible: the regulator's filing, the company's own statement, the transcript, the dataset, or the product on Harry's desk. Figures are checked before they are published and rechecked if a reader questions them. Mistakes are corrected under a published policy. Readers across the world can reach him directly at support@iaqaba.com.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending