Bug 47047 - designMode frame slows to a crawl in some circumstances
Summary: designMode frame slows to a crawl in some circumstances
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://marijn.haverbeke.nl/upload/web...
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-02 02:57 PDT by Marijn Haverbeke
Modified: 2010-10-03 09:30 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marijn Haverbeke 2010-10-02 02:57:34 PDT
On the linked page, a designMode frame is created and filled with lots of span and br nodes. If you put the cursor at the end of any of the lines in the frame and type something, it takes up to three seconds for the text to appear. Typing in the middle of a line is responsive as normal. Using a small document or setting the whiteSpace style to "nowrap" removes the problem.

This test case is intended to simulate the kind of editable frame created by CodeMirror (http://codemirror.net) which has suffered from very bad performance in recent Safari and Chrome versions.
Comment 1 Marijn Haverbeke 2010-10-02 03:49:25 PDT
It seems I wasn't using the latest WebKit -- 533 has this problem, 534 doesn't. So this is fixed.

(As an aside, you might want to make the 'Version' drop down in the bug entry form actually reflect the current versions. It has 528+ as the highest option right now.)
Comment 2 Alexey Proskuryakov 2010-10-02 22:48:18 PDT
> (As an aside, you might want to make the 'Version' drop down in the bug entry form actually reflect the current versions. It has 528+ as the highest option right now.)

Or to remove it altogether, since it's usually unclear whether the reporter provided a correct version there, or left it at the default, or was confused about Safari and WebKit versions. And since no one is likely to take on the job of updating the version list all the time.
Comment 3 David Kilzer (:ddkilzer) 2010-10-03 09:30:58 PDT
(In reply to comment #2)
> > (As an aside, you might want to make the 'Version' drop down in the bug entry form actually reflect the current versions. It has 528+ as the highest option right now.)
> 
> Or to remove it altogether, since it's usually unclear whether the reporter provided a correct version there, or left it at the default, or was confused about Safari and WebKit versions. And since no one is likely to take on the job of updating the version list all the time.

Please file a bug.  I think Tim Hatcher used to update it.