Skip to content
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

Closed
joshtriplett opened this issue Mar 18, 2021 · 10 comments

Comments

@joshtriplett
Copy link

(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:

  1. Start a Jitsi Meet meeting, with multiple participants.
  2. Make sure you're in the default view with equally sized tiles for each participant
  3. Open a new tab
  4. Hit ctrl-w to close the new tab, and make sure you release ctrl before w
  5. Notice that the view has changed to show one large tile for one participant

Expected behavior:

The view should not change.

Actual behavior:

The view changes when the 'w' key is released.

Server information:

  • Jitsi Meet version: Latest on meet.jit.si

Client information:

  • Browser / app version: Firefox 86
  • Operating System: Linux
@ls-1N
Copy link

ls-1N commented Mar 25, 2021

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.

@stale
Copy link

stale bot commented Jun 23, 2021

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.

@stale stale bot added the wontfix Issue won't be fixed label Jun 23, 2021
@ls-1N
Copy link

ls-1N commented Jun 25, 2021

@stalebot I still care about this.

@stale stale bot removed the wontfix Issue won't be fixed label Jun 25, 2021
@stale
Copy link

stale bot commented Jan 9, 2022

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.

@stale stale bot added the wontfix Issue won't be fixed label Jan 9, 2022
@joshtriplett
Copy link
Author

Bug still exists.

@stale stale bot removed the wontfix Issue won't be fixed label Jan 10, 2022
@stale
Copy link

stale bot commented Apr 17, 2022

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.

@stale stale bot added the wontfix Issue won't be fixed label Apr 17, 2022
@joshtriplett
Copy link
Author

This issue still exists.

@stale stale bot removed the wontfix Issue won't be fixed label Apr 17, 2022
@mbrodala
Copy link

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 Ctrl+D and focus switches to my browser. (Here Jitsi sees D and triggers the screen share dialog.)

@mbrodala
Copy link

Maybe fixed with #13520?

@saghul
Copy link
Member

saghul commented Jul 17, 2023

Yes indeed!

@saghul saghul closed this as completed Jul 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants