Closed
Bug 7027
Opened 26 years ago
Closed 25 years ago
page up/down requires a focus click to start working
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Core
DOM: UI Events & Focus Handling
Tracking
()
M11
People
(Reporter: mcafee, Assigned: joki)
References
Details
(Whiteboard: [TESTCASE] erin@imaginet.com)
Attachments
(3 files)
Linux.
page up/down does not scroll content until focus is
set to the window, e.g. click in the window once
and then page up/down starts working.
Reporter | ||
Updated•26 years ago
|
Target Milestone: M7
Reporter | ||
Comment 2•26 years ago
|
||
not M6, marking M7.
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M7 → M8
Assignee | ||
Comment 3•26 years ago
|
||
I had really hoped to nail this one for M7 but it is not to be. Requires more
discusion with xpfe guys to fix.
Assignee | ||
Updated•26 years ago
|
OS: Solaris → All
Summary: Gtk: page up/down requires a focus click to start working → page up/down requires a focus click to start working
Assignee | ||
Comment 4•26 years ago
|
||
This is also an xp bug, actually.
Updated•26 years ago
|
Hardware: Sun → All
Comment 6•26 years ago
|
||
Changing platform to ALL, page up/page down does not work on Windows in build:
1999-16-17-08-M7
Assignee | ||
Comment 7•26 years ago
|
||
Just so we're clear on this, does pgdn/up not work at all or not without a
click? These are different bugs and I want to make sure they don't get mixed
up. This bug is for pgdn/up not working until the window is clicked in.
Comment 8•26 years ago
|
||
On 6/17 Linux build, page up/down works but only after clicking in the window.
The Lose98 Apprunner Build of 1999061708 again offers cursor-key functionality,
but only after a focus click.
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Comment 10•26 years ago
|
||
Win32 builds require a click, then they work. This bug is a duplicate of 4125,
so I'm marking it as such.
*** This bug has been marked as a duplicate of 4125 ***
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Updated•26 years ago
|
Status: VERIFIED → REOPENED
Reporter | ||
Comment 11•26 years ago
|
||
Sorry, I don't buy the dup story.
4125 has a different test case, is marked Win32, and
has a milestone of M4. I like 7027 better than 4125,
can we get joki to add a comment here? Reopening.
Comment 12•26 years ago
|
||
Clearing Duplicate resolution since the bug is now Reopened.
Assignee | ||
Updated•26 years ago
|
Status: REOPENED → ASSIGNED
Target Milestone: M8 → M9
Assignee | ||
Comment 13•26 years ago
|
||
This is partially fixed. Right now if you unfocus, and then refocus the window
these keys work but on initial window creation they don't. I'd say that's
probably a WebShellWindow kind of thing. But I'd say this is as good as it will
get for M8 since I need WebShellWindow guys to tell me where this initial focus
change should happen. Moving rest to M9.
Updated•26 years ago
|
Whiteboard: making test erin@imaginet.com
Comment 14•26 years ago
|
||
Comment 15•26 years ago
|
||
Comment 16•26 years ago
|
||
Updated•26 years ago
|
Whiteboard: making test erin@imaginet.com → [TESTCASE] erin@imaginet.com
Comment 17•26 years ago
|
||
joki at w3c
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 18•25 years ago
|
||
This one really is a dupe. Marking as such.
*** This bug has been marked as a duplicate of 9701 ***
Comment 19•25 years ago
|
||
Moving to M11. Not to hold for M10 per conversation with joki during bug triage
today.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 20•25 years ago
|
||
verified
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•