Last modified: 2014-11-14 02:12:53 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 T75408, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 73408 - Flow: Keep editing doesn't scroll a new topic back into view.
Flow: Keep editing doesn't scroll a new topic back into view.
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
master
All All
: Unprioritized minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-14 02:12 UTC by spage
Modified: 2014-11-14 02:12 UTC (History)
5 users (show)

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


Attachments

Description spage 2014-11-14 02:12:53 UTC
1. Visit a Flow board
2. Start a new topic, entering "Tall topic test" in the text input.
3. In the "Post a new message to..." textarea below this, enter a tall first post, e.g. a lot of separate paragraphs, or some big images, or a long table.
4. Click Preview
5. Scroll down past the preview of the new topic and click 'Keep editing'.

Result: in both Firefox and chromium you are left way down the Flow board, and you have to scroll back up to the text inputs.

Expected: board should scroll the "Start a new topic" text input field back into view.

Workaround: use the arrow keys. The caret is in the textarea, so moving it will bring that part of the textarea into view.

Note that clicking 'Keep editing' when I add a post or edit a post and then Preview almost does the right thing in Firefox, bringing the Reply button and part of the textarea back into view. In Chrome it also leaves me way down the page.

This seems related to bug 69151.

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


Navigation
Links