Hi Charles & everyone,
Charles McCathieNevile wrote:
On Thu, 16 Aug 2007 19:56:59 +0200, Travis Leithead
<[EMAIL PROTECTED]> wrote:
Recently, a member-only vote was held
to attempt (yet-again) to resolve general complaining, grumbling, etc.,
about the latest API names chosen for the Select
David Håsäther wrote:
On 2007-02-06 15:03, David Håsäther wrote:
Sorry, I think I misunderstood you. I thought your "+1" was an objection
(As the last line you quoted was "Any objections?")
Sorry if I was not clear enough, the +1 was indeed on the decision not
on the call for objections ;
Hi David,
David Håsäther wrote:
On 2007-02-06 14:07, Christophe Jolif wrote:
Charles McCathieNevile wrote:
Not having heard strong objections, and having had support for
getElementsBySelector() that is at least as strong as anything else,
I think (with my chair's hat) this can be tak
Charles McCathieNevile wrote:
On Sun, 28 Jan 2007 13:41:10 +0530, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
Given the input from Björn I suppose there's no real need for a method
that returns a single element node (assuming implementations make that
optimization). Given that, I propose we r
Hi all,
Maciej Stachowiak wrote:
I like match/matchAll better than get/getAll or css/cssAll to be honest.
Why don't we just go back to the original versions?
If I wanted to be paranoiac, I would say that it was a good idea from
the match* proponents to come up with an even worst proposal t
Hi Maciej,
Maciej Stachowiak wrote:
Short Names For Common Idioms
---
Some examples:
Consider if in C++, the end of statement token was not the brief but
arbitrary ";", but the far more explicit "end_of_statement". Reading
code like this:
int x = get
Martijn wrote:
On 12/20/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
One of the arguments that was made was also that the existing methods
have
failed, which would make #3 the odd one out and probably #2 as well. "I
don't really care what the final name, but it should match the first
prin
Hi Doug,
Doug Schepers wrote:
> SVG
> JavaScript
> Desktop
Firefox 1.0+
I thought SVG was supported since Firefox 1.5 only?
--
Christophe
Jim Ley wrote:
"Christophe Jolif" <[EMAIL PROTECTED]>
Even though you can always imagine to find solution to workaround it.
I think it is a bad idea to go to 4 without having a clear knowledge
of what the status really is (successful or erroneous). Indeed bad or
null XML
Jim Ley wrote:
"Jonas Sicking" <[EMAIL PROTECTED]>
In IE you can at least test for .status == 200 to test if things
worked out ok. Even though the statuscode for various errors seem to
be weird to say the least, at least they are different from the
success codes.
I actually think this is h
Anne van Kesteren wrote:
On Thu, 06 Apr 2006 11:20:53 +0200, Christophe Jolif <[EMAIL PROTECTED]>
wrote:
As far as I can see, dispatching another event will not permit to
distinguished between readyState = 4 that means LOADED and readyState
= 4 that means ABORTED...
Per our last reso
Hi,
Anne van Kesteren wrote:
On Wed, 05 Apr 2006 22:56:28 +0200, Jonas Sicking <[EMAIL PROTECTED]> wrote:
If that is indeed true we need to fix it I agree. Is there a sensible
value we could set .status to for example?
Lets keep .status an HTTP status code. What about dispatching an abort
Maciej Stachowiak wrote:
On Apr 4, 2006, at 10:50 PM, Brad Fults wrote:
On 4/4/06, Web APIs Issue Tracker <[EMAIL PROTECTED]> wrote:
A.2) Define using a TimerListener interface which is meant only for
other languages, while ECMAScript only actually allows strings or
functions to be passe
Hi everyone,
There is something I still don't get with abort and XHR state. We saw
that we think the state after an abort must be 4 == loaded. Given that,
as a listener on the request, how can I know if a request has been
aborted or has been loaded? As far as I can see, I can't. And it seems
14 matches
Mail list logo
