Ctrl+K search modal requires multiple close clicks and causes inconsistent theme behavior

[iamprasoon2006-cell]

Bug Description

When opening the search modal using the keyboard shortcut (Ctrl + K), the modal does not close properly with a single click on the close button.

Instead, multiple clicks are required and different UI states change on each click:

1. First click restores the scrollbar/background
2. Second click changes overlay appearance/brightness
3. Third click switches only the modal to light mode
4. Fourth click finally closes the modal completely

However, when opening the search modal normally by clicking the search bar manually, the issue does not occur.

Steps To Reproduce

1. Open the website
2. Press Ctrl + K
3. Click the close (X) button repeatedly
4. Observe inconsistent closing and theme behavior

Expected Behavior

• Modal should close completely with a single click
• Theme should remain synchronized across the page and modal
• Overlay/background state should reset correctly

Actual Behavior

• Multiple close clicks are required
• Theme partially updates
• Background and modal states become inconsistent

Possible Cause

Potential issue with:

• modal state cleanup
• keyboard shortcut event handling
• body scroll lock reset
• theme synchronization logic

[github-actions]

Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.

Don't raise PR unless assigned to you.

In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Resources which can help you know more about Github 👇🏻

1. End to End GitHub Beginner Playlist: GitHub Playlist.

2. Build your GitHub Profile: GitHub Profile Optimisation.

3. GitHub Handbook for dummies: GitHub Blog for Beginners.

[github-actions]

👤 Issue assigned to @iamprasoon2006-cell.

[sanjay-kv]

@iamprasoon2006-cell part of gssoc contribution?

[Adez017]

@iamprasoon2006-cell this is a good find , make sure , clearly define your approach and files changes with appropriate description

[iamprasoon2006-cell]

ok i will and yes this is a part of gssoc

…

On Thu, 14 May 2026 at 10:34 AM, aditya singh rathore < ***@***.***> wrote: *Adez017* left a comment (recodehive/recode-website#1511) <#1511 (comment)> @iamprasoon2006-cell <https://github.com/iamprasoon2006-cell> this is a good find , make sure , clearly define your approach and files changes with appropriate description — Reply to this email directly, view it on GitHub <#1511 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CA7PJCZ27HPKMAHWKSLMDTT42VHXJAVCNFSM6AAAAACY46U3FSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINBXG4YTQMJZGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>