Closed
Bug 12379
Opened 26 years ago
Closed 25 years ago
Frames don't get ENTER or RETURN key downs.
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
M16
People
(Reporter: hyatt, Assigned: joki)
References
Details
(Whiteboard: [PDT-])
I have implemented keyboard navigation in the tree control. To see it, open up
the bookmarks window in apprunner (by selecting Manage Bookmarks from the
Bookmarks menu).
Once it comes up click on a node. Then use the arrow keys to move down and up.
With a folder selected, hit the Enter key.
Current Behavior: Nothing happens.
Expected Behavior: The node should open. I never even see the enter key being
hit. This is happening on Win32.
Comment 1•25 years ago
|
||
Is this only on Windows? Is it still broken?
Comment 3•25 years ago
|
||
joki -- do you have a milestone in mind for this one?
Assignee | ||
Updated•25 years ago
|
Target Milestone: M15
Updated•25 years ago
|
Summary: [DOGFOOD] Frames don't get ENTER or RETURN key downs. → Frames don't get ENTER or RETURN key downs.
Assignee | ||
Comment 5•25 years ago
|
||
Mass-moving bugs out of M15 that I won't get to. Will refit individual
milestones after moving them.
Target Milestone: M15 → M16
Assignee | ||
Comment 6•25 years ago
|
||
Okay, this is taken care of. I have no idea why this ever went to dogfood
though.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 7•25 years ago
|
||
The menu activates when enter is hit, but the arrow keys do not move the
highlight bar.
Windows only.
Build: 2000-06-01-08-M16
Think this got marked dogfood by mistake. Removing dogfood keyword.
Assignee | ||
Comment 8•25 years ago
|
||
Arrow keys are working for me at the moment on WinNT
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
Comment 9•25 years ago
|
||
Mass update: changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer
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
•