Summary: I have many bookmark folders in my bookmarks bar, each folder containing many bookmarks. Often I want to open 2 or 3 bookmarks (perhaps from the same folder, perhaps from different folders) at a time in separate tabs. I've done this up until now with a combination of mouse-clicking the bookmark to load a bookmark in an existing tab and pressing command-t to create a new blank tab to load the next bookmark. I can do this in rapid succession. This worked fine in Safari 2, but Safari 3 has the annoying behavior of opening an extra blank tab for each new tab I create. In other words, if I attempt to create three tabs, Safari 3 creates six tabs -- three tabs containing my loaded bookmarks, and three unwanted blank tabs. Steps to Reproduce: (1) Show bookmarks menu. (2) In Preferences/General, set new windows to open with empty page. (3) Create bookmark folder containing three bookmarks, and put the folder in the bookmarks bar. IMPORTANT: the following steps need to be done in rapid succession. (4) Using the mouse, click on the bookmark folder in the bookmarks bar, and click on the first bookmark to open it. (5) Press command-t to create a new tab. (6) Click on the bookmark folder in the bookmarks bar, and click on the second bookmark to open it. (7) Press command-t to create a new tab. (8) Click on the bookmark folder in the bookmarks bar, and click on the third bookmark to open it. Expected Results: I end up with three tabs, loaded with my three bookmarks. Actual Results: I end up with six tabs: Untitled, bookmark#1, Untitled, bookmark#2, Untitled, bookmark#3 Regression: This bug occurs with Mac OS X 10.5.1 and Mac OS X 10.4.11. It did not occur with Safari 2 and Mac OS X 10.4.10. This is definitely a regression introduced in Safari 3 and Mac OS X 10.4.11. I've reproduced it on an a MacBook Pro Intel Core 2 Duo and an iMac Intel Core Duo. Notes: This bug is REALLY annoying. It messes up the page-opening workflow that I've used without problems for YEARS. I have discovered that I can open a bookmark from a folder in a new tab by command-clicking the bookmark, but this does not work reliably at all at high speed: sometimes the bookmark opens in the same tab, and sometimes every bookmark in the folder opens in a separate tab, which is unacceptable. Using command-t is the only reliable way to make sure the single selected bookmark opens in a separate tab. 17-Dec-2007: Please know that our engineers have not been able to reproduce this reported behavior. It ends up with three tabs (three bookmarks) as you describe in the Description. Should you continue to encounter this issue, please provide any information that would assist engineering in reproducing this reported behavior. 17-Dec-2007 Jeff Johnson: Please re-open this bug. The problem has been reproduced on 3 different machines and 5 different Mac OS X installations. I explained the problem to my boss, and he was able to reproduce it immediately on his Mac Pro running 10.5.1. I would be happy to provide more information, but I'm not sure how to make the steps to reproduce clearer. The opening of web pages in tabs doesn't need to be done in super-fast succession; just medium speed. You probably don't want to use a super-fast internet connection; usually the pages are still in the process of loading as I'm creating new tabs. This is a real, reproducible issue. We're not hallucinating. The problem is not even intermittent: it happens all the time. It happens at home, at work, in the coffee shop. Please do not close this bug. If necessary, I'll try to take a video of the process on one computer using the iSight on my other computer. Keep trying to reproduce. 17-Dec-2007 Jeff Johnson: Additional note for steps to reproduce: In Preferences, Tabs, make sure that "Select tabs and windows as they are created" is checked. 17-Dec-2007 Jeff Johnson: Actually, it turns out that the preference for "Select tabs and windows as they are created" doesn't matter. The problem is reproducible in either case. However, if you uncheck "Command-click opens a link in a new tab", then an ever stranger behavior occurs: sometimes my bookmarks open in a new *window* rather than in a new tab, despite the fact that I'm using command-t and not command-n (and despite the fact that I'm not command-clicking anything). In my steps to reproduce above, I had "Command-click opens a link in a new tab" checked. 17-Dec-2007 Jeff Johnson: See also http://forums.macrumors.com/showpost.php?p=4044937&postcount=2 for a similar report. 18-Dec-2007 Jeff Johnson: I talked via iChat to a friend in Finland, and he was able to reproduce the problem on his MacBook Pro running OS X 10.5.1. Another colleague is also able to reproduce it on a Mac Pro running 10.5.1. That's five different machines -- indeed, every machine we've tested. 21-Dec-2007: Engineering has provided the following feedback and requested additional information for this issue: We can reproduce this issue, but we believe this is behaving correctly. The change between Safari 2 and Safari 3 is that we now honor the command key in combination with a mouse click on a menu item from a bookmark folder in the bookmarks bar. So, in the given steps, if you go so quickly that the mouse-up from the click slightly overlaps the command-key-down from the next command-T, the click will count as a command-click, and the bookmark will be opened in a new tab in addition to a new empty tab being created. You may use fewer steps in Safari 3 to achieve the same result -- hold down the Command key when clicking menu items in bookmark folders, to open them in new tabs. You will not have to make new empty tabs at all. Please attach your findings to this bug report. 21-Dec-2007 Jeff Johnson: I am aware of the new command-click behavior. As I said above in the problem description, "I have discovered that I can open a bookmark from a folder in a new tab by command-clicking the bookmark, but this does not work reliably at all at high speed: sometimes the bookmark opens in the same tab, and sometimes every bookmark in the folder opens in a separate tab, which is unacceptable. Using command-t is the only reliable way to make sure the single selected bookmark opens in a separate tab." I believe that this is not a case of mouse-click and keypress overlap. I have done some additional testing, and there seems to be a window of time -- less than a second, but still human discernible -- after the completion of the mouse click (i.e., after mouse up) during which a new command keypress is interpreted by Safari as a command-click. I believe that this is a bug. Pressing the command key after the mouse-click is over should not be interpreted as a command-click. I think we can simplify the steps to reproduce: (1) Make sure the command key is not pressed. (2) Mouse click on a bookmark folder in the bookmark bar. (3) Mouse-click a bookmark in the bookmark folder. (4) As soon as possible *after* finishing the mouse-click in (3), press the command key. After the mouse-click, the keypress should be irrelevant, but if you get the timing 'right', the bookmark opens in a separate tab, as if you command-clicked it. Note that I cannot reproduce this issue with links in a web page. If I follow steps (1)-(4) with a link instead of with a bookmark, the link always opens in the current tab rather than a new tab; the command key is properly ignored after the click is over. 18-Mar-2008 Jeff Johnson: This is still an issue in both Leopard and Tiger after Safari 3.1 and Security Update 2008-002. Other menus don't work like this. For example, if you open two windows in Safari, open the File menu, select Close Window, and then press the option key as quickly as possible after releasing the mouse, it does not close all windows, even though holding down the option key turns the Close Window menu item into Close All Windows. This is definitely a bug in the bookmark menus. 19-Apr-2008 Jeff Johnson: For this kind of modifier key detection, I've found that the function GetCurrentEventKeyModifiers() works well. (I've read that there's a Quartz alternative, but it doesn't seem to be documented.) In my testing, GetCurrentEventKeyModifiers() performed perfectly when used to detect modifier keys for selected menu items. If you give me the code excerpts, I'd be happy to write a fix for you! :-) This problem has annoyed me every day since I updated to Safari 3, and it has given me thoughts of abandoning Safari for some other browser. Unfortunately, the alternatives are inferior, so I may have to write my own browser. Please don't make me write my own web browser!