Issue metadata
Sign in to add a comment
|
Un-elision during double-click word selection is un-intutitve |
||||||||||||||||||||||
Issue descriptionChrome Version: 69.0.3464.2 (Official Build) dev (64-bit) What steps will reproduce the problem? (1) Go to a site with a [Secure] or [Not secure] marker in the URL bar (2) Try to select a sub-string of the URL. What is the expected result? URL stays in one place, so my mouse is pointing at the same character as before I started selecting. I could imagine a UI where the scheme appears to sit on top of and occlude the verbose-chip instead of the verbose-chip disappearing, but anything that doesn't move the previously-visible part of the URL would be an improvement. What happens instead? If I click the URL before selecting, the whole thing gets highlighted. I have to click again to put down a single cursor, at which point the URL moves, and I have to move my mouse to make a selection starting at the character I first clicked. If I don't click the URL before selecting, the selection works as expected, but the URL jumps as soon as I finish selecting, so I have to re-focus to see that I selected the right text.
,
Jul 23
Mac triage: assigning to jyasskin@ for followup per #1.
,
Aug 1
Since the whole URL *moves*, preserving the location of the click can only be a partial solution. When I do a click and drag, since the URL has shifted to the right, the drag location is farther left than I actually clicked.
,
Aug 1
Another example, interacting with view-source. The second click lands in a seemingly random position (between the slashes, between the second pair of w's).
,
Aug 2
[omnibox triage] jleedev@, we've made some improvements in this behavior recently. Can you please let me know what Chrome version those videos are coming from. Assigning to tommycli@, who's dealt with this complexity before.
,
Aug 2
I don't remember what version that was yesterday, but the behavior is the same in Canary 70.0.3510.0 today. To elaborate, here's what I'm seeing: Old behavior: URL stays put until I edit some text. This is predictable for all permutations of clicking, double clicking, dragging, arrow keys, etc. New behavior: URL jumps if it is already focused and I click, select text, press an arrow key, double click, start dragging, etc. I do see that when this happens, the *first* click location is translated to the same relative position after the text has moved, but subsequent clicks are not. So here's what's happening, step by step: 1. Visit https://www.google.com. - Omnibox shows [google.com]. 2. Click once anywhere in the omnibox. - Entire text is selected, view is unchanged 3. Double click on the word [google]. - Text changes to [https://www.google.com]. - [https] is selected.
,
Aug 2
In the video in c#3, it looks like you are double-click-dragging. In other words, it looks like you are doing: Mousedown Mouseup Mousedown Drag Is that accurate?
,
Aug 3
Yes (it selects words).
,
Aug 3
Okay great. So it sounds like normal dragging is working alright - but double-click word-selection is unintuitive. Is that correct?
,
Aug 3
Yes, normal dragging is working. Un-elision during double-click-and-drag feels weird, and I would hope that it's a straightforward fix to keep the elided state during this gesture. If the URL is to jump around, doing so when the mouse button is released ought to be the least surprising, if the user is not about to immediately press the button again.
,
Aug 3
Awesome - thanks for the feedback. I will investigate if there's a way to accomplish this.
,
Sep 11
This behavior is very annoying when attempting to select and edit or copy a portion of a URL. The recent changes to elide "https://www" from the prefix of a URL are especially annoying, because the URL jumps around significantly underneath the mouse when doing double-click selection. Could this new UX please be rethought? This is being noticed by other colleagues, too: https://twitter.com/FlohOfWoe/status/1039534856001208320 Upgrading to P2 regression.
,
Oct 19
Issue 896120 has been merged into this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by k...@chromium.org
, Jun 21 2018