Text selection per word using Ctrl + Shift + Arrow left/right key is broken.
Reported by
b...@big-endian.nl,
Sep 14
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/69.0.3497.81 Chrome/69.0.3497.81 Safari/537.36 Example URL: https://www.google.com/ Steps to reproduce the problem: 1. Type a few words into the google search field on https://www.google.com/ 2. While the keyboard cursor is located at the end of the text, press Ctrl + Shift + Left Arrow. What is the expected behavior? Since Ctrl + Arrow left/right moves the keyboard cursor left or right per word. And Shift selects text when moving the keyboard cursor. The expected behavior is to select per word. What went wrong? Unsure. It seems to have stopped working since the new big Chromium UI update. I also have Chrome (not Chromium) version 69.0.3497.92 installed. Chrome is not affected. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? Yes 68 Does this work in other browsers? N/A Chrome version: 69.0.3497.81 Channel: stable OS Version: KDE Neon 5.12.6 LTS Flash Version: textarea and input[type=text] elements in this very form at https://chromiumbugs.appspot.com/ also seem to be affected. While the same textarea and input[type=text] elements on https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_textarea aren't affected. I've tested the same websites on Firefox, and on Firefox all works as expected. Which makes me conclude the problem is not in the website itself.
,
Sep 18
I got Chromium through the `apt` package manager (`sudo apt-get install chromium-browser`). I just noticed that opening the developer console using Ctrl + Shift + I or Ctrl + Shift + C also does not work anymore. Any combination with Ctrl + Shift actually (like Ctrl + Shift + Delete for clearing browser history). Switching to the Chrome (69.0.3497.100) browser which I have installed alongside Chromium, all still works.
,
Sep 19
Version 69.0.3497.81 (Official Build) (64-bit) The issue concern only Linux version, while those hotkeys works fine in Windows version. It works in the address bar, but not in others edit controls. Just open www.google.com and try it in the search line. Also as: Ctrl+Shift+Up/Down - Select line Ctrl+Shift+Home/End - Select till the begin of text or it's end One of previous version was loaded from the official site https://www.google.com/chrome/ and then was self updated several times up to latest 69 version. BTW, now I have a headache how to revert an old version, because there is no a link on the main page to get archived versions for Linux. And I can't use new version due to broken hotkeys for selection by words, as it one of most used combination for me when entering text in the browser.
,
Sep 19
,
Sep 20
Reporter@ Thanks for the issue. Tested this issue on Ubuntu 17.10 on the reported version 69.0.3497.81 and the latest Stable 69.0.3497.100 and unable to reproduce the issue by following the below steps. 1. Launched Chrome and navigated to https://www.google.com/. 2. typed 'Wikipedia' in the search bar and hit Ctrl+Shift+left arrow key. 3. can observe that the text is selected as expected. 4. Also hit Ctrl+Shift+I and could observe that the Devtools is opened as expected. Attached is the screen cast for reference. Request you to check and confirm if anything is missed from our end in triaging the issue. Also request you to update chrome to the latest Stable(69.0.3497.100), retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations. Thanks..
,
Sep 20
Thank you for your suggestion to check extensions. I found if turning off "Nimbus Screenshot & Screen Video Recorder" https://chrome.google.com/webstore/detail/nimbus-screenshot-screen/bpconcjcammlapcogcnnelfmaeghhagj The issue is goes away. Then I had to delete and install a new version of the extension, because the "update" button did not works for it. Problem was with version 8.6.7, and all works fine with current 8.6.9 extension version.
,
Sep 26
Mark WontFix since this is caused by Chrome extension, per #c6 and #c1. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Sep 17