Last modified: 2014-11-03 20:22:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T60091, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 58091 - VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?)
VisualEditor: History actions should scroll the location of the transaction i...
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: Normal enhancement
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-12-06 09:11 UTC by Wikifram@gmail.com (Account disabled)
Modified: 2014-11-03 20:22 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Wikifram@gmail.com (Account disabled) 2013-12-06 09:11:26 UTC 
When you have made changes to a page in VE, you can use the "undo" button to reverse these. However, the page doesn't scroll when doing this, so you don't "see" what the undo is actually doing. The same probably applies to the "redo" button, I haven't checked that one
Comment 1 Alex Monk 2014-11-01 03:51:02 UTC 
Hmm... Shouldn't this be a case of scrolling to the new location of the cursor when you undo/redo?
Comment 2 James Forrester 2014-11-03 20:14:12 UTC 
(In reply to Alex Monk from comment #1)
> Hmm... Shouldn't this be a case of scrolling to the new location of the
> cursor when you undo/redo?

Pretty much, which is bug 51911.
Comment 3 Alex Monk 2014-11-03 20:19:15 UTC 
Dupe then?
Comment 4 James Forrester 2014-11-03 20:22:57 UTC 
(In reply to Alex Monk from comment #3)
> Dupe then?

Doing it for the undo/redo stack is probably complicated, so I was leaving them distinct.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links