Bug 92594 - Consider lazily updating layout on addRange and removeAllRanges
Summary: Consider lazily updating layout on addRange and removeAllRanges
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: HTML Editing (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-29 12:47 PDT by Ryosuke Niwa
Modified: 2017-07-18 08:30 PDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 2012-07-29 12:47:06 PDT 
Right now, setSelection call in addRange and removeAllRanges forces page layout.
We can probably delay that until the selection is rendered or validation is required.
Comment 1 Ryosuke Niwa 2012-07-29 13:07:27 PDT 
http://crbug.com/138439
Comment 2 Silenio Quarti 2012-12-07 11:51:04 PST 
What is the status on this bug?

This is affecting our editor (orion.eclipse.org) on newer versions of Chrome. The problem started happening on Chrome 22. The performance of addRange() is really bad for long lines. See [1] for more info.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=394985