Cameron McCormack:
> I was thinking that an ES4 language binding would be separate from the
> ES3 one being specified here. I’m confident that the mapping for
> sequence in the ES3 binding can be written so as to allow an
> implementation to use a more efficient host object than an Array object.
Cameron McCormack:
> > Does sequence not cover that? Would you prefer it to be
> > "looser", in that [[Get]]s and [[Put]]s work like an array, but it is
> > not an ECMAScript Array object (so that it can have some more efficient
> > representation underneath)?
liorean:
> I would prefer that. The
Replying to some comments from Anne in IRC:
anne:
> heycam, [Constructor] also needs to address things with arguments
OK. Apart from the Audio/Image/Option constructors mentioned in HTML 5,
do you know of any other objects that have constructors that take
arguments?
> heycam, and actually also
2007/6/28, Lachlan Hunt <[EMAIL PROTECTED]>:
Would others accept changing the methods to cssQuery() and
cssQueryOne()? If this would achieve concensus, I'd be willing to use
these names.
I guess I'll accept this then.
I think the selectElement name is a much worse name (for the reasons
Bjoern
Anne van Kesteren:
> It would still be very good to have an octet / byte representation in
> ECMAScript. I'm aware of a couple of implementations of such a thing, but
> I haven't been able to play with them or figure out how they work exactly
> myself:
[snip]
> 2. I heard Adobe Flex has some
On Thu, 28 Jun 2007, Lachlan Hunt wrote:
>
> I'd have to make cssQuery() be the method that returns the node list
> because Dean Edward's implementation uses the same name to return an
> array. The question is then what to call the singular method.
>
> There has been an argument made that the
On Thu, 28 Jun 2007 12:36:01 +0200, denis sureau <[EMAIL PROTECTED]>
wrote:
[...]
Fixed the typos.
Not clear what you mean by bubbling:
...is dispatched on it during the bubbling phase
That term is defined in DOM Level 3 Events.
Should not contain a "format" but a string instea
* Lachlan Hunt wrote:
>I don't agree with the last argument about text selection applying to
>these names, since the names clearly say Element, but in general, you
>make a very good case.
I believe dojo.html.selection.selectElement changes the text selection
so the specified element is selected
Anne van Kesteren:
> It would still be very good to have an octet / byte representation in
> ECMAScript. I'm aware of a couple of implementations of such a thing, but
> I haven't been able to play with them or figure out how they work exactly
> myself:
>
> 1. XMLHttpRequest has a response
On 28/06/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
On Thu, 28 Jun 2007 05:57:09 +0200, Cameron McCormack <[EMAIL PROTECTED]>
wrote:
>> For sequence it would be really nice if we could have a more
>> native representation of a byte array than a UTF-16 string.
>
> Strange, I really should h
On Thu, 28 Jun 2007 05:57:09 +0200, Cameron McCormack <[EMAIL PROTECTED]>
wrote:
For sequence it would be really nice if we could have a more
native representation of a byte array than a UTF-16 string.
Strange, I really should have used sequence there.
Fixed.
I still am a little unsettled
I have just achieved the translation in french.
I dont know if this is regarded as a contribution, but I have noticed some
inacuracies...
Users agents become a single one:
Conforming user agents must support some version of DOM Events and DOM
Core, because this specification uses some of the f
Maciej Stachowiak wrote:
Arguments against cssQuery:
- Selectors are not just called "Selectors", not "CSS Selectors", and
using "css" in the API may lead people to think selectors are only for CSS
Arguments for cssQuery:
- Significantly shorter than selectElement()
- Already the name used
On Thu, 28 Jun 2007 04:05:13 +0200, Cameron McCormack <[EMAIL PROTECTED]>
wrote:
Hi everyone.
I’ve filled in most of the interesting stuff for the Bindings spec, so I
think it could do with some more review.
"what Hixie said" :)
Let's start a formal call for consensus.
cheers
Chaals
-
On Thu, 28 Jun 2007 07:17:41 +0200, Martijn <[EMAIL PROTECTED]>
wrote:
2007/6/28, Doug Schepers <[EMAIL PROTECTED]>:
Decisions get made all the time without informing the public list. The
decision to create this spec in the first place was not a public
decision. Most of the wording and fu
Hi Lachlan,
On Jun 22, 2007, at 10:23 PM, Lachlan Hunt wrote:
*Conclusion*
After carefully considering all of these reasons, I have update the
spec to use selectElement() and selectAllElements(), based on the
arguments given above.
http://dev.w3.org/cvsweb/~checkout~/2006/webapi/select
On Jun 27, 2007, at 11:38 AM, Doug Schepers wrote:
Hi, Jean-Yves-
Jean-Yves Bitterlich wrote:
We find it unfortunate that past resolutions within the working
group are being invalidated (unless of course there are new
evidences/information that justify this act) in particular because
t
17 matches
Mail list logo
