You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, the spec says to update the currentTime asynchronously, so attempting to get the currentTime immediately after it's been set will return an incorrect current time. Firefox was the only browser to implement this per_spec the others kept an internal timer cache to ensure the correct currentTime was always returned.
Submission to follow
The text was updated successfully, but these errors were encountered:
@jdalton - turns out this isn't quite as straight forward to test for as I initially thought it might be. Time permitting, I'm going to ping you on IRC tomorrow to go over where I'm at, maybe you'll have some ideas or see something from a different light then I am.
Basically, the spec says to update the currentTime asynchronously, so attempting to get the currentTime immediately after it's been set will return an incorrect current time. Firefox was the only browser to implement this per_spec the others kept an internal timer cache to ensure the correct currentTime was always returned.
Submission to follow
The text was updated successfully, but these errors were encountered: