Bug 92594
| Summary: | Consider lazily updating layout on addRange and removeAllRanges | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> |
| Component: | HTML Editing | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | a9016009, darin, enrica, mitz, silenio_quarti, tpopela |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ryosuke Niwa
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ryosuke Niwa
http://crbug.com/138439
Silenio Quarti
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