This content has been marked as final. Show 2 replies
I can confirm the same behavior on our site.
For our implementation I will open a new case with support.
Support passed it on to development.
So I hope they come up with a bugfix in a future release