Forum: Ruby on Rails Prototype 1.5.0_rc0 breaks my Form.serialize

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
6805b35d0a8ea3ede0a7da2d4cf5ae77?d=identicon&s=25 Jonathan Weiss (Guest)
on 2006-04-07 14:15
(Received via mailing list)
Cheers,


Prototype 1.5.0_rc0 breaks backwards compatability with this diff in
Form.Element.Serializers:

http://dev.rubyonrails.org/changeset/4147


I have explicit value="" in my options and now I get the text submitted.
E.g.

<select id="foo">
  <option value="">Please select a value</option>
  </option value="1">Nr. 1</option>
  </option value="1">Nr. 1</option>
</select>


Now I get foo='Please select a value' against foo='' with prototype 1.4.

This breaks my code.

Jonathan
E3c79c779c0b390049289cdfe7cb9705?d=identicon&s=25 Bob Hutchison (Guest)
on 2006-04-11 16:33
(Received via mailing list)
On Apr 7, 2006, at 8:14 AM, Jonathan Weiss wrote:

> submitted.
> E.g.
>
> <select id="foo">
>  <option value="">Please select a value</option>
>  </option value="1">Nr. 1</option>
>  </option value="1">Nr. 1</option>
> </select>

You might try fixing the </option> tags that are likely intended to
be <option>. Don't know how far that'll get you but it might make
things a bit clearer.

Cheers,
Bob

> Jonathan Weiss
> http://blog.innerewut.de
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

----
Bob Hutchison                  -- blogs at <http://www.recursive.ca/
hutch/>
Recursive Design Inc.          -- <http://www.recursive.ca/>
Raconteur                      -- <http://www.raconteur.info/>
xampl for Ruby                 -- <http://rubyforge.org/projects/xampl/>
6805b35d0a8ea3ede0a7da2d4cf5ae77?d=identicon&s=25 Jonathan Weiss (Guest)
on 2006-04-11 21:45
(Received via mailing list)
Bob Hutchison wrote:
>>
> You might try fixing the </option> tags that are likely intended to be
> <option>. Don't know how far that'll get you but it might make things a
> bit clearer.

Sorry for this, this was just a copy&paste error. This has nothing to do
with my real problem.

The real code of course has <option value="2">blabla</option>

>
> Cheers,
> Bob

Regards,
Jonathan
This topic is locked and can not be replied to.