Closed Bug 200294 Opened 22 years ago Closed 22 years ago

Cursor keys don't move cursor correctly when text-entry is being performed after line has wrapped

Categories

(Firefox :: General, defect)

Sun
SunOS
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 178735

People

(Reporter: doofer-public, Assigned: bugzilla)

References

()

Details

(Keywords: qawanted, Whiteboard: Need to reproduce(*nix))

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4a) Gecko/20030402 Phoenix/0.5
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4a) Gecko/20030402 Phoenix/0.5

If you type a long enough string of characters for the cursor to hit a new line
in a text entry box (just like the one I am using now), the cursor keys will not
work correctly after the first line. You can move up and down OK, but left to
right is completely screwey.

Reproducible: Always

Steps to Reproduce:
1. Start writing something in the 'additional comments box' on this bug description
2. Continue until you have got onto the second line (no pressing [enter] - its
cheating, and it will not reproduce the bug).
3. Press left mid line, not on the first line...

Actual Results:  
Cursor does not move one character to the left or right

Expected Results:  
Cursor should move through text as it does on the first line.
Reporter:
Can you still reproduce with your clean profile?

Works for me with:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030402 Phoenix/0.5
I just moved my .phoenix directory to .phoenix-old, so Phoenix would not find my
profile, it loaded up with no bookmarks or cookies so I assume it worked, and
yes, I could still reproduce it. It could be a *nix thing of course.
Reporter:
Did you try with same build-ID Mozilla?

-> qawanted (Need to reproduce)
Keywords: qawanted
Whiteboard: Need to reproduce(*nix)
No. I was going to try but yesterdays nightly tar.gz wasn't a valid archive. I
don't have time to try it today, though I will give it a go when I have the chance.
Dooferlad wrote:
> No. I was going to try but yesterdays nightly tar.gz wasn't a valid archive. I
> don't have time to try it today, though I will give it a go when I have the 
> chance.

Can you post the exact URL of the tar.gz tarball which failed for you, please ?
The one that wouldn't unpack was the nightly build of the same date that I got
the  nightly build of Phoenix that still showed the cursor ptoblems. You can get
the date from the brower ID that I submitted the bug with.

I have had problems in the past with nightlies sometimes not being complete
archives, but they just get overwritten with a valid archive some time later
when another comes out.

Unfortunatly I don't have the time or resources here to build phoenix myself and
get a debugger on it. If it isn't doing it in Windows then it is probably a GTK
problem. I haven't rebuilt GTK on this machine for at least 6 months, so if
there is a bug I am hitting, it could be that.

If someone else can run a Solaris build and see if they can reproduce it, then
that would help narrow down where the problem is.
Works for me on GNU/Linux with GNOME 2

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030419 Phoenix/0.5+
Is this problem still present using recent builds of Firebird?
Yep. We really need someone else with a Solaris box to confirm it.
I have the same problem in all versions of Mozilla on Sun or PC from 1.2.1 and on
So per comment #10 this seems to be a SeaMonkey issue - hence we should try and
find a related SeaMonkey bug and finally either dupe it or move it over to
SeaMonkey!
Erik, indeed, this appears to be a dupe of bug 178735

although some comments indicate it was fixed, the bug is still new
I can reproduce this with 1.4 release on Solaris 8.
per comment 13, moving to dupe against 

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