On 9/24/07, Maris Orbidans <[EMAIL PROTECTED]> wrote:
>
> is it a joke ? In that case web design templates would need a unique
> class attribute for each element that is going to be used via Ajax.
> And in some cases it's not possible at all. For example, odd rows in a
> table might have a different color than even rows. Typically one kind of
> rows have the same class attribute.
> If wicket will use class attribute as an identifier then there will be
> no way to work with table rows.
Huh? Using class attribute as identifier for Ajax replacement? How did
you came to this conclusion?
-Matej
>
> And it's just an example. In every web design there are many html tags
> with the same class attribute.
>
> Maris
>
> > We are going to stop using ids and move over to class as it make re-use
> > easier and avoids a number of wicket problems with ids... The HTML monkey is
> > not happy though. He reminds me of the Family Guy screaming monkey today.
> >
> >
> >
> > Alex Objelean wrote:
> >
> >> This is about how wicket generates dynamically markupID.
> >>
> >> I have, for instance, the following markup component:
> >>
> >> <input wicket:id="quantity.noOfUnits" />
> >>
> >> The generated markupId for this component looks like the following:
> >> quantity.noOfUnits1232 .
> >>
> >> I suggest to escape any css valid specifiers from the generated markupId,
> >> by replacing them with something else (for instance '_' character).
> >>
> >> The problem appear when I am trying to identify the component by it's id
> >> using some js library (like jQuery) and as a consequence the result of
> >> this query: $("#quantity.noOfUnits1232") is invalid.
> >>
> >> Thank you!
> >>
> >> Alex.
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
