Getting started actions should account for actions from the UI

[miguelsolorio]

1. Create codespace
2. Terminal is open by default
3. Navigate to "Ports" view
4. 🐛 Getting started displays the "view ports" step as incomplete

I didn't use any commands and the "port" view was already moved into my panel. Also, I had already ran actions in the terminal as well so that step should checked.

fyi @digitarald

[JacksonKearl]

It only checks off by running the command right now, so if you open it from the UI it wont (but if you use the keybinding it should). Since we now support manually clicking the item to check it off do you think we need to also have a way to listen in to clicks for automated checking off?

[miguelsolorio]

Ideally it would check off no matter what route you take, that gives you a nice overall experience. When I went through this step, it felt like a bug that it wasn't checked after I navigated to it.

[digitarald]

In cases where the UI is already visible I also thought to use when clauses to hide the task. The buttons for those cases will always be a bit awkward, as the click will not have any visible reaction; and the user already has found the UI without help from the walkthrough.

Alternatively, a task could also highlight a related UI element; something we discussed in the past that makes it easier to use walkthroughs for UI tours.

[miguelsolorio]

I don't think we want to hide items when they are visible, in my case the terminal was already open and then I clicked on the "Ports" panel. It's more about providing different avenues for the user to complete the task.

[digitarald]

Right, I was mixing up issues here! Agreed that these kind of UI tasks should still be checked off even when not using the given command.

[miguelsolorio]

Created #120147 to track exploring hints, with I discussed with Kai today

[JacksonKearl]

Duplicate of #122570