You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Okay, excellent. So, let's assume there's no easy way to optimize the width changes. But we can very easily optimize everything else. Strip all the jQuery calls out of partialRender and renderElement. Don't look up any elements there either; cache your element lookups beforehand, ideally as raw DOM elements or arrays of DOM elements.
(12:18:10 PM) Ryan Grove: In renderElement, if you make only native DOM calls, that should chop a significant chunk off your cost, even if you still touch all those widths.
(12:18:30 PM) Aphyr: Yeah, I think you're right.
(12:18:32 PM) Ryan Grove: In Chrome and FF, you have a very good native querySelectorAll implementation, so jQuery is pretty unnecessary for that.
The text was updated successfully, but these errors were encountered:
Okay, excellent. So, let's assume there's no easy way to optimize the width changes. But we can very easily optimize everything else. Strip all the jQuery calls out of partialRender and renderElement. Don't look up any elements there either; cache your element lookups beforehand, ideally as raw DOM elements or arrays of DOM elements.
(12:18:10 PM) Ryan Grove: In renderElement, if you make only native DOM calls, that should chop a significant chunk off your cost, even if you still touch all those widths.
(12:18:30 PM) Aphyr: Yeah, I think you're right.
(12:18:32 PM) Ryan Grove: In Chrome and FF, you have a very good native querySelectorAll implementation, so jQuery is pretty unnecessary for that.
The text was updated successfully, but these errors were encountered: