using 3/22 build of netscape 1) launch netscape 2) launch composer 3) enter some text on several lines 4) leaving caret at the end of the last line 5) drag all the text from first line to end of line caret jumps to next line caret should remain at end of last line.
If I drag text, I expect the caret to be at the end of the dragged text or for the dragged text to be entirely selected. I see this in my debug Mac mozilla build from today. Sujay--any idea when this broke?
Assignee: beppe → brade
Summary: dragging text beyond the text results in cursor jumping to next line after the text → dragging text beyond the text results in bad caret placement
I think I am reproducing the steps 1. are you hitting enter at the end of the line or letting it wrap? 2. are you pressing enter after the last line? if not, how can the caret jump to the next line? 3. when you drag from the beginning to the end are you stopping to the left of the blinking caret or are you dragging past the caret? on win98 using the build from 2001032904 I cannot reproduce this
This problem has disappeared....Kathy can you still reproduce it?
I still see the caret going to the wrong place (Mac debug build from today).
Priority: -- → P4
Target Milestone: --- → mozilla1.0
spam composer change
Component: Editor: Core → Editor: Composer
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Target Milestone: mozilla1.0.1 → Future
What I see in Netscape 7 build is this: * enter this text into composer abc def ghi * click after 'f' * double click "abc" * drag selection to after 'i' Result is caret blinks before ghi If you skip the step for clicking after 'f', the caret blinks on the blank line where "abc" used to be.
Component: Editor: Composer → Editor: Core
Target Milestone: Future → ---
*** Bug 79770 has been marked as a duplicate of this bug. ***
Summary: dragging text beyond the text results in bad caret placement → dragging text results in bad caret placement
Still an issue. On drop, we should leave the dropped text selected. What happens now is that the selection is left where it was before you dragged, and is now collapsed.
Summary: dragging text results in bad caret placement → Selection left in wrong place after dragging text
I can not reproduce using 2003031905 build on WinXP. editorbase+, nsbeta1+ for Mac work.
Keywords: nsbeta1 → nsbeta1+
OS: All → MacOS X
Whiteboard: editorbase → editorbase+
You need to log in before you can comment on or make changes to this bug.