Chris, should we add more details to help CPU profiler users migration.

This bug reflects my gripe about having the CPU profiler warning on the Performance panel.

The CPU Profiler was located on what is now the Memory panel. It was removed from that panel because it's not related to Memory analysis, and because of duplicate functionality (everything you can do with the CPU Profiler, you can do with the Performance panel).

The warning should be located where the feature used to be located. That's where users are going to say "huh? what happened to the CPU profiler?"

It doesn't make sense to have it on the Performance panel. Look at how it confused the reporter of this bug. Having the warning on the Performance panel makes it seem like CPU profiling has been removed from the Performance panel

If we have a Help Center article that explains the migration, it makes sense to link to it in the deprecation warning. Let's add a "Learn more" link at the end of the first paragraph that links to https://developers.google.com/web/updates/2016/12/devtools-javascript-cpu-profile-migration .

@Kayce: The rationale was that if a developer were looking for the CPU Profiler, could no longer find a Profile tab, and were presented with the new choices of "Performance" and "Memory", they would visit "Performance" first. CPU profiling is about measuring performance, after all. The only risks would be if:

a.) They navigated those tabs spatially (i.e. Memory is in the same "place" as Profile was)
b.) They were on the Memory tab when they last opened DevTools before the update
c.) They judged each option by its "shape" (i.e. the Memory panel looks more like the old Profile panel)

(a) and (b) seemed extremely unlikely, and even in the event of (c), the next choice would be to open the Performance panel, which would provide the explanation. But, if we want to hedge our bets, we could include the warning on BOTH panels.

@alph: How much effort would it be duplicate the warning on the "Memory" panel? It could appear between the list of radio buttons and push buttons, and would need slightly different language (i.e. the first paragraph would be "The functionality of the JavaScript CPU Profiler has moved to the new Performance panel. _Learn more_").

That rationale makes sense, thanks. I definitely fall in the camp of (c), i.e. judging each option by its "shape".

Maybe the warning on the Performance panel should be more explicit about which feature has been removed. If I'm reading the reporter's original post correctly, the reporter thought that JS profiling had been removed from the Performance panel.

These are too verbose, but I would communicate the changes like this:

Warnings on Memory panel:

"This panel was previously called the Profiles panel. The "Record JavaScript CPU" feature that was previously on this panel has been moved. Learn more."

Warnings on Performance panel:

"The "Record JavaScript CPU" feature that was on the Profiles panel in previous versions of Chrome has been moved. You can use this panel to profile JavaScript. Learn more."

I'm okay with making this warning shorter, especially if there's now a Help article that explains the change (with visuals).

I'd cut even more aggressively:

Memory panel:
"The Memory panel provides features formerly found in the Profile panel. JavaScript CPU profiling has moved. _Learn more_"

Performance panel:
"The Performance panel provides features formerly found in the Timeline panel. You can use this panel to profile JavaScript. _Learn more_"

I think this will also help address Brain's issue with the warning being too prominent.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/03c41c3afff86bdc441eb093749f4b2a4f6056b0

commit 03c41c3afff86bdc441eb093749f4b2a4f6056b0
Author: alph <alph@chromium.org>
Date: Wed Mar 22 22:13:49 2017

DevTools: Add a link to JS CPU profiler migration notes.

BUG= 690460 

Review-Url: https://codereview.chromium.org/2764123003
Cr-Commit-Position: refs/heads/master@{#458893}

[modify] https://crrev.com/03c41c3afff86bdc441eb093749f4b2a4f6056b0/third_party/WebKit/Source/devtools/front_end/timeline/TimelinePanel.js

@kayce Sorry for the late reply, but my misunderstanding that led me to file this was that I thought the ability to attribute CPU usage had been removed entirely.

@chowse Yes, your proposed rewording would have prevented my misunderstanding.  What I'm currently seeing in the attached screenshot would also have prevented my misunderstanding.

Thanks so much for being responsive.  I'd read the post announcing this change back when it was posted, but was surprised and confused when it actually happened.  The new UI is (in my opinion) much better.

Deleted: Performance panel explanation.PNG 34.9 KB

	Performance panel explanation.PNG 34.9 KB View Download

@alph: are we done here?