Solved Typing glitch

Parkinsond

Level 54
Thread author
Verified
Well-known
Dec 6, 2023
4,389
11,454
5,269
There is a glitch in Vivaldi browser for Windows (7.4.3684.55 (Stable channel) (64-bit), on Windows 11 24h2).
Cannot type some capital letters such as m and k using shift key; only by caps lock.
Edge is working fine.
 
This seems like a unique issue. Try reinstalling the browser or resetting your keyboard settings. If the problem persists, consider reporting this to the Vivaldi support team.
 
In that case, it might be a specific issue with Vivaldi. Try to update the browser to the latest version. If the problem persists, contact Vivaldi's support team for further assistance.
I am using the latest version of Vivaldi.
 
There is a glitch in Vivaldi browser for Windows (7.4.3684.55 (Stable channel) (64-bit), on Windows 11 24h2).
Cannot type some capital letters such as m and k using shift key; only by caps lock.
Edge is working fine.
There have been some reports of Vivaldi having issues with keyboard shortcuts or general input, though not always specifically tied to "M" and "K" with Shift in the past I would advise reporting the issue.

 
There have been some reports of Vivaldi having issues with keyboard shortcuts or general input, though not always specifically tied to "M" and "K" with Shift in the past I would advise reporting the issue.

This glitch has appeared just this morning, without changing settings or updating Vivaldi.
I will try to wait for the next updage (especially Vivaldi did not get the latest security fix) and see if it is going to be corrected.
 
Installed the latest snapshot (also to get the latest security fix as they are reluctant to release for the regular version) and glitch still exists.
 
Installed the latest snapshot (also to get the latest security fix as they are reluctant to release for the regular version) and glitch still exists.
If it worked in a guest profile and then failed in your main, it would point to corruption. But if it fails in a clean snapshot environment, it suggests a core Vivaldi issue.

Once (presumably) tested in a clean profile within the snapshot, your next action should be to formally report this bug to Vivaldi. They won't know about it unless users like you tell them.

Here's how to do it effectively.
Go to the Vivaldi Bug Report Page, the most direct link is usually:

Report a Bug | Vivaldi Browser
 

You may also like...