Hi, in some projects i'd like to get rid of the onclick="javascript:return Tapestry.waitForPage(event);' and onsubmit="javascript:return Tapestry.waitForPage(event);" code in the generated html.
That code is generated in AbstractComponentEventLink#beginRender and in Form#beginRender() Initially i though of using some (more) conditionals to change this, but then i noticed that in both cases ClientBehaviorSupport is available and used in the code nearby. And as the ClientBehaviorSupport name suggests, it makes sense for it to be the one responsible for outputting that code ( and in that way give anyone the ability to override its behavior ) So i'm thinking of a new method, ClientBehaviorSupport.addWaitForPage(Element) Do you guys see any problems with thisd approach? If there are no objections, i'll soon add a JIRA and go on with this -- Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr Apache Tapestry PMC / http://chesstu.be owner Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
