366796 - textarea: unexpected cursor behaviour during arrow key navigation

Status: RESOLVED WORKSFORME

(Core :: DOM: Selection, defect)

Description

[Alexander Klauer]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061205 Iceweasel/2.0.0.1 (Debian-2.0.0.1+dfsg-1)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061205 Iceweasel/2.0.0.1 (Debian-2.0.0.1+dfsg-1)

cursor column position is reset to 0 when arrow up/down keys are used, provided that current cursor column position is smaller than the length of the line below (arrow down) resp. above (arrow up) the current line.

Reproducible: Always

Steps to Reproduce:
1. Go to the indicated URL
2. In the text area, place cursor between the two closing curly braces ("}}") in line 13 or any other appropriate line
3. press arrow up or arrow down
Actual Results:  
cursor column position is reset to 0 (beginning of line)

Expected Results:  
cursor column position remains unchanged

Current software is rebranded to "Iceweasel" by my Linux distributor, but I believe the bug already occurred when it was still called "Firefox".

Comment 1

[Uri Bernstein]

Duplicate of / related to bug 358361?

Comment 2

[Alexander Klauer]

I don't use TB, but judging from the description it quite seems so. So it's not a textarea bug, but a bug in the common edit widget used by several pieces of Mozilla software. I'm not familiar with this bug tracking system. Should I file a bug against some component (Toolkit component perhaps?) instead and mark this bug as a duplicate?

Thank you.

Comment 3

[Uri Bernstein]

Let's keep this bug, since we're not sure it's a duplicate.

I'm moving it to Core/Selection for now. This seems to be Linux-only - I can't reproduce it on Mac, so I can't confirm it.

Comment 4

[Steve England [:stevee]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.2pre) Gecko/2007011004 BonEcho/2.0.0.2pre
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a2pre) Gecko/20070112 Minefield/3.0a2pre ID:2007011204 [cairo]
WFM

Comment 5

[Mike Hommey [:glandium]]

I'd say it's a duplicate of bug #335810.

Comment 6

[Alexander Klauer]

Hi, the bug is gone, and has been gone for some time now. In all likelihood, it occurred due to bug #335810. So I'm closing my bug report. Feel free to reopen if this is not appropriate.