Hi @Alexandru @Edith1
It’s a known issue on iOS Safari 26, and we have reported the issue to Apple.
Thanks Vic