Closed Bug 265039 Opened 21 years ago Closed 21 years ago

Middle-clicking history items no longer opens them in new tabs

Categories

(Firefox :: Bookmarks & History, defect)

1.0 Branch
x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED FIXED

People

(Reporter: jruderman, Assigned: bugs)

Details

(Keywords: fixed-aviary1.0, regression)

10/18 aviary build. Steps to reproduce: 1. Open the history sidebar. 2. Middle-click an item. Result: the item becomes selected, but nothing else happens. Expected: item should open in a new tab. The checkin that broke this was at 2004-10-17 18:15. The intent of the checkin seemed to be to make Ctrl and Shift do multiple selection actions like in a normal listboxes.
Flags: blocking-aviary1.0?
confirming win2k sp4 Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041019 Firefox/1.0
ben is having a look...
Flags: blocking-aviary1.0? → blocking-aviary1.0+
Ctrl-clicking in history has always opened in new tab and this is now broken. We kind of can't have crtl click be doing 2 things here. Need to decide which crtl-click action is the correct one and document it that way.
Actually, the way it works now is completely inconsistant with a normal picker window where shift-click and ctrl-click can select multiple items. In a picker of this sort then single click would need to select a single item. So, either need to revert to requiring a double click to open a page from bookmarks and history to make it work like a picker, or have it work like links on a webpage and have ctrl-click open in tabs etc. The current behaviour is not constant with either interface.
this bug now appears to be fixed (although how I don't know) Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041020 Firefox/1.0
This was fixed by the checkin for bug 265150.
resolving as Fixed per previous two comments.
Status: NEW → RESOLVED
Closed: 21 years ago
Keywords: fixed-aviary1.0
Resolution: --- → FIXED
Component: History → Bookmarks & History
QA Contact: mozilla → bookmarks
You need to log in before you can comment on or make changes to this bug.