For example, if your code looked something like this:
MoviePlayer1.DesktopURL = "DesktopMovie.mp4"
MoviePlayer1.MobileWifiURL = "WifiMovie.mp4"
MoviePlayer1.Play()
It was possible for the code to be sent to the browser like this:
MoviePlayer1.Play()
MoviePlayer1.DesktopURL = "DesktopMovie.mp4"
MoviePlayer1.MobileWifiURL = "WifiMovie.mp4"
In this case it was possible that the previous movie would start playing and then a new one would load because the properties were set second. Our controls were designed to handle this internally, but it made for some very hard to find bugs.
As mentioned above, starting in 2012r2, property assignments and method calls are sent to the browser in the order they are specified in your code. We suspect that this will clear up a number of strange bugs that have been reported about properties not getting set properly.
2 comments:
Indeed, it is an important correction!
Thanks for the fix! I had problems exactly like the one mentioned (with movie players playing the previously-assigned movie before changing the movie).
Post a Comment