I like the new Prototype.Browser for browser detection. As I am
working on a SVG application, I need to know WebKit version as webkit
version < 420 does not handle SVG. It will be great to have something
like Prototype.Browser.WebkitVersion or even simplier
Prototype.Browser.Webkit could be 0 or W
I like the new Prototype.Browser for browser detection. As I am
working on a SVG application, I need to know WebKit version as webkit
version < 420 does not handle SVG. It will be great to have something
like Prototype.Browser.WebkitVersion or even simplier
Prototype.Browser.Webkit could be 0 or W
On 3/13/07, Christophe Porteneuve <[EMAIL PROTECTED]> wrote:
>
>
> Marius Feraru a écrit :
> > Could you please explain why do you think this breaks W3C specs, as I
> cannot
> > see it, neither at level 3 [1], nor at level 2 [2]? TIA.
>
> Indeed, this doesn't break the specs.
Oops. Again I mixed
Marius Feraru a écrit :
> Could you please explain why do you think this breaks W3C specs, as I cannot
> see it, neither at level 3 [1], nor at level 2 [2]? TIA.
Indeed, this doesn't break the specs. Lexical scanning clearly states
that both single and double quotes can be used. Which is why
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mislav Marohnić wrote:
> In 1.5.1 it doesn't matter anymore, single or double quotes.
> That kinda breaks W3C specs, but hey - rules are meant to be broken :)
Could you please explain why do you think this breaks W3C specs, as I cannot
see it, neith
On 3/13/07, Christophe Porteneuve <[EMAIL PROTECTED]> wrote:
>
>
> > 4. "foo=a=b=c" becomes { foo:'a=b=c' }
> Totally (is this even a valid URL component though?).
Backends choose how they parse query strings. This is how Rails parses it,
and here it preserves original data when serialized back t
Hey Mislav,
According to the talk we had in Core's campfire, and to the way Rails
seems to behave, here's my take on your examples.
> 1. { foo:'', bar:null } becomes "foo=&bar=".
OK.
> 2. { bar:undefined } is skipped
OK.
> 3. for now, "a=b&bar" becomes { a:'b', bar:undefined }. That should
>
I'm back on the issue. In a recent talk we agreed that we should go by Rails
conventions as much as applicable, so I went and ported some Rails tests to
JavaScript. I also made minor changes to toQuery methods, and here is where
my patch stands now:
1. { foo:'', bar:null } becomes "foo=&bar=".
On 3/13/07, AJ <[EMAIL PROTECTED]> wrote:
>
>
> So the following will return nothing
> var elems = $$("label[for='someId']");
In 1.5.1 it doesn't matter anymore, single or double quotes. That kinda
breaks W3C specs, but hey - rules are meant to be broken :)
But if the above query fails in 1
I would like to suggest a warning or note of importance be added to
the documentation on the usage of $$().
It should be noted in the documentation that, unlike other areas in
JavaScript, the $$() method actually cares what type of quoting you
use (ie single vs double quotes). The selector synt
Aha! Very useful. But the list must be MASSIVE!!! and then different
languages use different rules.
With the comments made, I can see no need to add them to prototype,
though maybe the addCommas method could be useful for instances where
nicely formatted numbers is required.
On 13/03/07, Mislav
On 3/12/07, Richard Quadling <[EMAIL PROTECTED]> wrote:
>
> I'm not a rails person at all. What do you mean by "irregular inflections
> list"?
They maintain a list of irregular stuff, like "octopus" -> "octopi". The
framework also lets you specify your own irregular plurals or to save
uncountable
12 matches
Mail list logo
