Re: [clipboard] typo in WebIDL

So does this imply that someone (i.e. Hallvord :)) needs to move it elsewhere? Sincerely, James Greene On Wed, Sep 18, 2013 at 12:17 PM, Tab Atkins Jr. wrote: > On Wed, Sep 18, 2013 at 10:06 AM, James Greene > wrote: > > On Sep 18, 2013 10:42 AM, "Anne van Kesteren" wrote: > >> On Wed, S

Re: [clipboard] typo in WebIDL

On Wednesday, 18 September 2013 at 20:31, Hallvord Steen wrote: > > So does this imply that someone (i.e. Hallvord :)) needs to move it > > elsewhere? > > > > Nah, it just means I should be more stringent on pushing out releases and go > through the TR process (painful or not) so that t

Re: [clipboard] typo in WebIDL

On Wed, Sep 18, 2013 at 12:09 PM, James Greene wrote: > On Wed, Sep 18, 2013 at 12:17 PM, Tab Atkins Jr. > wrote: >> On Wed, Sep 18, 2013 at 10:06 AM, James Greene >> wrote: >> > On Sep 18, 2013 10:42 AM, "Anne van Kesteren" wrote: >> >> On Wed, Sep 18, 2013 at 10:09 AM, James Greene >> >> >>

Re: [clipboard] typo in WebIDL

> So does this imply that someone (i.e. Hallvord :)) needs to move it > elsewhere? Nah, it just means I should be more stringent on pushing out releases and go through the TR process (painful or not) so that the thingy with /TR/ in the URL is as up-to-date as possible. For a spec like clipboard

Re: [clipboard] typo in WebIDL

On Wed, Sep 18, 2013 at 3:09 PM, James Greene wrote: > So does this imply that someone (i.e. Hallvord :)) needs to move it > elsewhere? The URL given in OP is the correct URL. (Though at some point all specifications should be in GitHub.) -- http://annevankesteren.nl/

Re: [clipboard] typo in WebIDL

I'm lost. Is there an explanation of this somewhere? On Sep 18, 2013 10:42 AM, "Anne van Kesteren" wrote: > On Wed, Sep 18, 2013 at 10:09 AM, James Greene > wrote: > > Remember that the URL referenced is not for the latest version of this > spec. > > Correct URL: > >http://www.w3.org/TR/clip

Has WebApps' work on streams-api ended? [Was: [streams-api] WebIDL bug]

Hi Feras, All, So, what is the plan for WebApps' streams-api spec? (I noticed the ED hasn't been updated in seven months .) -Thanks, AB On 9/18/13 10:01 AM, ext Dominique Hazael-Massieux wrote: Le mercredi 18 septembre 2013 à 09:53 -0400, Anne van Keste

Re: [clipboard] typo in WebIDL

On Wed, Sep 18, 2013 at 10:06 AM, James Greene wrote: > On Sep 18, 2013 10:42 AM, "Anne van Kesteren" wrote: >> On Wed, Sep 18, 2013 at 10:09 AM, James Greene >> wrote: >> > Remember that the URL referenced is not for the latest version of this >> > spec. >> > Correct URL: >> >http://www.w3.

Re: [clipboard] typo in WebIDL

On Wed, Sep 18, 2013 at 10:09 AM, James Greene wrote: > Remember that the URL referenced is not for the latest version of this spec. > Correct URL: >http://www.w3.org/TR/clipboard-apis/ If the URL includes TR/, it's not the correct URL. -- http://annevankesteren.nl/

Re: [clipboard] typo in WebIDL

On 9/18/13 10:09 AM, James Greene wrote: Remember that the URL referenced is not for the latest version of this spec. Correct URL: http://www.w3.org/TR/clipboard-apis/ Again, this has no IDL for the dictionary at all. That's clearly wrong. -Boris

Re: [clipboard] typo in WebIDL

Understood, just making sure we're pointed at the right spec. For some reason, Google search results can't seem to shake that old spec in favor of the new one. The new spec doesn't even make the first 5 pages of results for me when I search "clipboard api" or "html|html5 clipboard api". :-\ It

Re: Overlap between StreamReader and FileReader

Still thinking about it, my proposal is OK to handle simply delta data produced by the APIs, for the other proposals I could not see the link between the data producer APIs and the streams, then looking at what node does, maybe a createStream method could be added so we can do something like:

Re: [clipboard] typo in WebIDL

Remember that the URL referenced is not for the latest version of this spec. Correct URL: http://www.w3.org/TR/clipboard-apis/ On Sep 18, 2013 8:54 AM, "Anne van Kesteren" wrote: > On Wed, Sep 18, 2013 at 9:05 AM, Hallvord Steen > wrote: > > At some point I started using respec.js and switche

Re: [streams-api] WebIDL bug

Le mercredi 18 septembre 2013 à 09:53 -0400, Anne van Kesteren a écrit : > On Wed, Sep 18, 2013 at 4:52 AM, Dominique Hazael-Massieux > wrote: > > While parsing en-masse some of the IDLs in JavaScript APIs out there, I > > stumbled upon an incorrect IDL in > > https://dvcs.w3.org/hg/streams-api/r

Re: [streams-api] WebIDL bug

On Wed, Sep 18, 2013 at 4:52 AM, Dominique Hazael-Massieux wrote: > While parsing en-masse some of the IDLs in JavaScript APIs out there, I > stumbled upon an incorrect IDL in > https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm#error-uris_for_streams This specification is obsolete. Nob

Re: [clipboard] typo in WebIDL

On Wed, Sep 18, 2013 at 9:05 AM, Hallvord Steen wrote: > At some point I started using respec.js and switched to whatever convention > the respec version I was using used for IDL snippets. I may have to sit down > and understand if I've done that correctly, or if I've done something > incompati

Re: [clipboard] typo in WebIDL

On 9/18/13 4:52 AM, Dominique Hazael-Massieux wrote: >> should read instead Thanks Dominique, will fix. > What Gecko's WebIDL has here is: > > and claims it came from the spec draft... At some point I started using respec.js and switched to whatever convention the respec version I was using us

Re: Allow javascript: URIs for registerProtocolHandler

> Maybe. We'd lose the symmetry with registerContentHandler() unless we > move its redirect-like logic to fetch as well, aside from the security > implications. This would need more discussion. It would be useful to allow registerContentHandler() also to be used inside tags, but also I don't thin

Re: Allow javascript: URIs for registerProtocolHandler

On Wed, Sep 18, 2013 at 8:42 AM, pira...@gmail.com wrote: > I find the fact of being able to use custom protocols on and >

Re: [clipboard] typo in WebIDL

On 9/18/13 4:52 AM, Dominique Hazael-Massieux wrote: should read instead dictionary ClipboardEventInit : EventInit { DOMString data; DOMString dataType; }; What Gecko's WebIDL has here is: dictionary ClipboardEventInit : EventInit { DOMString data

Re: Allow javascript: URIs for registerProtocolHandler

> Ian, was it ever the intent that these methods affect the way Fetch > works? Either way, this could use some tightening up as the current > language is quite vague. I think we should only let them affect the > navigate algorithm. Either way, we should clarify where the URL > translation happens a

Re: Allow javascript: URIs for registerProtocolHandler

On Tue, Sep 17, 2013 at 4:34 PM, pira...@gmail.com wrote: > Really :-) I though the same, but since its a "GET equivalent operation" > just like XHR and in fact Google Charts creates on-demand graphics based on > the data on the URL query, so why not? So I created a custom fake protocol, > set it

[clipboard] typo in WebIDL

Hi, While parsing en-masse some of the IDLs in JavaScript APIs out there, I stumbled upon an incorrect IDL in http://dev.w3.org/2006/webapi/clipops/clipops.html#dictionary-clipboardeventinit-members Dictionary members are not declared with the "attribute" keyword. So dictionary Clipboard

[streams-api] WebIDL bug

Hi, While parsing en-masse some of the IDLs in JavaScript APIs out there, I stumbled upon an incorrect IDL in https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm#error-uris_for_streams First, the stream API should not redefine the URL interface, but instead define the additional method i