Well I was thinking of an application flag just like stripWicketTags. It is certainly the easiest, and imo also a clean, solution.
Adding a flag or attributemodifier to listitem would imo make things less clear to the users. But you are the developers and I am a user :) Maurice P.S. this is not top priority or anything to me so feel free to pick up other more pressing things first. -----Oorspronkelijk bericht----- Van: Juergen Donnerstag [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 15 februari 2005 11:07 Aan: [email protected] Onderwerp: Re: [Wicket-develop] id of elemets and listviews No you'are right. I was mislead. Removing the whole id attribute is probably not a good solution either as id attributes are sometimes used for CSS. Just removing them from listItems would imo be to much magic and introducing another application flag would open the door for plenty more such switches. If it concerns you, what about an attributeModifier attached to listItem and removing the id attribute. Thus it is the user's decision. In that context it might make sense to just add a flag to ListItem, though. Juergen On Tue, 15 Feb 2005 10:49:53 +0100, Maurice Marrink <[EMAIL PROTECTED]> wrote: > Are you referring to ApplicationSettings.stripComponentNames? > If I read the code correct that only removes the "wicket-" part from the > name and still leaves us with the id attribute. > The use of the wicket attribute could be a solution, but should it not > be possible to remove the entire attribute that makes up the component > name? > In other words remove the id / wicket attribute completely from the > output. > > Or am I missing your point? > > Anyway just my 2 cents. > > Maurice > > -----Oorspronkelijk bericht----- > Van: Juergen Donnerstag [mailto:[EMAIL PROTECTED] > Verzonden: dinsdag 15 februari 2005 10:24 > Aan: [email protected] > Onderwerp: Re: [Wicket-develop] id of elemets and listviews > > 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=ick > _______________________________________________ > 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&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=ick _______________________________________________ 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
