Skip to content

Toggled Modifiers Affecting Keybinds & TAB switching from keybinds #6808

Open

Description

@cqb13

Describe the bug

This is 2 issues relating to setting keybinds.

  1. When trying to set a keybind to the TAB key, instead of setting the keybind, focus is switched to the next input. This also appears to leave the module window in a broken state, the settings cant be closed with ESC until focus is removed from the input box that was switched to and a non tab keybind is set or ESC isn't pressed again to end the keybind setting process.
  • I assume this happens because the widget screen switches on tab based on press, but keybinds are set on release. maybe adding some lock to stop the tab switching while entering a keybind could fix this
Screenshot 2026-11-15 at 12 05 04 AM Screenshot 2026-11-15 at 12 05 46 AM
  1. When caps lock or num lock are toggled on (the key is not pressed down), the key is treated as held. So turning on caps lock or num lock then pressing a letter will result in a keybind of Caps Lock + A instead of A. I assume expected behavior would be for this to happen only if capslock is actually held down. This also leads to situation where you can create keybinds like Caplock + Capslock.
Screenshot 2026-11-15 at 12 14 37 AM

read down from here for more info: https://discord.com/channels/689197705683140636/689197706169942135/1571383296389292042

Steps to reproduce

For the tabs: starting setting a keybind and press TAB, instead of setting the keybind to the tab key, focus will be switched. (This will only happen if the module has an input box other an the keybind. works as expected in Packet Logger because no inputs, but not in Notifier because it switches to notification delay input)

For the Capslock/Num Lock issue: Toggle caps lock or num lock then press a key. Instead of setting the keybind the key, it will set the keybind with the caps lock/num lock modifier despite them not being held down.

Meteor Version

26.3-19

Minecraft Version

26.3

Operating System

macOS

Before submitting a bug report

  • This bug wasn't already reported (I have searched bug reports on GitHub).

  • This is a valid bug (I am able to reproduce this on the latest dev build).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions