We won’t bring the floating mode back, but I will add automatic show/hide option after my vacation till Monday.
to be honest, I’ve thought all the time, “floating mode” would be the right term for “automatic show/hide option” … 
OK, what I really wanted all the time was and is the “automatic show/hide option”.
Thank you very much for the promise to bring it back! 
Yes, I’ve read your mind.
Congratulations Code-Jack! 
It’s everything you ever dreamed of
Ok, so the thing is that “Floating mode” never existed in the first place.
Floating mode involves UI elements that can be moved around the screen. Users have direct control over these elements, deciding where they want them placed.
We never had this option, so it was auto show/hide all along.
Nevertheless, that’s odd that Anytype talk about it everywhere as “floating mode” if it’s not. And that’s still concerning that you remove the Auto show/hide feature for now reason… More and more people are talking about a UX design problem, and I must admit I don’t blame them.
You could move it around and even snap to the right side. This is 0.41.1 on the video. Snap to the right side was removed several versions before since the design team didn’t like it.
So, you are wrong.
Indeed, my bad.
A new update with auto-hide, cool!
Even though I had just decided to share a CSS auto-hide version for the space bar 
:
CSS does not allow coordinate threshold and timeouts.
It’s for me?
I don’t need “coordinate threshold and timeouts”, I want autohide this space menu with a quick and easy hover action. And CSS do what I want, without the need for coding nor designer approval because it’s client side (thanks).
I think it might interest some people, so I’m sharing. Those who want it can use it, those who are looking for something else can’t :).
And my example needs to be improved, with animations for example.
(it has nothing to do with a floating mode but the term was misused on this post I think)
Thanks for the new version, @Razor
Soo much better then the last versions!
Although … there is one detail not as good as expected:
The menu disappears too slow.
It should disappear instantaneously when the mouse leaves the menu.
The delay ruins the feeling of a quick workflow.
Could you please completely remove that delay?
While I don’t need this change, I must agree with you that if I were using the spaces bar, it would be way too slow for a comfortable usage.
Just commenting to say the sidebar feels perfect to me now - thank you for that!
@Angelo Who is responsible for having indicated that this FR was now Feature Life/Implemented when it certainly is not?
The auto-hide function was re-implemented in the last release. The request for the Spaces Widget is a different matter, though. Our product team only accepts dedicated requests, so a separate FR needs to be submitted just for the Spaces Widget.
There are several already for making widget more flexible:
I understand, but the title of this FR isn’t about Auto-hide function, it’s about floating mode. Currently, the content of an Object is resized everytime the sidebar is collapsed or expanded. The wish is to get back the sidebar over the content, not making it bounce everytime.
So this FR isn’t implemented at all.
That’s fair for the Space widget as a separate FR, even though this need has been sufficiently debated and demonstrated IMO for the last few weeks.
That specifically is a good example of a lacking aspect of the Anyteam communication. Explaining after a while if you reject a request or not and why. Currently, your communication just holds us blindly to many subjects, hoping to see improvements or features that may never be accepted or impemented. It’s quite sad.
The roadmap is good, but it represents 1 hundredth of the requests. For the rest, we’re in the unknown. So it would be wise to start thinking about communication in the image of your ideal, which is Open-source 
Morgan, my title was wrong, that’s all, see this post.
Therefore my request was fulfilled.
(I didn’t see the need to edit the title after it was clear that I’ve used a wrong term.)
Also see this detailed post from @anton as well as this post from @Razor.
Razor gave many answers in this thread, also did anton explain why there will be no floating mode. The communication in this thread was very well, so I can’t see why you complain about lacking communication in this thread?
I would say: the problem is only that the day has only 24 hours.
Two team members have spent some time here in this thread alone to communicate with us, as well as fulfilled the request!
That deserves a best note in my opinion!
I’m always surprised, how many posts Razor seemingly reads - not only the BR’s and FR’s - and gives answers. And that even on weekend or late in the evening!
But you can’t expect that he or the other team members give answers to every single post in this whole forum.
It feels unfair to me if you blame them for lacking communication.
One can find in deed a few examples for lacking communication in the thousands of threads, but not here in this case and also not in most cases.
I would say, you expect a bit to much. As already mentioned: the day has only 24 hours.
And it is surely better if the team mainly does the work to make the product better, instead of discussing things over and over - often enough in different threads parallel.
Yes, but your mistake is indeed an actual FR for me 
Either the title had to be renamed to make this Topic Implemented, or removing this tags, but there is a choice to make, otherwise, members with the same need that me, will make the same assumption, that should be obvious.
I don’t, I speak about the vast majority of FR, and a clear development status, consideration of the FR or not.
That is not what I suggest, I think every singles FR should indeed have some sort of status to indicate to us what is the Anyteam consideration about them. Rejected, accepted, will be implemented in long term or not.
All this could be just done with a simple tag system, no need for the Anyteam to ever discuss the status of their decision.
Agree, pehaps simply rename this FR to prevent other users from making mistakes?