Add null-safety to searchbar keyboard event handlers#36
Closed
Add null-safety to searchbar keyboard event handlers#36
Conversation
Merged
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Copilot
AI
changed the title
[WIP] Address feedback on redesign from review comments
Add null-safety to searchbar keyboard event handlers
Nov 7, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Keyboard shortcuts (Cmd+K to focus, Escape to blur) were calling methods on
searchbarwithout null-checking, causing runtime errors during SSR or before DOM initialization.Changes:
?.) tosearchbar.focus()andsearchbar.blur()callsgetElementById('searchbar')returnsnull✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.