On Mar 10, 2011, at 21:29 , Cameron McCormack wrote:
Anne van Kesteren:
Which specifications use it then?
The ones I could find were: Web Applications 1.0, RDFa API and The
System Information API (admittedly fewer than I thought!).
System Information is being split into smaller pieces that
On Fri, 11 Mar 2011, Simon Pieters wrote:
On Fri, 11 Mar 2011 01:02:25 +0100, Ian Hickson i...@hixie.ch wrote:
On Fri, 11 Mar 2011, Cameron McCormack wrote:
Anne van Kesteren:
Lets at least remove sequenceT from the draft then.
Cameron McCormack:
Other specifications use
On Fri, 11 Mar 2011, Cameron McCormack wrote:
Anne van Kesteren:
Lets at least remove sequenceT from the draft then.
Cameron McCormack:
Other specifications use it, and it really serves a different
purpose from things like NodeList, like passing in native Array
objects to DOM
Ian Hickson:
Web Apps 1.0 will change if you need it to. Don't constrain on my account
here. I'll do whatever you think we should do. The only places I use it
are in an argument to a method because I want to allow authors to pass in
literal JS Arrays of values, and on a NodeList descendant
On Fri, 11 Mar 2011, Cameron McCormack wrote:
Ian Hickson:
Web Apps 1.0 will change if you need it to. Don't constrain on my account
here. I'll do whatever you think we should do. The only places I use it
are in an argument to a method because I want to allow authors to pass in
literal
Ian Hickson:
Makes sense. What I really want is a NodeList-like interface, but ideally
one that supports all the Array accessors, but I don't want to have to
redefine it each time. Is there some way we could get a macro for that
kind of thing?
See also:
On Fri, 11 Mar 2011 01:02:25 +0100, Ian Hickson i...@hixie.ch wrote:
On Fri, 11 Mar 2011, Cameron McCormack wrote:
Anne van Kesteren:
Lets at least remove sequenceT from the draft then.
Cameron McCormack:
Other specifications use it, and it really serves a different
purpose from things
On Tue, 08 Mar 2011 19:47:47 +0100, Arun Ranganathan a...@mozilla.com
wrote:
Do you disagree that FileList should be a sequence parametrized type?
I think the construct of a parametrized type makes a lot of sense. But it
should work like the types we have to date, so that NodeList,
On 3/9/11 7:12 AM, Anne van Kesteren wrote:
On Tue, 08 Mar 2011 19:47:47 +0100, Arun Ranganathan
a...@mozilla.com wrote:
Do you disagree that FileList should be a sequence parametrized type?
I think the construct of a parametrized type makes a lot of sense. But
it should work like the types
On 1/31/11 11:04 AM, Simon Pieters wrote:
Hi,
Why is FileList defined as
typedef sequenceFile FileList;
rather than as an interface similar to NodeList? It seems that in
Gecko and WebKit FileList is more like NodeList than as a sequence.
(In the process of going through feedback to
On Tue, 08 Mar 2011 19:47:47 +0100, Arun Ranganathan a...@mozilla.com
wrote:
On 1/31/11 11:04 AM, Simon Pieters wrote:
Hi,
Why is FileList defined as
typedef sequenceFile FileList;
rather than as an interface similar to NodeList? It seems that in Gecko
and WebKit FileList is more
Hi,
Why is FileList defined as
typedef sequenceFile FileList;
rather than as an interface similar to NodeList? It seems that in Gecko
and WebKit FileList is more like NodeList than as a sequence.
--
Simon Pieters
Opera Software
12 matches
Mail list logo
