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
‘w’ key to change view triggers when hitting ctrl-w to close adjacent tab #8837
Comments
There might be valid reasons why it is implemented the way it is - I don't know - but for reference, the code that you want removed/changed seems to be here. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@stalebot I still care about this. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bug still exists. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue still exists. |
One possible solution would be taking modifiers into account, see #7933 Personally I always accidentally trigger the screen share dialog when closing a terminal via |
Maybe fixed with #13520? |
Yes indeed! |
(Previously discussed at https://community.jitsi.org/t/w-key-to-change-view-triggers-when-hitting-ctrl-w-to-close-adjacent-tab/95836 .)
Description:
If I open another tab from a Jitsi conversation (such as by following a link from the chat), and then hit ctrl-w to close the new tab and return to the Jitsi tab, having ‘w’ still momentarily pressed (because I haven’t released it yet, and I happened to release the ctrl before the w) causes Jitsi to receive a keyup event without a corresponding keydown event or keypress event. Jitsi seems to react to the keyup event for ‘w’ by changing the view (from showing everyone to showing one person), which then means I have to switch the view back.
Could Jitsi switch to using keypress rather than keyup, to avoid this? Browsers are careful to not send a keypress event in this scenario.
Steps to reproduce:
Expected behavior:
The view should not change.
Actual behavior:
The view changes when the 'w' key is released.
Server information:
Client information:
The text was updated successfully, but these errors were encountered: