I can confirm that this is a nuisance and it would be nice to have this smaller as suggested.

I totally agree. I think a confirmation could (should) appear in a designated area and not be modal.

I hope that there can be a special place for that, which expands when needed and disappears after some seconds.

@JHoeck i still have this issue .

Maybe move the alert inside flow ?

Hi DenisChenu,
maybe move it up to the top of the page is enough. I would assume it's unlikely, that people will click on anything in the top navigation after saving the question.
(Also, I do not understand what you might mean by "alert inside flow").

inside : floaw , see screenshot.

Inside the content, take place

Capture d’écran du 2020-04-20 08-52-43.png (43,197 bytes)   

Capture d’écran du 2020-04-20 08-52-43.png (43,197 bytes)   

I hope that there can be a special place for that, which expands when needed and disappears after some seconds.

I prefer to have a "close" link, not disapeear, but it's a personal opinion, and if it can be impoved to have a user option.

Hi
thanks for the image.
I am not sure about a close link (X on the right) or an automatic close. As one might continue working on the question, this question has been changed and is not saved in that current state. A close link might make users forget that the question has not been saved.
Also: What if a user saves again - how does he know, that his last changes have been saved (and it's not only an old message still showing).
This makes it appealing to me to have it disappear automatically. Of course there can be an additional X in the corner to quickly get rid of the message.

I didn't like the autohide when in flow : because if you have already your mouse on a button : the button move :)

Currently : when there are error : it's hard to copy paste the text :)

A close link might make users forget that the question has not been saved.

But if auto hide : you are not sure user see it :)

Autohide is the current way I believe. I agree, that the user might not notice. But as the user has just clicked on SAVE he will probably assume that something happens.
Right now the user waits (dots on screen while saving) for the message. I would think this is not different when autohide would be use in future (well, it could flash 3 times or so).

fixed in 4.4.0 rc1