On 3/16/07, Colin Mollenhour [EMAIL PROTECTED] wrote:
Here's mine. First, it uses $H(value).findAll, so it isn't safe (try
feeding
it each, for instance).
The new function in 1.5.1_rc1 has the same problem so I figured you
were comfortable with that fact already..
No I'm not
The new version of $$() is wonderful but doesn't seem to work all that
well with the :nth psuedo-elements. It looks to only work correctly
when in the formula an+b, a and b are positive and b a. I
don't know if anyone has noticed this yet, but I couldn't find a bug id
so I filled a new one
Hey Trevan,
Trevan Richins a écrit :
The new version of $$() is wonderful but doesn't seem to work all that
well with the :nth psuedo-elements. It looks to only work correctly
when in the formula an+b, a and b are positive and b a. I
don't know if anyone has noticed this yet, but I
Andrew Dupont wrote:
We *are* trying to implement a serialization
method compatible with application/x-www-form-urlencoded
I think this makes the situation very simple then. We need Hash.toQueryString to
behave *exactly* like a form of type application/x-www-form-urlencoded. Forms
*do not*
Hello!
I am from Brazil and my English is very poor... hehehehe
I have a lot of doubts about using the Prototype.Ajax to get
information of a XML.
Somebody can help me?
I don´t understand if a can get the information of XML using JSON... I
am lost!!!
Thank´s!
Vitor
Thanks. No reason - we simply forgot to update the page ;)
On 3/16/07, seb [EMAIL PROTECTED] wrote:
Hi
I have just noticed that on the website, in the download area, it's
still 1.5.1_rc1 and not 1.5.1_rc2.
Just for information (or may be there ia reason that I don't see)
Seb
Tom Gregory wrote:
Take Michael's argument a bit further (_exact_ encoding as a form
would do it), and perhaps it might be acceptable that any nested
arrays/hashes simply be JSON encoded and passed as a string. It's a
simple convention, with no edge cases.
I'm ok with this. It's
On 16 mar, 12:14, Mislav Marohnić [EMAIL PROTECTED] wrote:
Using that structure is treating arrays as hashes, which they are not.
Besides, you are not integrating a framework in an existing application,
you are porting your existing application to a framework.
Get it
That means some
serious
Michael Peters wrote:
In the process, blank values are being
lost. Here's an example:
var query = 'foo=barfoo=foo=foo=baz';
alert('BEFORE: ' + query + \nAFTER : +
$H(query.toQueryParams()).toQueryString());
The reason this breaks is because toQueryParams() translates
Michael Peters wrote:
Michael Peters wrote:
In the process, blank values are being
lost. Here's an example:
var query = 'foo=barfoo=foo=foo=baz';
alert('BEFORE: ' + query + \nAFTER : +
$H(query.toQueryParams()).toQueryString());
The reason this breaks is because toQueryParams()
After seeing all of the server-side inconsistencies with url decoding,
I too agree that Hash.toQueryString is getting too complicated. In
fact, what was wrong with the old one? The one currently in 1.5.1_rc2
needs to go as it has several problems that the old one didn't have
and it is pretty
11 matches
Mail list logo
