3 ms·
one big drawback I'm seeing is binding styles directly to DOM elements (it will appear as style attribute). this definitely has memory (many non-shared styles)
by woid 17y ago
one big drawback I'm seeing is binding styles directly to DOM elements (it will appear as style attribute).
this definitely has memory (many non-shared styles) and performance implications (may cause many reflows because you are setting styles individually) and it may interfere with existing code
I would expect this tool to generate real CSS stylesheet code and embed it into page dynamically
- axod 17y agoI don't think this is an issue. You're modifying the DOM directly. Those style properties exist anyway. You're just modifying them via js. It only "appears as style attribute" if you serialize the DOM into HTML.
- woid 17y agoHave you ever looked at any open-source browser implementation? Because of cascading nature of style definition. Data structures describing current styling form trees (for memory efficiency and easy manipulation from script). Effective styles are evaluated during rendering. For example look at this talk and around 11:30 the guy is describing style-related data structure in Chrome/WebKit: http://www.youtube.com/watch?v=RVnARGhhs9w http://www.youtube.com/watch?v=RVnARGhhs9w Your statement "Those style properties exist anyway" is simply not true.