philc
Vomnibar input doesn't receive focus on Chrome canary (v 132.0.6806.1)
Describe the bug
When opening the vomnibar by pressing e.g T it opens up, but it doesn't receive focus, nothing seems to respond to input until I click the bar. When opening a second time on the same tab it works though. I've checked that the permissions seems fine as suggested in similar issues.
Browser and Vimium version
Google Chrome | 132.0.6806.1 (Official Build) canary-dcheck (64-bit) (cohort: DCHECK-64)
Revision | 706e653689cd92665d3f28148e50d0d8cbc7d1d8-refs/branch-heads/6806@{#2}
OS | Windows 11 Version 23H2 (Build 22631.4391)
JavaScript | V8 13.2.82
User Agent | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36
Command Line | "C:\Users\marpe\AppData\Local\Google\Chrome SxS\Application\chrome.exe" --force-prefers-no-reduced-motion --restart --restart --flag-switches-begin --enable-experimental-web-platform-features --enable-smooth-scrolling --flag-switches-end
Vimium Version: 2.1.2
Edit
I thought it was working after manually focusing the vomnibar, but it fails sometimes when toggling the bar on and off by hitting eg T -> ESC -> T a couple of times afterwards too. No clue what's causing it to fail, seems pretty random.
i noticed the following. on a different machine there is no issue. it drives me crazy because i do not understand what causes vomnibar do not be focused anymore
I have the same problem on v134.0.6998.45 (arm64). In addition, find mode also not be focused directly. But I found that it works fine on chrome-extension://{extension package name}/page. It looks like the same issue that this PR sloved #3277
I also have this issue on one of my computers and would love some help investigating it. It affects the Vomnibar and find mode. On the browser where it occurs, it happens 100% of the time.
As a workaround, I've found I can hit tab once to get the focus into the Vimium UI components.
I have an M1 and an M2 MacBook.
M1 MacBook:
- Occurs in Chrome, no sync enabled, build 134.0.6998.45
- Does not occur in Brave, no sync enabled, running chromium 134.0.6998.45
- Does not occur in Chrome Beta, no sync enabled, running 135.0.7049.3
M2 MacBook:
- Does not occur in Chrome, sync enabled, build 134.0.6998.45
- Does not occur in Chrome canary, no sync enabled, 136.0.7059.0
I don't recall when this issue first began occurring, but I feel like it's been awhile (i.e. long before Chrome 134.0.6998.45)
Things I've tried on the M1 MacBook Chrome install:
- Remove Vimium, reinstall it
- Disable all other extensions
- New chrome profile with only Vimium installed
- Delete and reinstall the Chrome MacOS app (although the application settings persisted across the reinstall)
The last thing to try is to reset the browser's settings, but I haven't done that yet, and I'd be surprised if that's different than creating a fresh profile.
I agree that the issue sounds similar to #3277. What's so bizarre is that (for me) it doesn't reproduce across browsers on the same machine.
Any changes in the past weeks? It might be caused by different default status of Chromium flags on about:flags
Any changes in the past weeks? It might be caused by different default status of Chromium flags on
about:flags
I use the Chrome on M4 MacBook. Is there any flag that might affect this? By the way, I tried using vimium-c, but it had the same problem on Vomnibar (but search mode was working fine)
Had the same issue, disabling this flag solved it for me: enable-experimental-web-platform-features.
Edit: enable-experimental-web-platform-features enables a LOT of new behavior that is under development (being a blanket flag of sorts), so in case someone depends on a specific experimental feature that they're testing/want enabled, they can do so by figuring out the feature name and enabling it by passing it to the --enable-features flag. In my case, it is just the Web Preferences API.
This happens to Edge (on Arch Linux), too 138.0.3309.2 (Official build) dev (64-bit) . Can confirm disabling edge://flags/#enable-web-payments-experimental-features helps.
Had the same issue, disabling this flag solved it for me:
enable-experimental-web-platform-features.
good work! This solved all my problems.