Last modified: 2014-07-21 08:50:09 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 T54577, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52577 - VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V)
VisualEditor: Scroll to the user's position when VE is invoked via shortcut (...
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
MediaWiki integration (Other open bugs)
unspecified
All All
: Normal enhancement
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-06 14:38 UTC by Guillaume Paumier
Modified: 2014-07-21 08:50 UTC (History)
8 users (show)

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


Attachments

Description Guillaume Paumier 2013-08-06 14:38:08 UTC
I don't know if this is possible, or if it's been requested elsewhese, but a few users on the French-language Wikipedia have suggested that, when the user has scrolled through the page and invoked VisualEditor via the keyboard shortcut, VE should automatically scroll to that same position on the page when it opens (similarly to what the section edit link does).
Comment 1 Daniel Naber 2014-07-21 08:50:09 UTC
This should always be the case, no matter how the editor is invoked. "User's position" when the editor is opened should be *exactly* the same as before. Use case: I want to fix a simple spelling error, so I click on the edit link on the paragraph. Often, the content has now scrolled up/down a bit and I need to find the location of the spelling error again. This is surprisingly difficult/annoying (just give it a try).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links