Bugs item #1124299, was opened at 2005-02-16 22:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1124299&group_id=119783
Category: core Group: None Status: Open Resolution: None Priority: 5 Submitted By: Juergen Donnerstag (jdonnerstag) Assigned to: Nobody/Anonymous (nobody) Summary: revew apps settings for setStripXX Initial Comment: spent some minutes (confirm or revise) current apps.settings().setStripXXX() naming and usage. Copy from mail discussion ====== I'm not yet sure whether using the already existing setStripComponentNames() is the right way to go. setStripComponentNames() currently removes wicket="xxx" and modifies id="wicket-xxx" => id="xxx". Using setStripComponentNames() means your id="wicket-xx" tag will always be removed and you won't have the chance to end up with id="xxx" without all wicket tag and attr still in. I wonder ... we also have setStripWicketTag() which removes <wicket:xx> from output. I wonder if it makes sense to change that to setStripWicketComponentIdentifiers(): combination of setStripWicketTags() and setStripComponentNames() as it is today. That is removing all wicket specific tags, attrs and attr-value-substrings. And setStripWicketIdAttributes() which if true, removes the whole id attributes if like id="wicket-xxx". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1124299&group_id=119783 ------------------------------------------------------- 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
