Got a fun one, I think.
Consider a simple action that fast-forwards a 360video to 100% via .seek(100%)
<action name="gotoend">
callwhen(plugin[videoplayer].loaded,
trace('goto end');
plugin[videoplayer].seek(100%);
);
</action>
Using OS X, under any browser, this fires off seamlessly, the trace traces & the seek seeks to 100%.
Using Windows 10 Pro, under any browser, the trace traces BUT the seek does not seek. It stays at the current position ( beginning / 0% ), with no error being thrown.
Anyone else notice this?