Ten days ago I submitted a question on StackOverflow: "How to profile CSS selectors?" [1] and I didn't get proper answers.
I'm going to repost (and update) that question here<p>1) Google removed the CSS Profiler [2]<p>2) Firefox doesn't have one [3]<p>3) Opera had dragonfly, but now Opera is Blink based... and dragonfly is gone.<p>4) The only profiler around there in Safari, doesn't work on my 7.0.0 / OSX 10.9. (it keeps recording CSS and I can't stop it)<p>5) I know about "CSS-Stress-Testing-and-Performance-Profiling" [4] but I didn't figure it out how to use it for my purposes.<p>The chromium guys say: "CSS selector matching is now reasonably fast for the absolute majority of common selectors that used to be slow at the time of the profiler implementation", well...<p>I came across some benchmarks on jsperf.com like http://jsperf.com/css-selector-speed/15 and basing on that one I wrote: http://tagliala.github.io/vectoriconsroundup/cssperf/fa400 and http://tagliala.github.io/vectoriconsroundup/cssperf/fa321<p>I ran those tests (repeating them several times, results may change a lot across different runs) on different browsers and hardware and I got these results: https://gist.github.com/tagliala/7174356<p>It seems there are still differences and when developing css frameworks you should take care of selectors.<p>So... are you still profiling CSS selectors? And how?<p>Sorry for my English<p>[1]: http://stackoverflow.com/questions/19407451/how-to-profile-css-selectors
[2]: http://code.google.com/p/chromium/issues/detail?id=265486
[3]: http://bugzilla.mozilla.org/show_bug.cgi?id=713031
[4]: http://edinborough.org/CSS-Stress-Testing-and-Performance-Profiling