Closed Bug 361196 Opened 19 years ago Closed 19 years ago

no scrollInToView on undo/redo in textarea

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 331269

People

(Reporter: helpmepro1, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 i textarea that must scroll because it's text is long, in textarea on undo/redo: it changes the text (undo/redo) it moves the caret to the correct place * it does not scrolls to the caret to show the change; it selects the changed text on undo from redo; when i do undo or redo there is no sense to where and what has changed. i migrated my web file source code editor to firefox and i found core problems(i use Firefox 2) and this one of them Reproducible: Always Steps to Reproduce: 0. it happened to me in Firefox 2 1. tape many lines long text so you have scrollbars in a textarea 2. select and delete a word from the end of typed text. 3. scroll to top of textarea 4. click Ctrl+Z once Actual Results: the result: is that it is does not scrolls to the caret. you see that nothing happened on the screen but if you will scroll you will find the caret in place and the added text is corrected in undo and in redo. Expected Results: the expected result: is it will remove the added text in step 2, move the carret, scroll into view, also in redo should select the text(not just in undo). i think it should select the text only if not the whole text is changed in whole text it is not useful. also misc foo : (not related to the bug); * it restart the caret position and the scroll position on minor content changes by script like insert tab char near the caret. * focus on the window takes focus from textarea.
*** This bug has been marked as a duplicate of 331269 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.