After some testing, it turned out the issue was a conflict with a particular setting in a W3 Total Cache extension. It wasn’t present before the latest update, so I guess the conflict is somewhere there. @mvi, @webdesignphx, hope that helps you narrow it down with your issue.
Thank you, Kriesi team for the support.
Thank you, @Yigit,
I’ll test it on the parent theme to see if it’s related to this.
I’ll be watching the forum to see if similar issues / solutions pop up.
Best regards,
Kaloyan