Closed Bug 644320 Opened 13 years ago Closed 13 years ago

Input box viewport keeps returning to top when cursor down

Categories

(Core :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: markhobley, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0

On a wiki or other such website, the input box viewport keeps returning to the top when the cursor down key is pressed.



Reproducible: Sometimes

Steps to Reproduce:
Create a file containing about 500 lines:

Line 1
Line 2
...
...
Line 500

Now try to edit one of the lines, cursor down to about line 100.


Actual Results:  
The input box viewport returns to the top, so only the first so many lines are visible. (You cannot see line 100 to edit it).

Expected Results:  
You should be able to see the line containing the cursor for edit.

This has been working for a couple of weeks, but today the problem is persistent. I cannot edit the online document because the viewport keeps rolling up.
Seems to work fine for me using Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.2a1pre) Gecko/20110323 Firefox/4.2a1pre ID:20110323074443

Please can you elaborate as to the STR (eg a specific URL would be great), in case I'm not doing it correctly.

Does this work fine with 3.6.x?

Could you see if there are any errors in the console (just errors, don't need to warnings) and paste them here please. Use Ctrl + Shift + J to access.

Also, could you see if the issue occurs if using Firefox in safe mode:
http://support.mozilla.com/kb/Safe+Mode

How about with a new, empty testing profile? (Don't install any addons into it)
http://support.mozilla.com/kb/Basic+Troubleshooting#w_8-make-a-new-profile
Component: Keyboard Navigation → General
Product: Firefox → Core
QA Contact: keyboard.navigation → general
Version: unspecified → Trunk
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.