User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20061205 Iceweasel/188.8.131.52 (Debian-184.108.40.206+dfsg-1) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20061205 Iceweasel/18.104.22.168 (Debian-22.214.171.124+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".
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.
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.
Assignee: nobody → selection
Component: Form Manager → Selection
Product: Firefox → Core
QA Contact: form.manager
Version: unspecified → Trunk
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:126.96.36.199pre) Gecko/2007011004 BonEcho/188.8.131.52pre Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a2pre) Gecko/20070112 Minefield/3.0a2pre ID:2007011204 [cairo] WFM
I'd say it's a duplicate of bug #335810.
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.