We are working on a webplayer Unity project that has been in development for some time, and relies heavily on Javascript for communication between the Unity object and a set of JS functions. This goes through the normal ExternallCall/SendMessage technique explained here: http://unity3d.com/support/documentation/Manual/Unity%20Web%20Player%20and%20browser%20communication.html
Since last week, this seems to no longer work on Chrome. We didn't change anything to our code; it's the same build. Firefox, IE, Safari still work fine; Chrome gets stuck at the initialization step in our game where the browser <-> unity communication happens through Javascript.
Has anyone else had this issue on Chrome, and is there a known workaround? Thank you.