It would be nice if OctoPrint shows somewhere the baudrate of the connection when it is used in the auto mode, because now it is not possible (at least I didn't find a way how to) get the current baudrate. For example as a tooltip on the "Disconnect" button the connection panel, or somewhere in the terminal tab.

Partially implemented as a side effect of the fix/implementation of #2740. The commit above fully implements it that the current settings are now reflected in the selection boxes after a connection has been established:

Pushed to maintenance, soon devel, to be released with 1.3.10
Thanks, but recently I've updated my OctopPrint to the version 1.3.10rc2 and I still can't see the current baudrate/port after connecting with the AUTO setting. According to the changelog, it should be part of 1.3.10rc1 or am I wrong?

You aren't wrong and that should be implemented. The problem is that it works here, both of these were set to AUTO before connecting:

Does it work in safe mode? Have you tried clearing your browser's cache?
Ooooh, wait. Did that connection happen through auto connect on server startup or through a manual connect?
It was a manual connect. See my video (recorded in the incognito mode, so it can't be caused by the browser's cache) https://gyazo.com/d9114fd8ac759e6e09ca217da04b08c2 Also, I am able to replicate it on two different computers and browsers (Safari and Chrome),
This not working under 1.3.10 is still unreproduced. Marking as such.
I'm experiencing the same issue even in safe mode. I'm on OctoPrint 1.3.10 running on OctoPi 0.15.1
Can I provide you further information to help you?
@Edo78 exact steps with which you experience this issue. The more details the better. I still cannot reproduce this.
I did nothing special:
I even tried the incognito mode in chrome but I stile get AUTO/AUTO.
If I set the proper values then I see them, otherwise it's always been AUTO/AUTO
Now that was weird. I couldn't reproduce it at all - until today. Now I finally could reproduce it and looking at the code have no idea why it ever worked for me to begin with. I'm... very confused by this 馃え
In any case, I hope the above commit now fixes it for good - it does for me. Already pushed to maintenance, soon devel, to be part of 1.3.11.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
Now that was weird. I couldn't reproduce it at all - until today. Now I finally could reproduce it and looking at the code have no idea why it ever worked for me to begin with. I'm... very confused by this 馃え
In any case, I hope the above commit now fixes it for good - it does for me. Already pushed to
maintenance, soondevel, to be part of 1.3.11.