Nah, XUL *needs* it. Wicket doesn't properly parse it.
e.g. <html:form will result in a ComponentTag with tagName 'html'. The FormComponent checks whether the tag name == 'form', which thus fails.
Eelco
Gili wrote:
Sorry, I don't get it. I get that XUL doesn't handle namespaces properly but I don't understand the proposed workaround. What is this about a namespace property for ComponentTag?
Gili
On Mon, 3 Jan 2005 23:40:31 +0100, Juergen Donnerstag wrote:
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
