I finally got some time to write the code for new Element() and
Element#writeAttributes. I had some thoughts/question regarding this
and thought I bring it up here for discussion.
My patch right now will allow one to set the boolean attributes (e.g.
checked, disabled, readonly multiple) using
On 13/03/07, Mislav Marohnić [EMAIL PROTECTED] wrote:
foo=afoo=bfoo=c becomes { foo:['a', 'b', 'c'] }. Rails (PHP too, I
think) would preserve only the first value. Ruby preserves all.
In PHP, this would end up as
array(1) { [foo]= string(1) c }
$_GET is an array of 1 element with an index
On 3/14/07, Martin Ström [EMAIL PROTECTED] wrote:
What do you think?
Seems nice to me. Not everything has to be strict :)
The only problem now remains IE and its read-only attributes like name ...
If only it weren't for that :(
--~--~-~--~~~---~--~~
You
I think I have the patch ready and will submit it asap to trac.
Actually my tests to create an input element and set it's name
attribute using #writeAttributes worked fine (both IE6 and IE7) but
maybe I didn't trigger the bug correctly.
On 3/14/07, Mislav Marohnić [EMAIL PROTECTED] wrote:
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Would/could anybody edit this ticket's subject to add the proper [PATCH]
prefix? TIA :)
http://dev.rubyonrails.org/ticket/7826
- --
Marius Feraru
-BEGIN PGP SIGNATURE-
iD8DBQFF+GzRtZHp/AYZiNkRAvxiAJ0e1R2i5yn2a63KdBZMxlQ4ttV2hgCg7Q9s
The compressed versions (not gzip) doesn't seem to work on safari
2.0.4
I get a syntax error- parse error
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send
Yes, as I stated in my previous post as well, this *definitely* need
to be changed to follow the array name with brackets, otherwise you
are simply redefining that variable over and over again and it will
simply equal the last value. Maybe rails handles this correctly but
probably nothing else
Wee. This is very well done. Thanks martin and please submit this. It's lovely
On 2/5/07, Martin Str�m [EMAIL PROTECTED] wrote:
I was just about to submit a patch to trac so instead I bring it up
here for discussion.
Since we already have the Builder in script.aculo.us I don't think is
Trac isn't responding at the moment so I can't explore and see what
other problems Hash.toQueryString is having, but I completely rewrote
it myself to support nested structures and the rewrite handles all of
the cases mentioned in this thread correctly (including for servers
out there that aren't
Trac should be back up now... so you're welcome to submit that.
On Mar 15, 1:31 am, Colin Mollenhour [EMAIL PROTECTED] wrote:
Trac isn't responding at the moment so I can't explore and see what
other problems Hash.toQueryString is having, but I completely rewrote
it myself to support nested
10 matches
Mail list logo
