|Summary:||DOMSelection shouldn't instantiate VisibleSelection everywhere|
|Product:||WebKit||Reporter:||Ryosuke Niwa <rniwa>|
|Component:||HTML Editing||Assignee:||Ryosuke Niwa <rniwa>|
|Severity:||Normal||CC:||benjamin, darin, enrica, kling, koivisto|
|Version:||528+ (Nightly build)|
|Bug Depends on:|
Description Ryosuke Niwa 2014-02-15 19:11:31 PST
Right now, various member functions of DOMSelection instantiates VisibleSelection. This would mean that all those functions are triggering synchronous layout at that point. Defer those synchronous layout until FrameSelection's member functions are called so that we may optimize them later in the bug 127832.
Comment 1 Ryosuke Niwa 2014-02-15 19:12:12 PST
This change is needed to increase the test coverage of asynchronous selection because we don't have that many tests for selection inside text fields.