W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 12541] <video> Media Element seeking: the asynchronous behaviour of steps 5-12 causes unexpected, unwanted behaviour when getting the currentTime immediately after it's been set.

From: <bugzilla@jessica.w3.org>
Date: Mon, 01 Aug 2011 21:19:51 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qnztv-0001BT-Op@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12541

--- Comment #9 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-01 21:19:50 UTC ---
We can't set currentTime once only, since some UAs can't know ahead of time if
the stream is seekable.

What we _could_ do is have currentTime get set immediately, and then adjust
itself asynchronously if the seek is not possible.

That would basically be the same as now except that the attribute does get set
straight away. In most cases that would mean it seems synchronous. In cases
where seeking to the given time doesn't work, it would mean the attribute
changes twice, so you could still find that immediately after setting it it
doesn't have the same value in one UA as another. (Then again, that's always
going to be true modulo bug 12267.)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 1 August 2011 21:19:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:15 UTC