Whoa! Why is this a bug? I have code that might break with this change.  A better solution I think for backwards compatibility would be to have an extra parameter that defaults to including disabled and if passed "false" will not include disabled elements.

Colin

Thomas Fuchs wrote:
Btw, just applied the patch to Prototype trunk, see
http://dev.rubyonrails.org/changeset/5354


-Thomas

Am 24.10.2006 um 09:33 schrieb Martin Bialasinski:

  
On 10/24/06, Zyclops <[EMAIL PROTECTED]> wrote:
    
When using form.serialize, it also includes disabled elements.
      
This is a bug.

    
Would
it be possible to alter future versions of prototype to not include
disabled elements, or have an option not to include disabled  
elements.
      
http://dev.rubyonrails.org/ticket/4586

    
Is there a trac(or similar program) for prototype?
      
See above.

    

--
Thomas Fuchs
wollzelle

http://www.wollzelle.com

questentier on AIM
madrobby on irc.freenode.net

http://www.fluxiom.com :: online digital asset management
http://script.aculo.us :: Web 2.0 _javascript_
http://mir.aculo.us :: Where no web developer has gone before







  

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Reply via email to