Quick update on our side: I have retested on the latest 3.2.6 image and the issue no longer happens. I get the same behavior as in Chrome/IE now. Must have been fixed between 3.2.5 and 3.2.6
Quick update on our side: I have retested on the latest 3.2.6 image and the issue no longer happens. I get the same behavior as in Chrome/IE now.
Must have been fixed between 3.2.5 and 3.2.6