Improve discoverability of 'Restart Frame'

[weinand]

[isidorn]

Currently we show the restart frame in the context menu when the debug adapter supports the restart frame request.
However we show this on every stack frame in the call stack. For node I get an error whenever I try to execute this command on any stack frame that is not top level.

1. Should we show this action only on the top stack frame? Since it does not make a lot of sense to me that a user can restart any other stack frame than the top

How to improve its discoverability? My idea is the following:

• Similar to the inline thread and session actions in the call stack view, we would on hover and focus render a restart icon. It would be rendered instead of line and column infomation. In case we go down this approach we would could use our old restart icon, or a new one to distuingish that this does not actually restart the whole program. So the icon should have a meaning of "mini restart" @misolori

Let me know what you think Andre Weinand (@weinand) roblourens Connor Peet (@connor4312)

Pic for reference of inline session actions. However for stack frame we would just have one for now

[connor4312]

Showing it on hover makes sense to me. My once concern would be accidentally clicking it since it's a new clickable area that shows up only on hover. Maybe having the icon to the left of the location would be less likely to have misclicks (i.e. left of "_onPaused")

Being in or beside a stack frame the standard restart icon conveys the message to me. Or alternately something like this would also work:

[isidorn]

Fancy design skill and a good idea.
Let's see what others have to say. New icon, or old icon + hover text explanation

Having the action left of the tree item is not really aligned with what we do in other parts of our UX (open editors being the only exception). And I am not worried about people accidently clicking on it, since that area is not really clickable so far (why would a user click there)

[miguelsolorio]

This is merely for illustration purposes, but something like this?

[isidorn]

@misolori that is pretty awesome

[isidorn]

I have pushed a change to show the restart frame icon on hover and on row focus. When the adapter does not support restartFrame action everything behaves as before. So on hover no change

Some follow up work:

1. @misolori once we have a new icon can you just update the codicon used here
2. Andre Weinand (@weinand) roblourens Connor Peet (@connor4312) can we decide if we need this action for not top stack frames. In theory this makes sense, however I am not sure if debuggers can support this in practice. Currently node2 throws an error when trigged by the user. It could instead restart the top frame instead or we show the action as disabled (would need to be contributed by the adapter)
3. @misolori once I focus on the action, it jumps up a bit. And stays vertically not centered. I believe this is nothing special for this icon, but a general codicon action bar issue. Can you look into this ( I can also create a new issue)

Try it out and let me know how you feel about it. Thanks!
I had an alternative solution where I would just hide the line numbers (and still show the filename) for the action but after discussion with Andre Weinand (@weinand) we decided on the curren solution

[connor4312]

It looks like the chrome devtools can, so in js-debug/PWA we should be able to restart frames anywhere in the current stack. But with async stack traces we won't be able to restart frames that happened on a different stack that the current one (even though it's displayed as the 'same' call stack in the UI).

I think it would make sense for a 'restartable' flag to to be annotated on stack frames sent back down the DAP. And other languages might only be able to restart the top stack frame / only be able to restart under certain conditions.