On 20 Feb 2009, at 10:52, Greg Hauptmann wrote:
> fair enough - interesting through things worked fine with > "form_for", and it was just when moving to "remote_form_for" the > issue kicked in... > Probably because with remote_form_for the serialization happens in javascript. You're going down a different codepath and so the undefined behaviour may be different. Fred > 2009/2/20 Matt Jones <[email protected]> > > No, it's not a Rails bug - lrn2html. (ref: > http://www.w3.org/TR/html401/struct/tables.html#h-11.2.1 > ) > > Typically, one puts the table in the form, not the other way around. > The HTML spec is pretty specific about what can go inside the table > tag > without being contained by a cell. > > I'd also add, in reference to the original code, that you should be > using > f.select(:default_view, Account::ROLES) - form_for and friends pass > the > builder to the block. > > --Matt Jones > > On Feb 19, 12:17 am, Greg Hauptmann <[email protected]> > wrote: > > 2009/2/19 Greg Hauptmann <[email protected]> > > > > > 2009/1/9 Allen Walker <[email protected]> > > > > >> I solved it: Don't put your form tag under a <table> tag. Argh. > > > > I see that you can put a form in a table, but it has to fit > entirely within > > a table cell (not perfect answer, but better than not being able > to use a > > table at all) > > > > > -- > Greg > http://blog.gregnet.org/ > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
