Status: Unconfirmed Owner: ---- Labels: Type-Bug Pri-2 Area-Undefined New issue 31512 by megazzt: console.profile does not output to console or indicate it has worked http://code.google.com/p/chromium/issues/detail?id=31512
Google Chrome 4.0.266.0 (Official Build 33992) WebKit 532.6 V8 2.0.3.1 User Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.6 (KHTML, like Gecko) Chrome/4.0.266.0 Safari/532.6 What steps will reproduce the problem? 1. Use console.profile and console.profileEnd in a webpage What is the expected result? Developer Tools should pop up (or at least switch tabs if it is open currently) in the Profiles tab to show that it is starting/stopping profiling. And/Or a message should be printed to the console on start/stop to indicate that profiling is indeed occurring. What happens instead? Nothing appears to happen. It is not clear until you view the Profiles tab and see the generated profiles. This was confusing to me at first. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
