On Wed, 16 Feb 2005 16:36:57 +0100, Maurice Marrink wrote:
>I really don't want to start this discussion all over again, but I have
>to disagree with you Martijn.
>
>If I develop a closed component I can skip the id attribute completely
>by using the wicket attribute. That way the user can use any id's he
>likes and not worry about id's I used in my component. And since id
>attributes are not required by w3c the browser will uniquely id the
>elements of my components for me.
>
>The only drawback is that the user can't use scripting to access html
>elements in my component without me supplying some way to assign an id
>to an element.
>
>Maurice
Maurice,
This is exactly why I keep on saying this idea is a nonstarter:
because you lose the ability to reference your component using JS or
CSS which is a very big deal.
Gili
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
