On leopard, with Safari 3.1, viewpoint is causing an infinite loop of the page reloading trying to notify me that I need viewpoint. I can see two or three of the viewpoint installation frames and they keep refreshing and loading over again, infinitely until I close the window.

I just installed the latest player from here:
http://www.viewpoint.com/dc/

On the project we are working on we are using the latest 5.0.2.29 version of MTS3Interface.js, also found on viewpoint.com/dc

I tried to find some viewpoint examples, of which there are none anymore on viewpoint.com (which worries me a little), and the ones I came across caused the same error:
http://automobiles.honda.com/certified-used/2006/accord-coupe/gallery.aspx

Is this a new bug caused by a safari update, or something specific to my machine?
Viewpoint works on this machine in firefox, and if I use the developer tools to set my user agent in safari to firefox, it works fine as well. Definitely a detection error.

Can anyone confirm or deny, and possibly offer a solution?

Thanks
-matt

I am sorry to inform you that we are unable to support the new release of Safari at this time. We are working on an update which will resolve the problems you are having with our online Installer. Please look for an updated release in the future on http:/developer.viewpoint.com
In the mean time if you are developing content you can use sniffer code to exclude Safari 3.1 so that users do not experience the broken NE Installer in Safari 3.1 on Mac or PC.

just came across the same thing.

Thank God none of my clients have come across this yet - it is a major **** up. I guess I had better work out a bit of sniffer code.

Barnaby

I noticed that commenting out this line in the MTS3interface.js seems to stop the problem...

if (VET_Safari && document.addEventListener)
// COMMENTING OUT THE NEXT LINE SEEMS TO 'FIX' SAFARI 3.1 BUG
// document.addEventListener("DOMContentLoaded", VET_MTSUnsupported, false);

of course commenting out the line before might have been a good idea too.

Thanks Barnaby,

We experienced the same problem, that fix seems to have worked perfectly!

This message has been edited. Last edited by: S.T.,