On Domingo, 6 de Febrero de 2011 22:36:09 Michael Latta escribió: > Why are the association-record-errors placed as a DIV at the same level as > the ol entries for each record, rather than being at the top of the ol for > the record with the error? > > My users reported a usability problem with creating a record that had > validation errors: > > 1) create a new record > 2) filling invalid data > 3) submit > 4) errors are returned but the new record can not be deleted to get a clean > submit. > > Item 4 above seems wrong to me. In digging around the code I found where > it explicitly prevents the last record if new from being deleted. Users > should be able to scrap a new record with errors. If I remove the locked > logic I can delete the record but the errors remain. If they were > rendered within the ol then it would clean them up when the ol was > removed.
I have moved errros inside the ol, but it's only possible in vertical subform, is not possible in horizontal subform because errors and record are in different tr. What logic did you change to remove the record? -- Sergio Cambra .:: entreCables S.L. ::. Mariana Pineda 23, 50.018 Zaragoza T) 902 021 404 F) 976 52 98 07 E) [email protected] -- You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en.
