We can now confirm the reported issue does occur on your website but could not replicate it in our test environment. Therefore believe this to be caused by some sort of conflict or interaction and advise you run a conflict assessment as described here
Let us know the outcome of that, hope it provides valuable clues.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.