[Bug]: Custom shortcuts not working in F11

Open
#2,913 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
desktop

Research direction

Reproduced by remapping "Next tab" to Tab and entering fullscreen (F11), after which the default Tab focus-navigation wins. Start by locating where Helium patches Chromium's keyboard accelerator/command routing for the browser window and how fullscreen changes which handler sees the key first; the reproduction with a fresh --user-data-dir profile is the fastest way to confirm the regression before touching code. Done means a user-assigned Tab binding still switches tabs while fullscreen, with default behavior restored when unassigned. Expect Chromium-scale build times and unfamiliar input-handling code, so this is not a quick first patch.

Written by the indexing model from the issue text.

Description

bug
Operating system

Windows

Version

Version 0.20.3.1 (Official Build, Chromium 156.0.8078.79) (64-bit)

Have you tested that this is not an upstream issue or an issue with your configuration?
  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
  • I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there
Description

Custom shortcuts not working in F11

Crash ID

/

How to Reproduce?

Assign "Next tab" shortcut to only tab instead of default ctrl tab. at first it will work as expected but going F11 (fullscreen) breaks user assigned shortcut and uses default (navigates between elements) instead.

Actual behavior

tab assigned to "Next tab" navigates between elements

Expected behavior

tab assigned to "Next tab" switches to next tab

Additional context

This issue isn't specific to Helium. I've experienced the same behavior in other browsers.

It's particularly relevant to the IO gaming community, where Tab is the commonly used shortcut for switching between browser tabs when multiboxing. It allows players to switch accounts without moving their fingers away from the main gaming keys.

Unlike alternatives such as Caps Lock, Tab doesn't interfere with normal typing or everyday browsing, which is why it's preferred. Some players may use different shortcuts, but Tab is by far the most common choice.

Since native browser shortcuts don't work reliably in fullscreen, many players are forced to use external tools like AutoHotkey.

Fixing this would be a significant quality of life improvement for the multiboxing community.

Dominant language
C++
Stars
21.2k
Forks
608
Avg merge
1d 4h
Merged PRs (30d)
27

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imputnet/helium

All issues in imputnet/helium

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.