Closed
Bug 42188
Opened 25 years ago
Closed 25 years ago
form controls break navigational keys (up/down arrows, spacebar)
Categories
(Core :: Layout: Form Controls, defect, P3)
Core
Layout: Form Controls
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: dbaron, Assigned: mjudge)
References
Details
(Keywords: regression, Whiteboard: [nsbeta2+][dogfood-])
DESCRIPTION: It seems the presence (or possibly activity) of form controls on a
page prevents the up/down arrows from being used to scroll the page.
STEPS TO REPRODUCE:
* start mozilla
* hit "Bugzilla" link in personal toolbar (or otherwise load http:
//bugzilla.mozilla.org/ )
* click in body of page
* hit down arrow to scroll
ACTUAL RESULTS:
* nothing
EXPECTED RESULTS:
* page scrolls down
DOES NOT WORK CORRECTLY ON:
* Win98 mozilla 2000-06-09-08-M17
WORKS CORRECTLY ON:
* Win98 mozilla 2000-06-08-08-M17
Reporter | ||
Updated•25 years ago
|
Keywords: nsbeta2,
regression
Reporter | ||
Comment 1•25 years ago
|
||
cc:ing mjudge
Comment 2•25 years ago
|
||
yep, noticed this also yesterday on windows - related to ender lite landing, I
guess. beppe and I were trying to figure this out.
Comment 5•25 years ago
|
||
Reporter | ||
Comment 9•25 years ago
|
||
Did you intend to reassign this?
Comment 10•25 years ago
|
||
FWIW: I can confirm this happening on Linux, buildID 2000061220. Scrollbars work
fine, PgUp/PgDn works fine, but up/down arrows do not scroll and produces
JavaScript error:
line 0: controller has no properties
OS should probably be changed to 'All'.
Comment 12•25 years ago
|
||
Changed platform and opsys to all/all
OS: Windows 98 → All
Hardware: PC → All
Comment 13•25 years ago
|
||
well, m16 has passed and this hasn't been fixed, so i changed the milestone to
m17. adding dogfood kw since this happens *often*.
question: does this also affect the spacebar? i've also seen the spacebar
failing. [eg, 2000.06.14.08-m17, linux]
Comment 14•25 years ago
|
||
S.E.V.: I can confirm the spacebar not working on buildID 2000061320, Linux.
Expected results: should scroll down a page just like pressing PgDn would do.
Actual results: no scrolling.
The spacebar problem may be a different animal because I don't get any
javascript error messages printed to stdout like I do with the up/dn arrows.
Comment 15•25 years ago
|
||
*** Bug 42503 has been marked as a duplicate of this bug. ***
Updated•25 years ago
|
Target Milestone: M17 → M16
Comment 16•25 years ago
|
||
setting to m16, where + bugs live
Comment 17•25 years ago
|
||
*** Bug 42884 has been marked as a duplicate of this bug. ***
Comment 18•25 years ago
|
||
*** Bug 42925 has been marked as a duplicate of this bug. ***
Comment 19•25 years ago
|
||
*** Bug 42987 has been marked as a duplicate of this bug. ***
Comment 20•25 years ago
|
||
*** Bug 42995 has been marked as a duplicate of this bug. ***
Comment 21•25 years ago
|
||
I just stumbled over that bug too and I was able to reproduce it in 061920 on
W2k w/o any form control present:
1) Fire up Mozilla with debug console
2) Click on 'Mozilla.org at a glance'
3) after page finished loading try down/up arrow
Actual result:
Page doesn't scroll either down or up but prints out in the console
JavaScript error:
line 0: controller has no properties
If you click on the document area to give it focus, arrow keys work again. If
you though go to bugzilla start page then (form controls), arrow keys are
completely broken.
I suggest therefore: Change component to...keyboard navigation(?) and change
severity to at least major.
Comment 22•25 years ago
|
||
The fact that the active document doesn't receive key bindings until it
receives focus (via being clicked upon) is a known bug, and it's been that way
for quite awhile...
Comment 23•25 years ago
|
||
This is not the old 'active window has to be clicked in' bug; this is a
new and highly annoying bug whereby windows displaying pages that have a
form in them (anywhere) do not scroll on spacebar/cursor down/cursor up,
even when they otherwise have focus. I really think this is an important
bug; for me, it is a significant usability hit to have spacebar stop
working (sufficiently significant that I have stopped trying to use recent
CVS pulls of Mozilla; it is simply too frustrating to move through pages
without a working spacebar).
Comment 24•25 years ago
|
||
Chris, I realize this isn't the same bug as the "must give document focus"
bug...I was responding to Jonas, who seemed to imply that this problem might not
be specific to the presence of form controls...
Comment 25•25 years ago
|
||
update summary
Summary: form controls break up/down arrows → form controls break navigational keys (up/down arrows, spacebar)
Comment 26•25 years ago
|
||
*** Bug 43197 has been marked as a duplicate of this bug. ***
Comment 27•25 years ago
|
||
M16 has been out for a while now, these bugs target milestones need to be
updated.
Comment 28•25 years ago
|
||
*** Bug 43437 has been marked as a duplicate of this bug. ***
Comment 29•25 years ago
|
||
this has been a continueing problem ( and annoyance ) in the milestone 17
nightly builds. shouldn't it be assignhed there?
Assignee | ||
Comment 30•25 years ago
|
||
this is fixed. non-text-selection was being hit from the ender-lite. now its
stubbed in nsTextAreaSelectionImpl.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 31•25 years ago
|
||
Marking VERIFIED FIXED on:
- MacOS9 2000-07-12-15-M17 Commercial
- Linux6 2000-07-12-21-M17 Commercial
- Win98 2000-07-12-21-M17 Commercial
Status: RESOLVED → VERIFIED
Comment 32•24 years ago
|
||
Don't want to panic people, but on BuildID 2000121904 Win98 I am seeing a
problem with scrolling.
Not on every page, but sometimes, notably on news.bbc.co.uk and slashdot.org
What happens is that the up/down arrows aswell as the page-up/page-down buttons
cease to provide any scrolling function, no crashes occur, but nor does any
scrolling.
This does not occur _every_ time the above pages are visited, but I have managed
to reproduce it by closing down my browser, opening it up again and revisiting
the sites. These pages are notable for having form elements in them, hence my
reporting this here. Is this a regression? Anyone else noticing this problem?
You need to log in
before you can comment on or make changes to this bug.
Description
•