Closed Bug 128073 Opened 23 years ago Closed 23 years ago

middle button pastes in wrong location in TEXTAREA with long lines and vertical scrollbar

Categories

(Core :: DOM: Editor, defect)

Sun
SunOS
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 97207

People

(Reporter: scatterlined, Assigned: kinmoz)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.8) Gecko/20020205
BuildID:    0.9.8

First you have to have enough lines of text to activate the scrollbar
on the TEXTAREA. This of course depends on the value of ROWS specified
in the creation of the TEXTAREA.
This is enough lines of text to work when ROWS is 6 or less, like the
"Description" TEXTAREA on the Bugzilla Helper page.
This is a rather long line of text without any returns in it. This text in a
TEXTAREA, plus enough lines of content to make one of the lines in the TEXTAREA
scroll off the top manages to confuse mozilla. If you left double click on a
word to select it (like -> mozilla <-) and then try to middle click to paste it
at the end of the TEXTAREA you will be disappointed.
Just try and paste it here ->

Reproducible: Always
Steps to Reproduce:
1. Fill a TEXTAREA with enough lines of text to activate the vertical
   scrollbar and scroll the first line off of the top.
2. Input a really long line of text without returns (you can use the
   data I used to describe it above, it includes a line with 365
   columns
   of data).
3. Left double click on a word to select it.
4. Try to middle click at the end of the TEXTAREA to paste the
   selected text.

Actual Results:  The text you are trying to paste gets inserted above the
insert point you middle clicked at.

Expected Results:  The text getting pasted should be inserted at the insert
point you middle clicked at.
This is fixed already on the TRUNK.

*** This bug has been marked as a duplicate of 97207 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.