-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typing two keys quickly in spotlight dialog closes the dialog #28493
Comments
I'm only a simple country web developer, but #28452 from last week changes the node that gets focused on various events in the spotlight dialog. |
This PR is not included in 1.11.86 as it was merged after the RC. @MidhunSureshR you were handling fixing this and believed it to be due to React 18 double-rendering which only affects development builds, this issue claims otherwise, can you confirm? |
I can repro on 1.11.86 but not on 1.11.85. |
From a git bisect, this is from #28336 |
move to 1.11.85. |
This is already fixed on develop and will be in the next release |
@t3chguy can you please tell us, approximately when the next release will be published? |
RC is today, Release next Tuesday |
Steps to reproduce
After upgrading to 1.11.86:
cmd-k
to open room quick searchI was able to confirm that downgrading to 1.11.85 fixes the issue.
Outcome
What did you expect?
I expect the search dialog to stay open and the input field shows the two keys I pressed.
What happened instead?
The dialog closes, and the message input is focused instead. This means that if I type, for example, three keys and press enter, the first two go into the room quick search and the third + enter go into the message box. I have been sending a lot of one-letter messages today.
2024-11-19-element-room-search-bug.mp4
Operating system
macOS
Application version
1.11.86
How did you install the app?
https://element.io/app-for-productivity, but that was a long time ago. This was just an in-app upgrade.
Homeserver
https://matrix.oxide.computer
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: