Last modified: 2014-04-16 19:23:40 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 T55217, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53217 - VisualEditor: When editing a section, don't wait for loading to be complete before scrolling to the section
VisualEditor: When editing a section, don't wait for loading to be complete b...
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-22 16:04 UTC by Chris McKenna
Modified: 2014-04-16 19:23 UTC (History)
9 users (show)

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


Attachments

Description Chris McKenna 2013-08-22 16:04:03 UTC
When loading VisualEditor from a section edit link, the editor opens at that position on the page. However, as the TOC is not displayed in edit mode (bug 49224) the content is effectively rendered higher up so a later section in the article moves into the view (from a users point of view this is perceived as scrolling to a random point). 

The view point does move to the new location of the desired section as the final step of loading, but only if the user has not scrolled at any point while waiting. 

If they have attempted to find the section themselves while VE is loading then either (a) the view point subsequently doesn't move when loading completes, or (b) moves by the amount it would have done if the user had not scrolled (meaning it now points at a different point to desired). I have not worked out how to specifically induce one behaviour or indeed what causes either.

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


Navigation
Links