Re: [whatwg] Apple Proposal for Timed Media Elements

2007-10-12 Thread Ian Hickson
On Thu, 5 Apr 2007, L. David Baron wrote: > > So why not give 'media-loop-start-time' an initial value (traditionally > called 'auto') that makes it use the value from 'media-start-time', > rather than forcing the author to specify the same thing twice for the > normal case? (And likewise for

Re: [whatwg] Accessibility and the Apple Proposal for Timed Media Elements

2007-10-12 Thread Ian Hickson
On Thu, 5 Apr 2007, Benjamin Hawkes-Lewis wrote: > > There are three things I'd hope to see from a element: > > 1) Ease of use compared to (A common API contributes to this, > and v2 might approach it with a default UI. Lack of agreement on a > baseline format is a major problem here.) We no

Re: [whatwg] Media protocols and state

2007-10-12 Thread Ian Hickson
On Mon, 2 Apr 2007, Kevin Calhoun wrote: > > I've been evaluating the behavior of the HTMLMediaElement in the current > working draft in light of the various network protocols and player > behaviors that I'm familiar with, and I think the current specification > of loading behavior and the defin

Re: [whatwg]

2007-10-12 Thread Ian Hickson
On Fri, 23 Mar 2007, Nicholas Shanks wrote: > > How about: > > > Audio fallback > Video fallback > > > User agents that don't support playlist, audio and video just get an ordered > list of fallback text. > UAs that do support them also benefit in being able to negotiate each varia

Re: [whatwg] Apple Proposal for Timed Media Elements

2007-10-12 Thread Ian Hickson
On Fri, 12 Oct 2007, Dave Singer wrote: > > I (we) agree completely that accessibility is both important and should > be explicitly addressed in the spec. I don't think it makes sense to > talk only about one kind, however. We've sent a previous email > outlining how a user could express thei

Re: [whatwg]

2007-10-12 Thread Ian Hickson
On Fri, 23 Mar 2007, Anne van Kesteren wrote: > > I don't really like this element. The name is confusing especially with > an attribute named src="". It also introduces yet another void element, > can't we just reuse ? The value="" attribute of would > point to a resource and the type="" attri

Re: [whatwg] , , Timed Media Elements -- Part I SMIL

2007-10-12 Thread Ian Hickson
On Thu, 22 Mar 2007, Dan Brickley wrote: > > I've not followed it, ... but there's a SMIL subset integrated with > XHTML at http://www.w3.org/TR/XHTMLplusSMIL/ ... if you find SMIL too > large, perhaps this or another profile is less intimidating? This profile doesn't seem to define error handli

Re: [whatwg] , , Timed Media Elements

2007-10-12 Thread Dave Singer
At 0:34 + 13/10/07, Ian Hickson wrote: On Thu, 22 Mar 2007, ddailey wrote: As a newcomer to this group, please forgive my ignorance of discussions that, undoubtedly, have already taken place, but as I have been reading these threads on and timed media and , a couple of questions have

Re: [whatwg] Apple Proposal for Timed Media Elements

2007-10-12 Thread Dave Singer
At 0:30 + 13/10/07, Ian Hickson wrote: On Thu, 22 Mar 2007, Dave Raggett wrote: From an accessibility perspective the proposal lacks support for captioning. There should be a mechanism for enabling/disabling captions to avoid disadvantaging people who have difficulties with hearing the

Re: [whatwg] Apple Proposal for Timed Media Elements

2007-10-12 Thread Ian Hickson
On Thu, 22 Mar 2007, Nicholas Shanks wrote: > > Volume has the range 0-100 in the DOM interface, but 0.0-1.0 in CSS. These > should be consistent (I favour zero to one and allowing percentages). The spec now uses a float and 0.0 .. 1.0. > I think that the ERROR state attribute should have a val

Re: [whatwg] , , Timed Media Elements

2007-10-12 Thread Ian Hickson
On Thu, 22 Mar 2007, ddailey wrote: > > As a newcomer to this group, please forgive my ignorance of discussions > that, undoubtedly, have already taken place, but as I have been reading > these threads on and timed media and , a couple of > questions have come to mind: > > 1. why not just incl

Re: [whatwg] Apple Proposal for Timed Media Elements

2007-10-12 Thread Ian Hickson
On Thu, 22 Mar 2007, Dave Raggett wrote: > > From an accessibility perspective the proposal lacks support for > captioning. There should be a mechanism for enabling/disabling captions > to avoid disadvantaging people who have difficulties with hearing the > audio. It should further be possible t

Re: [whatwg] Apple Proposal for Timed Media Elements

2007-10-12 Thread Ian Hickson
On Thu, 22 Mar 2007, Sander Tekelenburg wrote: > > > > > > I'm worried about "The controller attribute is a boolean attribute. If > the attribute is present, the user agent must display a user interface > which allows the user to control

Re: [whatwg] Offline Web Apps

2007-10-12 Thread Robert O'Callahan
On Oct 12, 2007 9:39 PM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > On Oct 11, 2007, at 6:47 PM, Robert O'Callahan wrote: > > On Oct 12, 2007 12:53 PM, Ian Hickson <[EMAIL PROTECTED]> wrote: > > > The problem with isLocallyAvailable() -- as noted by Maciej on IRC -- is > > mostly one of race c

Re: [whatwg] element comments

2007-10-12 Thread Ian Hickson
On Sat, 4 Nov 2006, Anne van Kesteren wrote: > On Sat, 04 Nov 2006 07:37:32 +0100, Ian Hickson <[EMAIL PROTECTED]> wrote: > > > > > > * It should probably mention 'img.src = foo' (that loading directly > > > starts). I thought that 'img.setAttribute("src", foo)' even did > > > different things in

Re: [whatwg] Offline Web Apps

2007-10-12 Thread Maciej Stachowiak
On Oct 12, 2007, at 12:16 PM, Ian Hickson wrote: On Fri, 12 Oct 2007, Maciej Stachowiak wrote: The race-free approach would be to provide APIs to load resources only from the cache and to error out immediately if the the request can't be served locally. That's what the offline caching

Re: [whatwg] Apple Proposal for Timed Media Elements

2007-10-12 Thread Ian Hickson
On Wed, 21 Mar 2007, Robert Brodrecht wrote (in response to Apple's proposal, quoted): > > > > If the presentation of timed media by the user agent has been disabled, if > > the resource has an unsupported type, or if the preparations for its > > presentation fail either because of a protocol fai

Re: [whatwg] Apple Proposal for Timed Media Elements

2007-10-12 Thread Ian Hickson
On Wed, 21 Mar 2007, Robert Sayre wrote: > > My two cents: we should put off events and other API pieces that address > editing applications. It is possible to write web versions of things > like iMovie and SoundEdit in Flash right now, but I don't think it is > realistic to capture that stuff

Re: [whatwg] Bookmarking videos

2007-10-12 Thread Ian Hickson
On Wed, 21 Mar 2007, Kornel Lesinski wrote: > > This however is a little help to users who want to bookmark videos or > share links to certain parts of them - without a standard way of doing > it UA's won't be able to provide UI for it. Even if you implement that > for yourself using UserJS, yo

Re: [whatwg] Full screen for the element

2007-10-12 Thread Ian Hickson
On Wed, 21 Mar 2007, Kornel Lesinski wrote: > > Couldn't this be protected in a similar way pop-up blocking works? If > not, browsers could simply display confirmation dialog box before > entering fullscreen (some sort of protection is neccessary to protect > against phishing and annoyance). T

Re: [whatwg] Full screen for the element

2007-10-12 Thread Ian Hickson
On Wed, 21 Mar 2007, Martin Hassman wrote: > > I feel conflict here: > > a) UA provide some Fullscreen item in popup menu (from the discussion > seems for me that there shouldn't be any UA-GUI in page than popup menu) > b) web author give some Fullscreen button inside his video controls (to >

Re: [whatwg] Full screen for the element

2007-10-12 Thread Ian Hickson
On Wed, 21 Mar 2007, Mihai Sucan wrote: > > Shouldn't the video API include a way to toggle full screen on/off? This > is a rather basic feature of videos. If it will not be available, video > sites will hack around missing full screen support. > > The current spec doesn't define it. Currently

Re: [whatwg] Comments/questions on 4.6 Offline Web applications

2007-10-12 Thread Ian Hickson
On Fri, 12 Oct 2007, Adam Roben wrote: > > > > (Now step 20.) It does. Which is to say, it being on the online > > whitelist has no effect. Should it have an effect? We can omit the > > caching of such files if you want. > > Given that section 4.6.5.1 says that resources in the online whitelist

Re: [whatwg] Offline Web Apps

2007-10-12 Thread Ian Hickson
On Fri, 12 Oct 2007, Maciej Stachowiak wrote: > > The race-free approach would be to provide APIs to load resources only > from the cache and to error out immediately if the the request can't be > served locally. That's what the offline caching system does right now for any URI not on the whit

Re: [whatwg] database full error (was: Re: executeSql API is synchronous)

2007-10-12 Thread Scott Hess
On 10/12/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote: > On Fri, 12 Oct 2007 20:46:52 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote: > > Certainly that would be reasonable. I have added it. People should let me > > know if they want me to remove or add error codes, by the way. > > I think there s

[whatwg] database full error (was: Re: executeSql API is synchronous)

2007-10-12 Thread Anne van Kesteren
On Fri, 12 Oct 2007 20:46:52 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote: Certainly that would be reasonable. I have added it. People should let me know if they want me to remove or add error codes, by the way. I think there should be an error code for the database being full. For some platf

Re: [whatwg] executeSql API is synchronous

2007-10-12 Thread Ian Hickson
On Tue, 25 Sep 2007, Maciej Stachowiak wrote: > > I agree that the actual I/O to the database should be done up front. > However, it should be possible to make the conversion from SQLite's > native data types to JavaScript datatypes lazy (such type conversion can > have nontrivial cost, especia

Re: [whatwg] Comments/questions on 4.6 Offline Web applications

2007-10-12 Thread Darin Adler
On Oct 12, 2007, at 9:42 AM, Adam Roben wrote: Darin Adler wrote: On Oct 12, 2007, at 6:11 AM, Adam Roben wrote: It may be worth stating in this section what the behavior is when a section or opportunistic caching namespace appears multiple times. The parsing algorithm makes this clear, b

Re: [whatwg] Comments/questions on 4.6 Offline Web applications

2007-10-12 Thread Adam Roben
Darin Adler wrote: On Oct 12, 2007, at 6:11 AM, Adam Roben wrote: It may be worth stating in this section what the behavior is when a section or opportunistic caching namespace appears multiple times. The parsing algorithm makes this clear, but it would be clearer still to also state the beha

Re: [whatwg] Comments/questions on 4.6 Offline Web applications

2007-10-12 Thread Darin Adler
On Oct 12, 2007, at 6:11 AM, Adam Roben wrote: It may be worth stating in this section what the behavior is when a section or opportunistic caching namespace appears multiple times. The parsing algorithm makes this clear, but it would be clearer still to also state the behavior in this sect

Re: [whatwg] Comments/questions on 4.6 Offline Web applications

2007-10-12 Thread Adam Roben
Ian Hickson wrote: On Sat, 6 Oct 2007, Adam Roben wrote: Here are some comments and questions about section 4.6 Offline Web applications: Thanks for the feedback! It was very useful in making the spec better. Please do continue reviewing the spec! Glad to hear it! Can javascrip

Re: [whatwg] Offline Web Apps

2007-10-12 Thread Maciej Stachowiak
On Oct 11, 2007, at 6:47 PM, Robert O'Callahan wrote: On Oct 12, 2007 12:53 PM, Ian Hickson <[EMAIL PROTECTED]> wrote: The problem with isLocallyAvailable() -- as noted by Maciej on IRC -- is mostly one of race conditions. What if the resource was removed in between you asking for it and u