When you hit `t` on GitHub, it lets you search files inside the repo. It used to be that immediately after hitting `t`, the search box got focus so you could immediately type. Now you have to click in to the search box before you can type. I never noticed how much I cared about that feature until it stopped working 😆

7
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Aaron Patterson ✅

Also I have no idea how you write regression tests for features like that. Front end development seems hard 😅

2
1y

@tenderlove I _think_ it still works, but there’s a lag, so you have to hit ‘t’ and sneeze before you start typing

0
1y
José Albornoz

@tenderlove when I worked in the shopify admin we’d hit cases like this all the time. it’s just so hard to know exactly how people use things, despite how obvious it may seem. I remember a time we broke command+f because we made the list dynamic, merchants were NOT happy.

0
1y
Steven Harman

@tenderlove I got this too. And you also used to be able to hit ENTER to select the file, then `b` would switch to blame view. Now I swear I have to click the file with a mouse half the time, and the other half `b` lands in the on-page editor.

I suspect most of this is that there is lag that there didn’t used to be, so it feels broken when you’re typing fast.

0
1y
zellyn

@tenderlove wfm… ¯\_(ツ)_/¯

0
1y
Jabawack81

@tenderlove, like the poet said:
"But you only need the light when it's burning low
Only miss the sun when it starts to snow"

youtu.be/RBumgq5yVrA

;)

0
1y
Replies