On 7 Oct, 15:25, Bernhard Schussek <[email protected]> wrote: > Second of all, thank you all for the feedback. Fabien is right, we > need people to test the Form framework thoroughly and provide > feedback.
That's great, I wasn't aware it was ready to be used. > > 1. A readonly widget (for displaying non-editable values) > > What's the point of that? Is that not the same as echoing the value in > your template? Not quite. Suppose the field is marked as required, but we choose that the current user should not be able to edit it. Currently, I would have to a) subclass the form and unset the field; or b) change the field type to a hidden field and manually change the template for this form to echo the value. It would allow me to be more lazy if one of these can be handled automatically. As Jaime says, I don't want the value to be in a hidden input; I don't want it to be editable anywhere. Hope that makes sense! Peter -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en
