New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 666988 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Aug 27
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Pressing EV decoration starts URL drag when it should not

Project Member Reported by shrike@chromium.org, Nov 19 2016

Issue description

With the new EV pressed state, pressing the EV causes it to get darker, but if you press for "too long" you'll start dragging a URL. Now that the pressed state changes the background color, it's weird to get a draggable URL at this point. Pressing the EV should not start a drag session.

 
Another issue related to this behavior: clicking the outer area of the security chip selects the URL instead of opening page info. Maybe the click target is too small so that the click event is triggered on the omnibox?
Click.gif
1.5 MB View Download
Cc: shrike@chromium.org
Just the EV decoration? Should it also be the security verbose?
The security verbose also. These are now essentially buttons that are separate from the URL field.

Are we removing the drag behavior entirely? I kind of view it like the file icon proxy in document-based applications -- it's very handy for transferring URLs between different apps when Chrome isn't foreground.
No, we don't want to remove that functionality completely because it is useful, as you note. I guess in the past on non-EV sites we had a favicon and URL - to me it makes sense to be able to drag the favicon out to get the URL. Now, with the Secure / (i) states (and EV), it feels strange / disjoint to start dragging a favicon and site title from what are effectively buttons that are visually separated and distinct from the URL.

At least clicking the omnibox selects the URL, and a click and slight delay before dragging will get you the draggable URL, but it's not as nice as how it worked before. 
The favicon was never in the omnibox -- it was a page icon rather than the (i). I'm not sure it's that weird for these items to be draggable, since Chrome has several other draggable buttons (bookmarks, extensions).

The URL does auto-select on click, but it's not draggable when Chrome is not foreground.
> Chrome has several other draggable buttons (bookmarks, extensions)

That is true, but you actually drag those buttons. In this case you are not dragging the security indicator / EV chip - you start to drag and get something entirely different. That's why I find it weird. But I would like to give it more thought before disabling it.

Comment 8 by shrike@chromium.org, Dec 10 2016

I talked to pinkerton@ about this. He agrees it's confusing, and that it's a useful power feature. I think in the future the omnibox URL area will change in its presentation of URLs and it will be more straightforward to drag URLs from there (vs. now where you basically have to click twice). So my/our thought is to leave the current confusing behavior as it is for now, with the expectation that it will be forced into something better in the future.

Status: WontFix (was: Assigned)
Labels: -Pri-2 Pri-1
Status: Assigned (was: WontFix)
We should still improve the click behavior as soon as possible. Currently, it's very difficult to view page info because clicking the security chip triggers the URL drag too quickly when using a mouse (it's slightly better when using a trackpad). See attachment.
Click.gif
743 KB View Download
In addition, the URL text selection is inconsistent: sometimes dragging the security chip selects the URL, other times it doesn't. See attachment. 
Drag Select URL.gif
297 KB View Download
That's a good point. I can add a longer delay to start the drag. WDYT?
Sounds good, thanks! Yes, I think that could work.
Could you also look into the issue described in #11?
Seems like #11 depends on clicking the lock vs. clicking the "Secure" title. In theory these are both part of the same control but I believe they are two separate bits of UI?
They are two different issues. I'm going to file a new bug for it
New bug:  Issue 681910 
Status: WontFix (was: Assigned)

Sign in to add a comment