Performance Impact of CSS Selectors
A few months back there were some posts about the performance impact of inefficient CSS selectors. I was intrigued - this is the kind of browser idiosyncratic behavior that I live for. On further investigation, I’m not so sure that it’s worth the time to make CSS selectors more efficient. I’ll go even farther and say I don’t think anyone would notice if we woke up tomorrow and every web page’s CSS selectors were magically optimized.
Related Submissions:
- High Performance Web Sites :: Simplifying CSS Selectors ‘Simplifying CSS Selectors’ is the last chapter in my next book. My investigation into CSS selector performance is therefore fairly recent. A few months ago,...
- Why You Should Deeply Nest Your CSS Selectors. Most developers, even experienced developers, don’t understand the value of deeply nesting CSS selectors. Although writing the same selectors over and over might seem redundant,...
- 101 on jQuery Selector Performance Last week I analyzed a web page that spent 4.8 seconds in the onLoad event handler of a custom script file. It turned out that...
- Forgotten CSS Selectors Well, the market share of IE 6 is now finally at a level where we as developers can say that a site “supporting” IE 6...
- Styling a Poem with Advanced CSS Selectors CSS3 selectors offer endless possibilities of targeting specific HTML elements without the need of extra markup which was already possible with previous versions of CSS....