Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 60946

Summary:	can't select multiple items in list if you use "Page Down"
Product:	[Retired] Red Hat Raw Hide	Reporter:	Jonathan Kamens <h1k6zn2m>
Component:	mozilla	Assignee:	Christopher Blizzard <blizzard>
Status:	CLOSED WONTFIX	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-08-30 03:13:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jonathan Kamens 2002-03-10 06:07:44 UTC

Go to the bugzilla query form.  Click on a component.  Now hit "Page Down" as if
you are looking for another component to add to the one you clicked.  The one
you clicked is deselected and the one at the bottom of the currently displayed
portion of the list is selected instead.

Compare this to using the scrollbar to move down after the first click.  In this
case, the one you clicked remains selected, so you can use ctrl-click to add a
second selected item.  This is correct behavior.

Comment 1 Christopher Blizzard 2002-08-29 21:39:44 UTC

I don't think so.

Comment 2 Jonathan Kamens 2002-08-30 03:13:36 UTC

I don't understand why you changed the component to "mouseconfig".  This has
nothing to do with mouseconfig.  I also don't understand your assertion that the
current behavior is correct.  It differs from every other browser I've worked
with, including netscape 4.  It seems obvious to me that if I can select
multiple items using the scrollbar, I should also be able to select multiple
items using PgUp/PgDown.  Please clarify your position.

Comment 3 Christopher Blizzard 2002-08-30 18:00:06 UTC

The mouseconfig change was unintentional.  It was from testing.  I was saying
that I probably wouldn't change this at this point.  If it gets fixed upstream,
I'll pull it in.