In general, our feeling is the same. I agree that it is easy to envision
applications for both of the above. For another example, I can imagine
using tables to get, say, two complicated forms side by side on the page.
Right now NCSA Mosaic (I'm talking Windows here; our implementation of
tables is most stable there) supports at least my example, and probably
both of Eric's. (I'll have to check to be sure.)
Since FORMs can't be nested, what problems would we run into with something
like the following:
<FORM ...>
some stuff
<TABLE>
<TR><TD>some more stuff<BR>
<FORM ...>
still more stuff
<INPUT TYPE=.....>
<INPUT TYPE=SUBMIT....>
</FORM>
</TD>
</TR>
</TABLE>
this is yet more stuff
<INPUT TYPE=SUBMIT...>
</FORM
I can parse that, and there's an obvious choice for what the "inner" submit
button should do. For the "outer" submit button, are the "inner" inputs to
be considered part of the form? (My inclination would be no.)
Are there any specification problems (DTD-wise) with allowing something
like this while still disallowing nested FORMs? Should the "interleaved"
nesting be restricted, say, to a certain level?
Can anyone else think of bizarre examples that will cause problems?
mag
-- Tom Magliery ** NCSA ** 605 E Springfield ** Champaign IL 61820 ** USA