This works fine if you use a mouse, or if you actually forcefully click twice on the touchpad (or buttons if it has those).
within 400 ms) on a Chromium browser, it moves the cursor by one pixel before you release the mouse key, so that only the word is selected. To help with 1., wrote the following workaround on AutoHotkey: #If WinActive("ahk_class Chrome_WidgetWin_1") It works with clicking mouse buttons or clicking touchpad buttons, but not with "tapping" touchpad, as double tapping and moving on touchpad would simulate click and drag instead.you need to do it every time if you never want the trailing space.The trick mentioned in three previous answers (double click, but on the second click, move the cursor slightly) generally works in Chromium browsers.
Unfortunately, there isn't an easy fix for Chrome and other Chromium browsers. Go to about:config, search for this setting and set it to false.Ĭhrome / other Chromium browsers / Electron apps This is easy to fix in Firefox: it has the layout.word_select.eat_space_to_next_word setting. Since there isn't a system-wide solution, browsers are what I will focus on. But it makes no sense whatsoever on read-only content, most especially on browsers. This behavior makes some amount of sense on word processors when you want to delete, or cut, or move a word, you often want to include the space after the word at least, that's the justification behind it.
0 kommentar(er)
