Hi > What is the thinking behind ignoring those fields items in a form that have > been disabled? Is this an HTML recommended standard?
Browsers don't submit disabled fields, so Prototype doesn't serialize them. This has been true pretty much forever, but here's the latest HTML spec's description of this: http://www.w3.org/TR/html5/association-of-controls-and-forms.html#constructing-form-data-set So not just recommended, but dictated by the standard. HTH, -- T.J. Crowder Independent Software Engineer tj / crowder software / com www / crowder software / com On Jul 29, 5:03 pm, kstubs <kst...@gmail.com> wrote: > What is the thinking behind ignoring those fields items in a form that have > been disabled? Is this an HTML recommended standard? > > Here is what I do, perhaps there is a much better solution. > I often need to show a client a field value, like a primary key ID, but they > shouldn't change it, so I disable this input. I do like the look of the > disabled input, and this is why I default to this view - but - the item is > ignored on serialization. > > Karl.. -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
