On 11/6/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
Well... Semantically span is an inline element.
Form is a block element, as well as div.
Correct.
So I don' think so substituting it for a span is a good idea. Div itself
has no styling at all, unless you style it by css.
OK, fair enough.
Does it means that if the inner is replaced with that it
might look different (preview different from rendered output)?
Juergen
On 11/6/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
Well... Semantically span is an inline element.
Form is a block element, as well as div.
So I don' think so subst
Well... Semantically span is an inline element.
Form is a block element, as well as div.
So I don' think so substituting it for a span is a good idea. Div itself
has no styling at all, unless you style it by css.
-Matej
Martijn Dashorst wrote:
On 11/6/06, Matej Knopp <[EMAIL PROTECTED]> wrot
On 11/6/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
Every inner form is going to be written to output as div.
Just one last thing: can we substitute the div with a span? A span
typically has no styling and doesn't affect layout, just like forms.
Martijn
--
http://www.thebeststuffintheworld.com
Yeah, indeed this is a pissing content :)
So again, just in case anyone still thinks that we are going to output
nested html forms:
WE ARE NOT GOING TO OUTPUT NESTED HTML FORMS.
Every inner form is going to be written to output as div. Outer form is
going to be submitted, but only the inner
On 11/5/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
I vote (if im allowed) not to allow nested forms at all as they are not HTML
compliant.
I *love* a pissing contest :-) I did some research on nesting forms
(which is quite interesting though, seaside has had similar
discussions), and discov
I vote (if im allowed) not to allow nested forms at all as they are not HTML
compliant.
Regards
> -Ursprüngliche Nachricht-
> Von: Martijn Dashorst [mailto:[EMAIL PROTECTED]
> Gesendet: Sonntag, 5. November 2006 13:40
> An: Wicket Development
> Betreff: [VOTE] Nested forms - don't proc