2009/8/16 RVince <[email protected]>:
>
> Colin,
>
> THank you. However, in this case, the form doesn't contain the rows,
> but actually resides between them, in a separate div if that is at all
> possible. After examining this, I am convinced there is no way to
> feasibly do it aside from say, a link in the table that opens up a
> form in redbox/lightbox. And even that may not work.
>

I may be wrong but I do not believe that a div is permitted between
rows either.  To test generate some simple a simple test html page and
paste the source into the html validator at
http://validator.w3.org/#validate_by_input

Colin

> On Aug 15, 3:35 pm, Colin Law <[email protected]> wrote:
>> 2009/8/14 RVince <[email protected]>:
>>
>>
>>
>>
>>
>>
>>
>> > I have a view that has a swath of innerHTML in it. This innerHTML
>> > resides in an HTML table, and it is updated every second by a
>> > javascript timer which, through anX MLHttpRequest, reads a file of
>> > JSON data which is written to the server by another application.
>>
>> > The upshot is, this table is live on the web page. Within this table,
>> > I will have a link which the user can click, which would then open
>> > that row from that live table, in a formview to be user-edited.
>>
>> > I plan on usinghttp://www.prototypejs.org/api/element/toggleto pop
>> > this open. The problem is, this would require a div for each row that
>> > would have the form. As you can see from my description, I am updating
>> > this row every second, and at times there can be two dozen or more
>> > rows -- which is too much data to push through.
>>
>> > I'm wondering if anyonw can offer me any good ideas on how to solve
>> > this dilemma. I need to keep the data, the html, for the table as
>> > light as possible, When the user click the rows link, I need to open
>> > the form up within the rows (the typical type of editing behavior you
>> > see in web apps).
>>
>> Not helping solve the problem at all but just to point out that a form
>> cannot wrap a row or group of cells in a table, it is not valid html.
>> The form must include the whole table or the form must lie entirely
>> within one cell.  Do not be led astray by the fact that it appears to
>> work in some browsers, it will not work in all.  It is a pain but that
>> is the way it is.
>>
>> Colin
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to