New issue
Advanced search Search tips

Issue 723193 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 356887
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Can't create bookmark by dragging unsecure URL to bookmark bar (autosuggest box blocks)

Reported by abbarose...@gmail.com, May 17 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Visit any unsecure URL (http) that does not have the green "secure" padlock, and the www. stays displayed in the omnibox.  For example, http://www.nydailynews.com/
2. Click and drag the (i) info button toward the bookmark bar down quickly.
3. The omnibox's autosuggest box appears, blocking you from dropping it onto the bookmark bar.

What is the expected behavior?
You are normally able to drop the URL into the Bookmark Bar without issue.

Expected behavior seems to work in the following conditions:
Visiting a secure website, the padlock does not give the same issue.
Visiting a site that hides the www. in the beginning of its url does not always give the same issue.
A workaround is to hold on the (i) for approx 1.5 seconds until the site name is visible under your mouse.  Then the suggestion box stays hidden.

What went wrong?
When quickly dragging the info button on certain websites, the suggestion box appears and fails to check if a URL is being dragged.

In the attached picture you can see the bug.  The cursor is located by the shadowed "Breaking news".

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: stable
OS Version: OS X 10.12.4
Flash Version: 

This bug seems isolated to Max OS X and not Windows.  I'm leaning towards this having worked in the past, but I use my Windows machine more so I don't know.
 
chrome bug bookmark bar.png
749 KB View Download

Comment 1 by meh...@chromium.org, May 17 2017

Hi, can you reproduce it with latest Canary (https://www.google.com/chrome/browser/canary.html)? If not, then it has been fixed with  issue 356887  in Chrome 59. Thanks in advance.



Yes indeed seems to be fixed in 59.  Thanks.
Cc: sdy@chromium.org
ccing the dev @sdy from 356887 to merge the fix to M58 if it is a valid candidate to merge

Thanks,

Comment 4 by sdy@chromium.org, May 19 2017

Mergedinto: 356887
Status: Duplicate (was: Unconfirmed)
I'm not sure if we'll be able to merge this to M58, but you can follow along in the other issue :).

Sign in to add a comment