You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This Issue tracker is only for reporting bugs and tracking code related issues.
Before posting, please make sure you check community.jitsi.org to see if the same or similar bugs have already been discussed. General questions, installation help, and feature requests can also be posted to community.jitsi.org.
Description
Chrome shortcut keys are disrupting my meetings
Current behavior
If I press F5, it makes me disconnect from the room and basically restarts JME (jitsi-meet-electron)
If I press F12, the developer tools shows up
Expected Behavior
JME should prevent F5 and F12 from reaching Chrome, but still allowed in scenarios like remote control, i.e. pass F5/F12 to remote
Possible Solution
Fix this behavior in code
Steps to reproduce
See current behavior
Environment details
JME running in Windows 10/11
The text was updated successfully, but these errors were encountered:
bilogic
changed the title
Chrome shortcuts have undesirable effects
Chrome shortcut keys have undesirable effects
Oct 13, 2024
This Issue tracker is only for reporting bugs and tracking code related issues.
Before posting, please make sure you check community.jitsi.org to see if the same or similar bugs have already been discussed. General questions, installation help, and feature requests can also be posted to community.jitsi.org.
Description
Chrome shortcut keys are disrupting my meetings
Current behavior
If I press F5, it makes me disconnect from the room and basically restarts JME (jitsi-meet-electron)
If I press F12, the developer tools shows up
Expected Behavior
JME should prevent F5 and F12 from reaching Chrome, but still allowed in scenarios like remote control, i.e. pass F5/F12 to remote
Possible Solution
Fix this behavior in code
Steps to reproduce
See current behavior
Environment details
JME running in Windows 10/11
The text was updated successfully, but these errors were encountered: