#27330
It is a bug in v350 code and it seems the actual development build v351 fixes the problem. I’ve just sent it to you by email to test on your side.
A temporal v350 workaroung for the problem is to absolutely position not the image, but its enclosing DIV:
[language=xml:7ove3m5j]
[/language:7ove3m5j]
