Re: [whatwg] Scripted querying of capabilities

Robert O'Callahan wrote: > That would be nice to have. Unfortunately DirectShow and Quicktime do > not seem to expose the ability to enumerate supported codecs, so it > might be hard to implement for some browsers. > > As things stand, you can use elements to offer different > formats, and you can

Re: [whatwg] Video : Slow motion, fast forward effects

On Thu, 7 Aug 2008, Biju [EMAIL PROTECTED] wrote: > > On Thu, Aug 7, 2008 at 1:49 AM, Ian Hickson <[EMAIL PROTECTED]> wrote: > > playbackRate is the right way to do it, but maybe Firefox doesn't yet > > support it. > > So can I assume HTML5 spec also allow playbackRate to be negative value. > ie

Re: [whatwg] Video : Slow motion, fast forward effects

On Thu, Aug 7, 2008 at 1:49 AM, Ian Hickson <[EMAIL PROTECTED]> wrote: > playbackRate is the right way to do it, but maybe Firefox doesn't yet > support it. So can I assume HTML5 spec also allow playbackRate to be negative value. ie to support go backward at various speed Thanks ~Biju

Re: [whatwg] Video : Slow motion, fast forward effects

On Thu, 7 Aug 2008, Biju [EMAIL PROTECTED] wrote: > > How can I get Slow motion, fast forward effect on .? > > Is it possible to go backward at various speed also? > > PS: On Firefox I tried changing "playbackRate" attribute by > Markup as well as script, but did not see any effect. play

[whatwg] Video : Slow motion, fast forward effects

How can I get Slow motion, fast forward effect on .? Is it possible to go backward at various speed also? TIA Biju PS: On Firefox I tried changing "playbackRate" attribute by Markup as well as script, but did not see any effect.

Re: [whatwg] VIDEO tag height/width best fit

On Wed, 6 Aug 2008, Biju [EMAIL PROTECTED] wrote: > > We found Firefox implementation is wrong for aspect ratio adjustment. So > if it is fixed and the developer really to change aspect ratio how will > he able to it. > > Use case are > 1) developer wants to give special effect. > 2) to fix aspe

[whatwg] Setting the "title" attribute

http://www.w3.org/html/wg/html5/#dom-tree > >1. If the title element is > null, then a new >title element must be created >and appended to the head > element

Re: [whatwg] VIDEO tag height/width best fit

We found Firefox implementation is wrong for aspect ratio adjustment. So if it is fixed and the developer really to change aspect ratio how will he able to it. Use case are 1) developer wants to give special effect. 2) to fix aspect ratio problem in the existing media. like http://simon.html5.

Re: [whatwg] HTML 5 : Misconceptions Documented

On Wed, Aug 6, 2008 at 7:03 PM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > > On Aug 6, 2008, at 11:23 AM, Garrett Smith wrote: > >> >> My apologies for being rude. >> >> What would you suggest, Maciej? > > I would suggest: > > a) Point out mistakes courteously. Done. > b) Preferably do so in

Re: [whatwg] Offline Web Applications feedback

On Wed, Aug 6, 2008 at 7:49 PM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > Right, the idea is that you just have your whole web app as an opportunistic > caching namespace and make sure it loads everything it ever needs offline > the first time it loads. I don't think this is a great feature bu

Re: [whatwg] Scripted querying of capabilities

That would be nice to have. Unfortunately DirectShow and Quicktime do not seem to expose the ability to enumerate supported codecs, so it might be hard to implement for some browsers. As things stand, you can use elements to offer different formats, and you can try to play a stream and use script

[whatwg] Scripted querying of capabilities

Would it be possible to add methods or properties to HTMLMediaElement to support scripted determination of client codec capabilities? The supported codecs will no doubt change through the years, as the technology and the legal situation changes. I'd like to see determination of codec support (Vorb

Re: [whatwg] Offline Web Applications feedback

On Aug 6, 2008, at 7:28 PM, Aaron Boodman wrote: On Wed, Aug 6, 2008 at 7:08 PM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: HTTP caching can't promise that all the resources you load when your Web App loads will be available offline. But neither can this feature, since a resource is onl

Re: [whatwg] Offline Web Applications feedback

On Wed, Aug 6, 2008 at 7:08 PM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > HTTP caching can't promise that all the resources you load when your Web App > loads will be available offline. But neither can this feature, since a resource is only there if the application previously loaded it for so

Re: [whatwg] Workers feedback

On Wed, Aug 6, 2008 at 4:24 AM, Ian Hickson <[EMAIL PROTECTED]> wrote: > * I've written an intro section which shows how the API is expected to be > used. I've tried to illustrate each use case that people raised. I will > add more tomorrow. Thanks, that helps a lot. > * I've moved APIs to

Re: [whatwg] Offline Web Applications feedback

On Aug 6, 2008, at 5:48 PM, Aaron Boodman wrote: On Wed, Aug 6, 2008 at 2:20 AM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: On Aug 5, 2008, at 11:30 PM, Aaron Boodman wrote: Some quick notes/questions... - I think the manifest should be some structured, extensible format such as XML or

Re: [whatwg] HTML 5 : Misconceptions Documented

On Aug 6, 2008, at 7:17 AM, Thomas Broyer wrote: On Wed, Aug 6, 2008 at 11:29 AM, Maciej Stachowiak wrote: I think Garret has a valid point (despite his needlessly rude tone) that the way we describe magical dynamic properties in a way that makes clear they are also visible to the "in" o

Re: [whatwg] HTML 5 : Misconceptions Documented

On Aug 6, 2008, at 11:23 AM, Garrett Smith wrote: My apologies for being rude. What would you suggest, Maciej? I would suggest: a) Point out mistakes courteously. b) Preferably do so in the appropriate public forum where others can see them (I don't see any mail from you on this topic in

Re: [whatwg] Offline Web Applications feedback

On Wed, Aug 6, 2008 at 2:20 AM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > > On Aug 5, 2008, at 11:30 PM, Aaron Boodman wrote: > >> Some quick notes/questions... >> >> - I think the manifest should be some structured, extensible format >> such as XML or JSON. The current text-based format is go

Re: [whatwg] Offline Web Applications feedback

On Wed, Aug 6, 2008 at 2:20 AM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > > On Aug 5, 2008, at 11:30 PM, Aaron Boodman wrote: > > Some quick notes/questions... >> >> - I think the manifest should be some structured, extensible format >> such as XML or JSON. The current text-based format is g

Re: [whatwg] element comments

On Wed, 06 Aug 2008 22:42:09 +0200, Simon Pieters <[EMAIL PROTECTED]> wrote: Validators can still issue warnings to help with aspect ratio mistakes without putting up a road block for authors trying to migrate to HTML5. Moreover, currently the spec bans this, which seems legitimate enough:

Re: [whatwg] element comments

On Wed, 06 Aug 2008 22:06:33 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote: On Wed, 30 Jul 2008, Matthew Paul Thomas wrote: > > I'm not sure that this usage of is one that the spec today > considers valid. Wouldn't be the better way to do this? Indeed it wouldn't, because wouldn't work in w3

Re: [whatwg] element comments

On Wed, 30 Jul 2008, Matthew Paul Thomas wrote: > > > > I'm not sure that this usage of is one that the spec today > > considers valid. Wouldn't be the better way to do this? > > Indeed it wouldn't, because wouldn't work in w3m at all! Yeah, you're right, wouldn't work particularly well for t

Re: [whatwg] element comments

Ian Hickson wrote on 30/07/08 04:08: > > On Sun, 14 Oct 2007, Matthew Paul Thomas wrote: >> >> On Oct 14, 2007, at 2:03 AM, Henri Sivonen wrote: >>> >>> I don't think "If both attributes are specified, then the ratio of >>> the specified width to the specified height must be the same as the >>>

Re: [whatwg] Web Applications 1.0 and Menu Labels

Ian Hickson wrote on 29/07/08 03:21: > > On Fri, 10 Aug 2007, Matthew Paul Thomas wrote: >... >> I'm suggesting that since it is common for entire menus -- or >> toolbars -- to be temporarily irrelevant, such as when focus is in a >> field or pane where they do not apply, there should be a disable

Re: [whatwg] Workers feedback

>> - Would it be too weird to have createWorker overloaded to take an >> optional name parameter? This would make the behavior similar to >> window.open(), which either opens a new window or reuses an existing >> window with the same name. > > People seem to dislike overloading in general, but I do

Re: [whatwg] HTML 5 : Misconceptions Documented

On Wed, Aug 6, 2008 at 2:29 AM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > > On Aug 6, 2008, at 12:27 AM, Cameron McCormack wrote: > >> Hi Garrett. >> >> Garrett Smith: >>> [snip] >> Your tests do show that the HTML collections expose items through real >> properties rather than "fake" ones r

Re: [whatwg] HTML 5 : Misconceptions Documented

On Wed, Aug 6, 2008 at 11:29 AM, Maciej Stachowiak wrote: > > I think Garret has a valid point (despite his needlessly rude tone) that the > way we describe magical dynamic properties in a way that makes clear they > are also visible to the "in" operator and to > Object.prototype.hasOwnProperty. Ar

[whatwg] Workers feedback

Summary: * I've written an intro section which shows how the API is expected to be used. I've tried to illustrate each use case that people raised. I will add more tomorrow. * I've completely decoupled workers and Window objects. * I've moved APIs to a "utils" object, so that we rare

Re: [whatwg] HTML 5 : Misconceptions Documented

On Aug 6, 2008, at 12:27 AM, Cameron McCormack wrote: Hi Garrett. Garrett Smith: In EcmaScript, the property access operators seem to look like a "getter" to Cameron. What they really do is provide access to properties added to the collection, or, in one case (on one implementation), this see

Re: [whatwg] Offline Web Applications feedback

On Aug 5, 2008, at 11:30 PM, Aaron Boodman wrote: Some quick notes/questions... - I think the manifest should be some structured, extensible format such as XML or JSON. The current text-based format is going to quickly turn into a mess as we add additional fields and rows. We've implemented

Re: [whatwg] HTML 5 : Misconceptions Documented

Hi Garrett. Garrett Smith: > In EcmaScript, the property access operators seem to look like a > "getter" to Cameron. What they really do is provide access to > properties added to the collection, or, in one case (on one > implementation), this seems implemented as a "getter". A "getter" is a > met