No description provided.
Wouldn't it make more sense to put this logic inside the changeCurrentTime function?
have to agree, this makes more sense as a first check inside changeCurrentTime. The "set" is an implicit request to attempt a timechange, changeCurrentTime can then decide not to change it if it's the same as what it is right now. Although, that said, this check might not even be necessary; returning early means the seek events never fire. Technically correct but possibly not in the spirit of explicitly setting a currenttime
same comment here. This bypass is probably not a good idea. What aspect of the bug did this solve?
[#968874] Disable keyboard controls on YouTube by default.
[#968874] Do not change time if time is already changed because we do…
…n't want to fire seeked events when we don't actually seek.