New issue
Advanced search Search tips

Issue 903095 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
swarnasree.mukkala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Support GTK keyboard themes (emacs keybindings)

Reported by weiwu.zh...@alphawallet.com, Nov 8 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/70.0.3538.77 Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce the problem:
1. Enable emacs key-binding:

$ gsettings set org.gnome.desktop.interface gtk-key-theme "Emacs"
2. Enable it again by configuration file:

 $ cat .config/gtk-3.0/settings.ini 
[Settings]
gtk-key-theme-name = Emacs

3. Test every app (e.g. Firefox) with Ctrl+A in a text input area. the effect is the cursor moves to the beginning of the line.

4. Run Chromium and type Ctrl+A in an input area (e.g. address bar).

What is the expected behavior?
 The cursor should stop at the beginning of the line.

What went wrong?
 You get the "SELECT ALL" effect.

Did this work before? N/A 

Chrome version: 70.0.3538.77  Channel: stable
OS Version: Ubuntu 8.04
Flash Version: 

- Reboot doesn't help.
- This issue happened 10 years ago: https://bugs.chromium.org/p/chromium/issues/detail?id=11480

Comment 1 Deleted

Comment 2 by weiwu.zh...@alphawallet.com, Nov 8 

Ubuntu version is 18.04, not 8.04. Sorry

Comment 3 by vamshi.kommuri@chromium.org, Nov 8

Labels: Needs-Triage-M70

Comment 4 by swarnasree.mukkala@chromium.org, Nov 9

Cc: swarnasree.mukkala@chromium.org
Labels: Triaged-ET Needs-Feedback
Tried testing the issue on reported chrome version #70.0.3538.77using Ubuntu 17.10 by following below steps.

Steps:
=====
1.Launched chrome.
2.Opened terminal and tried enabling Emacs keybinding by -"gsettings set org.gnome.desktop.interface gtk-key-theme "Emacs"".
3.To enable it again by configuring the file  executed-"cat .config/gtk-3.0/settings.ini "
4.Observed that "gtk-theme-name=Breeze".

Attached screenshot for reference.
@reporter: Could you please review attached screenshot and let us know if anything is being missed here and also request you to confirm if the issue is specific to Ubuntu 18.04.
Thanks.!
903095.png
44.1 KB View Download

Comment 5 by weiwu.zh...@alphawallet.com, Nov 9 

I was not being clear enough. The command you should try is


$ cat > ~/.config/gtk-3.0/settings.ini

followed by typing the content of the file.

To verify the file is correctly edited you would use 

$ cat ~/.config/gtk-3.0/settings.ini
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 9

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by mpear...@chromium.org, Nov 13

Components: -UI UI>Input>KeyboardShortcuts
Labels: -Pri-2 Pri-3
Status: Untriaged (was: Unconfirmed)

Comment 8 by ligim...@chromium.org, Nov 16

Labels: Hotlist-DesktopUIChecked Hotlist-DesktopUIValid
*** UI Mass Triage *** 

Seems like a valid bug, adding appropriate label.

Comment 9 by mpear...@chromium.org, Dec 18

Description: Show this description

Comment 10 by mpear...@chromium.org, Dec 18

Labels: Hotlist-Polish Hotlist-GoodFirstBug
Status: Available (was: Untriaged)
This actually should be pretty easy to fix.  Code contributions are warmly invited!

Comment 11 by weiwu.zh...@alphawallet.com, Dec 18 

For those who seek workaround, you can use the latest Brave browser (version 0.57.18 based on Chromium: 71.0.3578.80) which is based on a rather new version of Chromium but strangely doesn't have this issue.
►

Sign in to add a comment