I like to keep a word list of any new and interesting words I come across day-to-day. Today I was curious how many entries were in my list and went to search the YAML file on GitHub.

To my delight, I discover that GitHub has hijacked the native Cmd-F browser search. To top it off, seems the maximum number of matches GitHub’s search returns is limited to 200.

I’ll excuse a search function that at least reports > 200 results matched, but there is no indication in the UI that this is the case. Even if you navigate to the 200th result and can see additional matches in the viewport, GitHub’s UI steadfastly refuses their existence.

Here’s what it looks like on macOS with Safari version 26.2:

A quickly-disappearing hint on the GitHub search model reported that hitting Cmd-F again brings up the native browser search. I gave that a whirl, but it still wasn’t finding all matches. I thought I’d inspect the page source for the text elements to see what’s going on under the hood:

… and hit a render error. This is another lovely bug I’ve been running into when the viewport changes quickly in Safari. I can see a data-target="react-app.reactRoot" attribute lurking in the dark: maybe I shouldn’t besmirch the React-ification of GitHub’s UI, though. After all, at least the raw file searches instantly in the browser:

Luckily, Firefox retains its native search experience:

Maybe I’m getting this all wrong, and I’d love to be corrected. But it sure feels like GitHub’s UI&UX has become increasingly slow and unfriendly as of late. In any case, I’ve reported this bug and I’ll update if I hear anything back.