Re: [whatwg] Microdata feedback

2011-07-08 Thread Philip Jägenstedt
On Sat, 09 Jul 2011 01:19:02 +0200, Ian Hickson wrote: On Sat, 9 Jul 2011, Philip Jägenstedt wrote: Step 11 is "If current has an itemprop attribute specified, add it to results." but should be "If current has one or more property names, add it to results." Property names are defined in http:

[whatwg] Call for Clarification of the Menu Element Et Al.

2011-07-08 Thread Hugh Guiney
Hey All, I was in the process of coding a prototype for a site I'm working on when I decided that certain nav's should actually be menu's. While the basic concept is apparent, unfortunately, with zero browser implementation at this time, it is impossible to actually know what my markup is doing (

Re: [whatwg] Timing API proposal for measuring intervals

2011-07-08 Thread Robert O'Callahan
, On Fri, Jul 8, 2011 at 2:54 PM, James Robinson wrote: > On Thu, Jul 7, 2011 at 7:36 PM, Robert O'Callahan wrote: > >> >> Using this value as a clock for media synchronization sounds appealing but >> is complicated by audio clock drift. When you play N seconds of audio, it >> might take slightly

Re: [whatwg] Microdata feedback

2011-07-08 Thread Ian Hickson
On Sat, 9 Jul 2011, Philip Jägenstedt wrote: > > Step 11 is "If current has an itemprop attribute specified, add it to > results." but should be "If current has one or more property names, add > it to results." Property names are defined in > http://www.whatwg.org/specs/web-apps/current-work/mu

Re: [whatwg] Microdata feedback

2011-07-08 Thread Philip Jägenstedt
On Fri, 08 Jul 2011 21:31:49 +0200, Ian Hickson wrote: On Fri, 8 Jul 2011, Philip Jägenstedt wrote: On Fri, 08 Jul 2011 00:33:14 +0200, Ian Hickson wrote: > On Wed, 8 Jun 2011, Tomasz Jamroszczak wrote: > > > > I've been looking into Microdata specification and it struck me, > > that crawling

Re: [whatwg] Microdata feedback

2011-07-08 Thread Ian Hickson
On Fri, 8 Jul 2011, Philip Jägenstedt wrote: > On Fri, 08 Jul 2011 00:33:14 +0200, Ian Hickson wrote: > > On Wed, 8 Jun 2011, Tomasz Jamroszczak wrote: > > > > > > I've been looking into Microdata specification and it struck me, > > > that crawling algorithm is so complex, when it comes to expre

Re: [whatwg] Video feedback

2011-07-08 Thread Ian Hickson
On Thu, 7 Jul 2011, Eric Winkelman wrote: > On Thursday, June 02 Ian Hickson wrote: > > On Fri, 18 Mar 2011, Eric Winkelman wrote: > > > > > > For in-band metadata tracks, there is neither a standard way to > > > represent the type of metadata in the HTMLTrackElement interface nor > > > is there

Re: [whatwg] Proposal to extend registerProtocolHandler

2011-07-08 Thread Jonas Sicking
On Fri, Jul 8, 2011 at 9:44 AM, Ojan Vafai wrote: > On Fri, Jul 8, 2011 at 12:05 AM, Jonas Sicking wrote: >> >> I definitely have privacy concerns regarding a isRegistered function. >> Such a function might be ok in some contexts, but I'd like to avoid it >> as far as possible. > > Just to be cle

Re: [whatwg] Proposal to extend registerProtocolHandler

2011-07-08 Thread Ojan Vafai
On Fri, Jul 8, 2011 at 12:05 AM, Jonas Sicking wrote: > I definitely have privacy concerns regarding a isRegistered function. > Such a function might be ok in some contexts, but I'd like to avoid it > as far as possible. > Just to be clear, you have privacy concerns for an isRegistered function

Re: [whatwg] Proposal to extend registerProtocolHandler

2011-07-08 Thread timeless
If offering a potentially registerable api is done via Then it'd be reasonable for a handling page to return some well known HTTP response (410?) to indicate that the API is no longer supported. The site wouldn't need to call a method, and the user agent would be able to do something reasonable

Re: [whatwg] The blockquote element spec vs common quoting practices

2011-07-08 Thread Jeremy Keith
Bjartur wrote: > Citation will most likely contain the cited resource (@cite), the title > of the cited resource (@title) and the date and optionally time of the > quote (@datetime?). All three of which are invisible and so do not match the use cases that Oli has outlined. At least @title has a

Re: [whatwg] Timing API proposal for measuring intervals

2011-07-08 Thread Roger Hågensen
On 2011-07-08 12:32, Mark Callow wrote: On 08/07/2011 11:54, James Robinson wrote: True. On OS X, however, the CoreVideo and CoreAudio APIs are specified to use a unified time base (see http://developer.apple.com/library/ios/#documentation/QuartzCore/Reference/CVTimeRef/Reference/reference.htm

Re: [whatwg] The blockquote element spec vs common quoting practices

2011-07-08 Thread Bjartur Thorlacius
Þann fös 8.júl 2011 11:20, skrifaði Jeremy Keith: 3) The solution that Oli has proposed (allowing footer within blockquote to include non-quoted information) is an elegant one, in my opinion. I can think of some solutions that would involve putting the attribution data outside the blockquote and

Re: [whatwg] Microdata feedback

2011-07-08 Thread Philip Jägenstedt
On Fri, 08 Jul 2011 00:33:14 +0200, Ian Hickson wrote: On Wed, 8 Jun 2011, Tomasz Jamroszczak wrote: I've been looking into Microdata specification and it struck me, that crawling algorithm is so complex, when it comes to expressing simple ideas. I think that foremost the algorithm should be

Re: [whatwg] The blockquote element spec vs common quoting practices

2011-07-08 Thread Jeremy Keith
Oli wrote: > I’ve outlined the problem and some potential solutions (with their > pros and cons) in: > http://oli.jp/2011/blockquote/ Excellent work, IMHO. I've added my own little +1 here: http://adactio.com/journal/4675/ Oli continues: > I think the blockquote spec should be changed to allow

Re: [whatwg] Timing API proposal for measuring intervals

2011-07-08 Thread Mark Callow
On 08/07/2011 11:54, James Robinson wrote: > True. On OS X, however, the CoreVideo and CoreAudio APIs are specified to > use a unified time base (see > http://developer.apple.com/library/ios/#documentation/QuartzCore/Reference/CVTimeRef/Reference/reference.html) > so if we do end up with APIs sa

Re: [whatwg] Proposal to extend registerProtocolHandler

2011-07-08 Thread Jonas Sicking
I definitely have privacy concerns regarding a isRegistered function. Such a function might be ok in some contexts, but I'd like to avoid it as far as possible. For example I don't think we need to think in terms of the, arguably crappy, UI that browsers currently use. One simple improvement that