Bug 42774 - Editable elements don't scroll to the bottom of inserted html
Summary: Editable elements don't scroll to the bottom of inserted html
Alias: None
Product: WebKit
Classification: Unclassified
Component: HTML Editing (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC All
: P2 Normal
Assignee: Nobody
URL: http://dev.ckeditor.com/ticket/5558
: insertHTML-scroll (view as bug list)
Depends on:
Reported: 2010-07-21 12:32 PDT by Sa'ar Zac Elias
Modified: 2012-05-01 22:44 PDT (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Sa'ar Zac Elias 2010-07-21 12:32:43 PDT
Inside an editable element (contenteditable="true"), after using insert html, the element scrolls to the beginning and not to the end of the new data.
A simple workaround was posted at http://dev.ckeditor.com/ticket/5558.
Comment 1 webkit 2010-07-21 15:13:34 PDT
By "using insert html" the reporter meant execCommand('inserthtml').
Comment 2 Ryosuke Niwa 2010-10-27 23:26:11 PDT
Could you describe more detailed reproduction steps and/or reduction and the problem (e.g. horizontal scroll bar stays, vertical horizontal bar resets, etc...) ?
Comment 3 Ryosuke Niwa 2010-10-27 23:28:38 PDT
Is this bug somehow related to https://bugs.webkit.org/show_bug.cgi?id=30243 ?
Comment 4 Emerick Rogul 2010-11-03 11:38:58 PDT
I also see this behavior (and yes, I would say that it is similar to the bug mentioned in the previous comment).

To reproduce the behavior, insert a large chunk of HTML into a contentEditable element using exec('inserthtml') - the chunk must be large enough that it will extend beyond the bottom border of the window.  After calling exec('inserthtml') the expected behavior would be that:

1 - The caret is at the end of the inserted block of HTML.

2 - The caret is scrolled into view.

Instead, what happens is just 1.  In other words, the caret is indeed at the end of the inserted block of HTML, but the caret has *not* been scrolled into view.
Comment 5 Ryosuke Niwa 2012-05-01 22:44:11 PDT
*** Bug 30243 has been marked as a duplicate of this bug. ***