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 T74804, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 72804 - VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down

Summary:	VisualEditor:After adding a focusable node inside a content cell , placing cu...

Status: RESOLVED DUPLICATE of bug 71560 Product: VisualEditor Classification: Unclassified Component: Editing Tools (Other open bugs) Version: unspecified Hardware: All All Importance: Unprioritized normal Target Milestone: --- Assigned To: Editing team bugs – take if you're interested! URL: Whiteboard: Keywords: Depends on: Blocks: ve-tablesupport   Show dependency tree / graph		Reported: 2014-10-31 05:46 UTC by Rummana Yasmeen Modified: 2014-11-05 16:05 UTC (History) CC List: 7 users (show) elitre82 esanders etonkovidova jforrester rmoen ryasmeen tparscal See Also: Web browser: --- Mobile Platform: --- Assignee Huggle Beta Tester: ---

Attachments video capture (1.03 MB, video/quicktime) 2014-11-03 20:10 UTC, Rummana Yasmeen Details Add an attachment (proposed patch, testcase, etc.)

Description Rummana Yasmeen 2014-10-31 05:46:01 UTC Steps to reproduce: 1.Insert a table 2.Add any focusable node inside content cell like template/image/math function 3.Place the cursor at the end of the table Observed Result: The page scrolls down to the end of it Comment 1 Ed Sanders 2014-11-03 14:34:35 UTC Works for me in Chrome & FF Comment 2 Rummana Yasmeen 2014-11-03 20:10:20 UTC Created attachment 17002 [details] video capture Still happening for me , See the video capture Comment 3 Ed Sanders 2014-11-05 16:05:00 UTC Oh *that* outside of the table. Yeah - you're not supposed to put your cursor there... *** This bug has been marked as a duplicate of bug 71560 ***