Martijn, Maurice and I had an offline discussion about the whole thing.
There are definitively pro's (like being complient, for generated JS,
etc) and con's (using non-generated JS etc) for the whole case. We would
be +1 for making this configurable. It would be a setting (default to
true?) that when true, would replace the id attribute values (if id is
used as the wicket attribute) with the unique path to that component
(but probably without the pagenumber and rendering). Besides being a
global setting, it is likely (we think) that people want to override
this on a page basis.
Jonathan, Juergen, would that be hard to implement? And do you agree?
Eelco
-------------------------------------------------------
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
