Re: [whatwg] Asynchronous events observe unexpected states in media elements

Robert O'Callahan wrote: A related surprise is that although a media element delays the document load event until the readyState reaches HAVE_CURRENT_DATA, it is possible for a loadeddata event handler to actually run after the document load event handler. For what it's worth, there are simil

[whatwg] Asynchronous events observe unexpected states in media elements

Media element state changes, such as readyState changes, trigger asynchronous events. When the event handler actually runs, the element state might have already changed again. For example, it's quite possible for readyState to change to HAVE_ENOUGH_DATA, a canplaythrough event is scheduled, then th

Re: [whatwg] Start position of media resources

2009/4/10 Chris Double : > On Fri, Apr 10, 2009 at 11:42 AM, Jonas Sicking wrote: >> http://example.com/video.ogg#t=5s >> >> displaying the selected frame, but displaying a timeline for the full >> video and allowing the user to directly go to any position. > > For this to work with custom user in

Re: [whatwg] Start position of media resources

On Fri, Apr 10, 2009 at 11:42 AM, Jonas Sicking wrote: > http://example.com/video.ogg#t=5s > > displaying the selected frame, but displaying a timeline for the full > video and allowing the user to directly go to any position. For this to work with custom user interfaces in JavaScript, the JS nee

Re: [whatwg] Start position of media resources

On Thu, Apr 9, 2009 at 5:30 AM, Silvia Pfeiffer wrote: > On Thu, Apr 9, 2009 at 4:46 AM, Ian Hickson wrote: >> On Wed, 8 Apr 2009, David Singer wrote: >>> > >>> > Navigation outside the indicated range could be done in several ways - >>> > it does not have to be through indicating the full length

Re: [whatwg] Start position of media resources

At 22:30 +1000 9/04/09, Silvia Pfeiffer wrote: On Thu, Apr 9, 2009 at 4:46 AM, Ian Hickson wrote: On Wed, 8 Apr 2009, David Singer wrote: > > Navigation outside the indicated range could be done in several ways - > it does not have to be through indicating the full length of the > resour

Re: [whatwg] localStorage behavior when cookies mode is session-only

There's already a giant thread about this topic, I suggest you join that thread. http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-April/019238.html "Private browsing vs. Storage and Databases" Cheers, Ian On Thu,

[whatwg] localStorage behavior when cookies mode is session-only

In the W3C spec for localStorage http://dev.w3.org/html5/webstorage/#the-localstorage-attribute is said to present it (the persistent storage) the same way as cookies. There were suggestion to throw DOM_QUOTA_ERROR exception when storing to localStorage in case when cookies are in a session-on

Re: [whatwg] Private browsing vs. Storage and Databases

2009/4/9 Darin Fisher : > On Tue, Apr 7, 2009 at 6:10 PM, Brady Eidson wrote: >> >> On Apr 7, 2009, at 6:04 PM, Ian Fette (イアンフェッティ) wrote: >> >> 2009/4/7 Jonas Sicking >>> >>> I do agree that there's still need for storing data while in private >>> browsing mode. So I do think it makes a lot of

Re: [whatwg] cross-domain scrollIntoView on frames and iframes

IMHO, XPath support can be programmed into a script library; the only requirement is DOM access. Chris

Re: [whatwg] cross-domain scrollIntoView on frames and iframes

Jon Barnett wrote: Was it advertized? Not particularly. I follow Firefox closely enough, but I don't remember when XPointer was supported. If you only follow "Firefox", then you might not have have noticed it anyway. XPointer support for anchor scrolling was added to Gecko in March 2003

Re: [whatwg] cross-domain scrollIntoView on frames and iframes

On Mon, Apr 6, 2009 at 3:51 PM, Jonas Sicking wrote: > >From my point of view I'm not sure how interesting this whole feature > is. We had support in firefox for XPointer for many years and saw > little to no uptake. I'm not sure if anyone complained when we removed > the support even (which woul

[whatwg] optgroup element used for selection

Currently (HTML4.01) and in the near-future HTML5 spec optgroup elements are used to group options (hence the name :-) and amongst others allow us to disable a group of option elements at once. Personally, I think it would make sense to add the ability to make an optgroup selectable. The result

Re: [whatwg] Start position of media resources

On Thu, Apr 9, 2009 at 4:46 AM, Ian Hickson wrote: > On Wed, 8 Apr 2009, David Singer wrote: >> > >> > Navigation outside the indicated range could be done in several ways - >> > it does not have to be through indicating the full length of the >> > resource in the timeline. >> >> surely.  but whic

Re: [whatwg] Private browsing vs. Storage and Databases

On Tue, Apr 7, 2009 at 6:10 PM, Brady Eidson wrote: > > On Apr 7, 2009, at 6:04 PM, Ian Fette (イアンフェッティ) wrote: > > 2009/4/7 Jonas Sicking > >> >> I do agree that there's still need for storing data while in private >> browsing mode. So I do think it makes a lot of sense for >> .sessionStorage t