Enter key not working on gmail search bar when using a non-US keyboard layout (chrome)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Some week ago I started to have issue with Gmail, in Chrome.
When I write something in the search bar it autocomplete, but then I hit "ENTER" and nothing happens.
I know, this doesn't sound like an Ubuntu issue, but I don't give up on me, I'll show you why I think it is.
I thought this was an issue with Gmail website, but after a couple of weeks without any change I decided to investigate.
If I change the layout of my keyboard from "US, with italian letters" to "US" the Enter key works without any problem.
When I change it back to "US, with italian letters" it stop working again.
ENTER key works everywhere else, even inside Gmail website, which makes the issue even weirder.
I'm not alone in this as you can read here:
https:/
and here (on Firefox apparently):
https:/
Apparently many people experiencing this with whatsapp webchat too, I don't use it so I don't know.
I've tried with Firefox too: the Gmail search apparently works, but when you login pressing enter after writing the password has no effect, you need to click the button (or change keyboard layout)
I've no idea what is causing this, it's probably a mixture of website issue and Linux / Gnome / Ubuntu issue: but I know none of my coworker with Mac and Windows are experiencing any issue on any browser, so I think the problem is mainly an issue with Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 4.15.0-44-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 5 15:50:08 2019
InstallationDate: Installed on 2018-10-20 (107 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
thank you for your bug report, but it's not a bug in the settings UI component (gnome- control- center) , if other softwares work fine then it's probably a but in chrome and firefox (or a component they use which GNOME doesn't use or not the same way), reassigning to firefox since chrome isn't free software nor on launchpad