Closed Bug 713031 Opened 10 years ago Closed 4 years ago
Add CSS selector profiler
Something similar to http://my.opera.com/dragonfly/blog/style-profiler-preview from Opera or https://bugs.webkit.org/show_bug.cgi?id=74004 from WebKit. AFAIK, there's currently no way to see how much time is spent on evaluating certain CSS rule, and how much time is spent on document reflow and/or repaint.
A generic profiler would be great, but a CSS selector profiler would also be very useful.
This needs a feature page.
kdangoor, would you like to do the honors or should I?
I don't believe anyone uses feature pages in Mozilla any longer. I suppose mockups, user stories and the like are still needed, but that's a task for whoever starts working on this issue.
Opera's old style profiler
I'm going to work on this in bug 975522.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 975522
Is bug 975522 really a duplicate of this? That one seems to just cover "was a selector used or not", while this is about time spent per selector. But maybe you plan to add more than what the description and existing patch over there conveys...? :)
(In reply to J. Ryan Stinnett [:jryans] from comment #7) > Is bug 975522 really a duplicate of this? That one seems to just cover "was > a selector used or not", while this is about time spent per selector. But > maybe you plan to add more than what the description and existing patch over > there conveys...? :) No, thanks - it's not a dupe of this. I'm fairly sure, bug 834865 is what I was thinking of.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Component: Developer Tools → Developer Tools: Performance Tools (Profiler/Timeline)
Version: 12 Branch → Trunk
julien, markus: is this idea still worth keeping around, or re-filing new bugs that are actionable? The links are pretty stale to the ideas.
I think we should re-file new bugs. I'm not even sure the tool for this should live in the profiler. Maybe it should be next to selectors in the inspector. Ideas come and go, and are only implemented when we have the right project/opportunity. It rarely is useful to keep old futuristic ideas in bugzilla. We very rarely end up implementing them as such.
Let's go ahead and close this as it's not actionable, and we're tracking product work elsewhere.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 4 years ago
Resolution: --- → WONTFIX
(In reply to Greg Tatum [:gregtatum] [@gregtatum] from comment #12) > Let's go ahead and close this as it's not actionable, and we're tracking > product work elsewhere. Would be good if you pointed the followers of this bug were product work is being tracked. I believe something like this would fit perfectly into the audit mode covered in bug 1415357, but sure, it needs to be discussed first how this feature should look like. Sebastian
Performance work is tracked either in perf.html or the Gecko profiler: https://github.com/devtools-html/perf.html https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=gecko-profiler&list_id=14006296 Further venues for communication can be found at: http://firefox-dev.tools/
You need to log in before you can comment on or make changes to this bug.