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

Issue 794189 link

Starred by 3 users
Status: Duplicate
Merged: issue 840387
Owner: ----
Closed: May 2018
Cc:
amin...@google.com
█ cmasso@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Command clicking on a bookmark folder with 15 items doesn't actually open them

Project Member Reported by ijpedowitz@google.com, Dec 12 2017 
Chrome Version: 65.0.3292.0 (Official Build) canary (64-bit)
OS: Mac OS X 10.12.6

What steps will reproduce the problem?
(1)  Have a bookmark folder with 15 items in my tab bar
(2)  Command click on the folder
(3)  Tap on Yes for "Are you sure you want to open 15 tabs?" prompt

What is the expected result?  All items in the folder are opened, one per tab

What happens instead?  Nothing happens, but the folder remains highlighted.  If I right click and tap on Open All, the items open.  This seems broken to the specific Commands+Click flow.  This bug has been present for a few weeks now.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

Comment 1 by dtapu...@chromium.org, Dec 19 2017

Components: UI>Browser>Bookmarks

Comment 2 by ijpedowitz@google.com, Jan 4 2018 

Friendly ping?  Still 100% reproducible for me, and really impacts my workflow for opening all my finances.

Comment 3 by ijpedowitz@google.com, Jan 17 2018

Cc: cmasso@google.com amin...@google.com
Ping?  Can this bug get some love?

Comment 4 by amineer@chromium.org, Jan 17 2018

Labels: OS-Mac
Adding OS-Mac to see if the Mac triage rotation picks this up.

Comment 5 by erikc...@chromium.org, Jan 30 2018

Labels: Hotlist-CocoaBrowser
Status: Available (was: Untriaged)
Sorry, I'm going to give the response that I hate receiving myself. 

We're working on a replacement: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/O2moeF9Jn-U

Which will not be ready for a while. In the meantime, there's no one available to work on this issue.

Comment 6 by ijpedowitz@google.com, Jan 30 2018 

What is the ETA on the replacement?  This regressed somewhat recently, so it would be really appreciated if whatever broke it could be reverted.  Perhaps you could have someone bisect to find the breaking change?

This really does impact my normal workflow :-(

Comment 7 Deleted

Comment 8 by ijpedowitz@google.com, May 9 2018 

Shouldn't  issue 840387  have been duped here since this issue was filed in December, but  issue 840387  filed two days ago?

Comment 9 by lgrey@chromium.org, May 9 2018 

 Issue 840387  had more context/discussion, I just happened to run into this while searching for that one to update it. Sorry this didn't get addressed at the time.
►

Sign in to add a comment