Summary: | Batch DOM changes | ||
---|---|---|---|
Product: | WebKit | Reporter: | chrome |
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WONTFIX | ||
Severity: | Enhancement | CC: | chrome |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | All |
Description
chrome
2010-01-06 05:52:53 PST
I'm pretty sure WebKit doesn't do layout or rendering in this scenario. It's only performed after script execution finishes, or when it's necessary for further processing (e.g. if the script asks for element size). I agree, but I am still wondering what is the "slow" part, calculating sizes or putting things on screen? If it's "drawing" a batch-mode would still have some effect. I see that this might break webkits rendering logic and isn't easy or even useful to implement. All this told me that keeping sizes in my script and reusing them as much as possible, is the only way to squeeze out some speed. This answers some questions I had asked in several related groups, but didn't get an answer. Thank you. |