Closed
Bug 146472
Opened 23 years ago
Closed 23 years ago
History Sidebar should go on click/enter, not on select
Categories
(Core Graveyard :: History: Global, defect)
Core Graveyard
History: Global
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hugovanwoerkomqt, Assigned: bugzilla)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; MSIE 6.0; Windows NT 4.0)
Got it from the latest trunk, but they all do this.
BuildID: 2002052221
In the sidebar bookmarks section you can scroll AT LEASURE to what you are
looking for and click enter to go there.
The history section does NOT allow that, it opens an entry immediately, WITHOUT
any keyboard interaction. As a result movement though it is very erradic(sp?).
AMF it makes the history section in the sidebar just about useless.
It could be that there is a duplicate but I couldn't find it.
Reproducible: Always
Steps to Reproduce:
1.F9 to open sidebar
2.Alt PgDn to history
3.try to get to the bottom: you won't be able to.
Actual Results: History in sidebar freezes
Expected Results: Be able to scroll to anywhere: hit enter and go there.
--> history
Assignee: sgehani → blaker
Component: Sidebar → History: Global
QA Contact: sujay → claudius
Comment 2•23 years ago
|
||
This is bad. Just opening the history sidebar can take you to a random page.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Summary: Sidebar History section should act like Sidebar Bookmarks → History Sidebar should go on click/enter, not on select
Reporter | ||
Comment 3•23 years ago
|
||
Right. Sidebar History section is unusable.
Assignee | ||
Comment 4•23 years ago
|
||
This got fixed by the fix for "opening history sidebar opens link
automatically." (which was nsbeta1+)
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•23 years ago
|
||
Right. Mozilla 1.1a
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a) Gecko/20020609 does it
properlyy. Thanks.
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•