okay. i was thinking about the case where someone's trying to style a wicket component somehow and wants to use the id. but in that case, they'd just assign an id and it would still use the wicket = "message" form.
but if wicket is going to remove the <wicket:x> tags, what does it do with any attributes set on the tag? for example if someone is trying to apply a css style to the thing with id = "x"?
am i making sense or am i confused? ;-)
Eelco Hillenius wrote:
If we would use wicket="message", there would be no problem at all, as the whole uniqueness of elements is determined by its id (id=""). And finally, if users want to be totaly complient, we could strip wicket="message" alltogether if that option would be set.
Eelco
Jonathan Locke wrote:
but we should still fix the namespacing of reusable components, right? otherwise some poor sucker gives their component the id "message" and takes a day to figure out that the feedback panel already took that css id, right?
------------------------------------------------------- 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_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
