This issue has been resolved - it turned out it was not specific to the DotNetGallery as I eventually managed to duplicate it in another page.

 

I still don't know why it was happening but we've managed to work around the issue.