Closed Bug 181237 Opened 22 years ago Closed 21 years ago

Control-K in a TEXTAREA only works the first three times you use it in succession.

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
FreeBSD
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: rfg, Assigned: aaronlev)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.1) Gecko/20021110 Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.1) Gecko/20021110 The control-K (kill line) editing command when used within a TEXTAREA containing many existing text lines only seem to have its normal/expected effect the furst three times it is used in succession, after wheich it seems to have no effect anymore. Reproducible: Always Steps to Reproduce: 1. Go to http://www.monkeys.com/moz-bug.html 2. Position cursor to the left of column 1 on the topmost text line. 3. Type control-K several times (more than 3). Actual Results: After the third control-K, further successive control-k's seem to have no effect. Expected Results: Control-k should have continued to kill successive text lines at or below the cursor position. This bug is REALLY aggravating! I can no longer use Google Groups and properly trim my follow-up postings because control-k is dysfunctional. P.S. Another oddity - After reproducing this bug as describe above, RELOAD on the example test page DOES NOT seem to restore the original text back into the example TEXTAREA. This is VERY WEIRD!
->keyboard nav
Assignee: asa → aaronl
Component: Browser-General → Keyboard Navigation
QA Contact: asa → sairuh
Control-K doesn't seem to work at all on today's build (2003072704, Win2000 SP4), can anyone else confirm this?
This works for me. Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040302 Firefox/0.8 Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7a) Gecko/20040307
resolving per Christopher Nehren's comments
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.