You can't simply rename id's if there is a css style attached to it, it will fail. You should at least give users the options to turn this behaviour on or off. But I think giving users the option to remove the wicket name attribute (whether it is id or wicket) is far more preferable over renaming id's.
Maurice -----Oorspronkelijk bericht----- Van: Gili [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 15 februari 2005 16:16 Aan: [email protected] Onderwerp: Re: [Wicket-develop] id of elemets and listviews I don't think removing the wicket attribute will make it compliant with W3. To my understanding, we simply remove the "wicket-" prefix and then the resulting IDs will still be identical. This is something the wicket component should simply be smart enough to handle (guarantee unique IDs based upon its component name). I don't think it's too hard either, you just add an integer after the wicket ID name. You'd probably want to ensure, though, that the 1st ID remains the same for previewability reasons... Gili On Tue, 15 Feb 2005 10:23:34 +0100, Juergen Donnerstag wrote: >Until we find the perfect the solution, you still have the option to >remove the wicket attribute from output which makes it compliant with >w3c. Another solution, though not compliant as well, is to use >wicket="myPanel" instead of id="wicket-myPanel". > >Juergen > > >On Tue, 15 Feb 2005 10:15:26 +0100, Maurice Marrink ><[EMAIL PROTECTED]> wrote: >> Hi, >> >> Not to be a pain in the ass or anything but I foresee a problem with the way >> id's are used in listviews >> >> Currently if I use a listview I have to specify it the following way >> >> <span id="wiket-list"> <span >> id="wicket-listitem"><!--content--></span></span> >> >> This generates a number of span's with the same id, namely "wicket-listitem" >> >> Again according to w3c an id should be unique within a document >> http://www.w3.org/TR/html401/struct/global.html#adef-id >> >> Although most browsers don't seem to have a problem with it, it might cause >> problems when trying to access the elements from within javascript. >> getElementById just to name 1. >> >> I am not sure how this is solved best, but I think it should be solved >> sooner or later. >> >> Maurice >> >> ------------------------------------------------------- >> 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_ide95&alloc_id396&opclick >> _______________________________________________ >> Wicket-develop mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/wicket-develop >> > > >------------------------------------------------------- >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_ide95&alloc_id396&op=click >_______________________________________________ >Wicket-develop mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- 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 ------------------------------------------------------- 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_ide95&alloc_id396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
