Re: Getting an implementation report from WebKit

On Wed, Jan 25, 2012 at 4:14 AM, Eric Carlson <eric.carlson@apple.com> wrote:
>  I think it does make sense to expose the end time to the DOM somehow. I didn't add it because I wasn't completely comfortable with a read-only attribute that automatically changes as soon the current time exceeds it.
>
>  On the other hand, that is how the time behaves and I don't have any great ideas.

I'm not sure of the best approach either. The main reason I exposed it
was to allow the controls to access it to show the fragment positions.
Our controls are implemented using the standard DOM API. In the end we
didn't land the UI side of the fragments so it wasn't used, but it's
there for third party control implementations, and for when we add
support to the UI.

-- 
http://www.bluishcoder.co.nz

Received on Wednesday, 25 January 2012 22:52:09 UTC