Closed Bug 21823 Opened 25 years ago Closed 25 years ago

Bugzilla scrolled text input field doesn't grab arrow keys

Categories

(Core :: DOM: Editor, defect, P3)

Product:
Core
Component:
DOM: Editor
Platform:
x86
Other
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: selmer, Assigned: Brade)

Details

(Whiteboard: [PDT-]) 

Enter a bug in bugzilla.  On that page, click in the description field and enter
some text.  Now, try to use the up/down arrow keys to move between lines of
text.  You will find that the whole page scrolls instead of the content inside
the text input box.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
I believe this is a result of 21610, marking this as a dup of that, if you
disagree, please reopen.

*** This bug has been marked as a duplicate of 21832 ***
Status: RESOLVED → VERIFIED
verified in 12/16 build
Re-opening.

This was actually marked as a duplicate of 21832, not 21610. Either way, both of
those are verified/marked as duplicates of resolved bugs.

Using this morning's build (only checked Mac), the Up/Down arrow keys didn't
have any effect within the text field. I assume that's a known bug, but
nonetheless...
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
It's very difficult to use Seamonkey for dogfood if the up/down arrow keys don't 
work in text fields. 

Marking as dogfood in the unlikely event this isn't being already tracked by 
another bug.
Keywords: dogfood
this is still broken, assigning to Kathy for debugging - Kathy I'm not sure if 
this would be Mike's bug or not
Assignee: beppe → brade
Status: REOPENED → NEW
Target Milestone: M14
Putting on PDT- radar.  Would not hold beta1 for this.  or call it dogfood.
Keywords: beta1
Whiteboard: [PDT-]
This works for me
Eli--can you recheck?
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
works for me...p[lease roepen if it doesn't wor for you Eli or Selmer
Status: RESOLVED → VERIFIED
Yup. Fixed in this morning's Mac OS build. Thanks! (whoever fixed it unknowingly)
You need to log in before you can comment on or make changes to this bug.