And what are ids like 'mypanel_myfirstlist_item2_mysecondlist_link3_linklabel' going to help you with, besides being complient with the W3C req that ids should be unique (and with which hardly anyone in the amazing world of web development complies to anyway)?
My proposal to remove the ids that are used by wicket alltogether makes sure those ids don't bite you. All the other (non Wicket) ids can be used as before, so, if you want them unique, you can do that. Furthermore, if you want unique ids within eg a list, you can generate them yourself using AttributeModifiers.
Eelco
Yep. I propose to just let go this whole discussion. I mean, we could even go through all components in our projects (which would be hell considering you have to maintain them as well), but how are you going to explain that 'requirement' to users? Nah. What we could do, is use wicket= instead of id="wicket- for all our prefab components. That, together with the option of removing these attributes, would be good enough to ensure that if people really want, they can have unique id's in their pages.
-1
Previewability is lost. Jon's proposal for uniqueness of IDs seems rather simple to implement and would solve a large subset of the problemset. Why not start with that?
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
