danger - remember: most wicket users come
> from
> > a
> > > >> point
> > > >> of GUI building, they dont know the limitations of http, html,
css,
> > > >> ajax -
> > > >> this ends usually up in trouble (security, locked out brows
1.3 a real
> > > > >> > improvement and a showcase for component frameworks: work
> > > > >> > around problems in an elegant and meaningful way. Abstract
> > > > >> > away the limitations of the protocols we have to work with.
> > &g
> condition is encountered. Non-binding.
>> > > > >
>> > > > > On 11/5/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
>> > > > >>
>> > > > >> shame on me ...
>> > > > >>
>> > > > >> now serious
>> >
t; >> point
> > > >> of GUI building, they dont know the limitations of http, html,
css,
> > > >> ajax -
> > > >> this ends usually up in trouble (security, locked out browsers,
> > > >> unusability,
> > > >> load,
e
> from
> > a
> > > >> point
> > > >> of GUI building, they dont know the limitations of http, html,
css,
> > > >> ajax -
> > > >> this ends usually up in trouble (security, locked out browsers,
> > > >> unusability
; point
> > >> of GUI building, they dont know the limitations of http, html, css,
> > >> ajax -
> > >> this ends usually up in trouble (security, locked out browsers,
> > >> unusability,
> > >> load, not barrer free...)
> > >>
> > >
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
is ends usually up in trouble (security, locked out browsers,
> >> unusability,
> >> load, not barrer free...)
> >>
> >> my personal way is to always stick to standards - it might be harder
> >> sometimes to achive this, but youre on a save side...
> &
unusability,
>> load, not barrer free...)
>>
>> my personal way is to always stick to standards - it might be harder
>> sometimes to achive this, but youre on a save side...
>>
>> Regards
>>
>> Korbinian
>>
>> > -Ursprüngliche Nachr
;> Regards
>>
>> Korbinian
>>
>> > -----Ursprüngliche Nachricht-----
>> > Von: Martijn Dashorst [mailto:[EMAIL PROTECTED]
>> > Gesendet: Sonntag, 5. November 2006 22:00
>> > An: wicket-dev@incubator.apache.org
>> > Betreff: Re: Re: [V
EMAIL PROTECTED]
> Gesendet: Sonntag, 5. November 2006 22:00
> An: wicket-dev@incubator.apache.org
> Betreff: Re: Re: [VOTE] Nested forms - don't process inner
> form fields in outer form submit
>
> On 11/5/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > T
After following your discussion:
[x] Yes, don't process those pesky little fields
Dirk
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
> > > Gesendet: Sonntag, 5. November 2006 22:00
> > > An: wicket-dev@incubator.apache.org
> > > Betreff: Re: Re: [VOTE] Nested forms - don't process inner form
> > > fields in outer form submit
> > >
> > > On 11/5/06, Eelco Hillenius <[EMAIL P
lto:[EMAIL PROTECTED]
> Gesendet: Montag, 6. November 2006 00:09
> An: wicket-dev@incubator.apache.org
> Betreff: Re: Re: [VOTE] Nested forms - don't process inner
> form fields in outer form submit
>
> On 11/5/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
> >
>
rüngliche Nachricht-
> Von: Martijn Dashorst [mailto:[EMAIL PROTECTED]
> Gesendet: Sonntag, 5. November 2006 22:00
> An: wicket-dev@incubator.apache.org
> Betreff: Re: Re: [VOTE] Nested forms - don't process inner
> form fields in outer form submit
>
> On 11/5/06, Eelco
liche Nachricht-
> Von: Martijn Dashorst [mailto:[EMAIL PROTECTED]
> Gesendet: Sonntag, 5. November 2006 22:00
> An: wicket-dev@incubator.apache.org
> Betreff: Re: Re: [VOTE] Nested forms - don't process inner
> form fields in outer form submit
>
> On 11/5/06, Eelco Hillen
my personal way is to always stick to standards - it might be harder
sometimes to achive this, but youre on a save side...
And that's a sane view point. However, we are not forcing people to
use nested forms, but we merely make it possible. We could consider
making this another configuration par
[VOTE] Nested forms - don't process inner
> form fields in outer form submit
>
> On 11/5/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > The vote: don't process inner form fields when the outer form is
> > > submitted [ ] Yes, don't process those
Hmmm breakfast. We already allow nested forms, but we don't do
anything about it, and these fail horribly at the moment as Korbinian
reminds us of constantly. The only other option would be to check the
markup and throw a runtime exception that nesting is not allowed.
I think the way we treat
On 11/5/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> The vote: don't process inner form fields when the outer form is submitted
> [ ] Yes, don't process those pesky little fields
> [ ] No, process them as if they were part of the outer form
I'm still not crazy about the whole concept, but I
The vote: don't process inner form fields when the outer form is submitted
[ ] Yes, don't process those pesky little fields
[ ] No, process them as if they were part of the outer form
I'm still not crazy about the whole concept, but I guess nested forms
can be useful sometimes. I just hope we do
On 11/5/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
The vote: don't process inner form fields when the outer form is submitted
[X] Yes, don't process those pesky little fields
[ ] No, process them as if they were part of the outer form
d forms - don't process inner form
> fields in outer form submit
>
> A problem with nested forms arises when the outer form is
> submitted and what should happen with the fields of the inner forms.
>
> Consider the following form setup in a page:
>
> outer
>
A problem with nested forms arises when the outer form is submitted
and what should happen with the fields of the inner forms.
Consider the following form setup in a page:
outer
inner1
inner2
inner3
inner4
If you submit the outer form, what should you process now? All inner
forms? I
29 matches
Mail list logo
