I completely agree with you. But what do you suggest:
parse on the client-side generated markup id and escape this kind of
characters or treat the special case by using document.getElementById
instead of $(), or maybe just give up discussing about this issue?
Martijn Dashorst wrote:
>
> On 9/28/07, Alex Objelean <[EMAIL PROTECTED]> wrote:
>> But as you see, the main drawback of this example is that I cannot access
>> the DOM element mapped to wicket component, because the
>> $("#quantity.unit123") has a different meaning than
>> document.getElementById('quantity.unit123').
>
> As already noted about a zillion times: there is a bug in the
> javascript libraries: this should work:
> $("#quantity\.unit123") == document.getElementById('quantity.unit123')
>
> Martijn
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0-beta3 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
>
>
--
View this message in context:
http://www.nabble.com/-VOTE--WICKET-995-tf4523748.html#a12935347
Sent from the Wicket - Dev mailing list archive at Nabble.com.
