>>! In T44138#3578131, @Jan_Dittrich wrote: 
> @Pginer-WMF – what do you think? And: Who is the one to decide about this?

I'm not convinced this would improve much. I'm ok with experimenting, but given the importance of the publishing workflow I'd like to have a clear hypothesis of what we expect and how to observe the impact of the change. More details below:

**On the need to communicate additional steps**

Ellipses may help to emphasise that the publishing process have multiple steps. The key question is whether we need to anticipate such information. There are many processes that require some kind of confirmation/follow-up step that users see as a logical progress to completion, and do not cause any kind of confusion or surprise despite those extra steps not being anticipated. For example, I don't think that adding ellipses to all actions that open any kind of panel such as "add link" or "insert image" would improve things much.

I'd like to understand better the specific issues that the uncertainty about "whether the save button saves immediately" generates. What do we expect users to do differently if they know there are more step behind the button?

The ellipses make also the call to action less strong. In addition, ellipses in buttons have been also used to communicate an action being performed (e.g., a "Save" button turning into "Saving..." after being pressed), so there is a risk of confusion for users thinking some publishing action may be going on that we may want to check.

**Connection with "preview" issue**
If the proposal is intended to improve the issue with preview (T155732), which some comments in this ticket still refer to, I don't think it will help much.

My understanding of the preview issue is that some users don't see "preview" necessarily as an intermediary step in their way to publishing. That is, some users understand preview as away to check that their recent editing actions produce the expected result before continue their editing session. Since they are not completing their editing session, it is not obvious that preview will be behind the "publish" path. We are supporting well the scenario of "preview in your way to publish" but we may not be doing so well with the "preview as you edit". 

Ellipsis help to emphasise that the publishing process has multiple steps. However, is surfacing that the publishing process has multiple steps going to solve the above issue? I don't think so. Since users in that context are not interested yet to go into the publishing path, they are unlikely to explore that way to check if they find functionality that they don't consider connected to it, being it "preview" or "print".