Hi, Okay, this isn't nearly as silly as it sounds and this email is actually just a call to have the documentation clarified and updated.
The "disabled" attribute for a Submit button is currently loosely documented as : " ... Further, a disabled field ignores any value in the request when the form is submitted." http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/corelib/components/Submit.html I would like it to be more explicit, along the lines of: " ... Further, if bound, the disabled attribute is re-evaluated upon form submission and the "selected" event is only fired should it evaluate to 'false'." For this stumped us in work today for a good half hour - it was because we weren't @Persist'ing our disabled attribute. Our expression was t:disabled="!myObject" and of course 'myObject' because null / false on form submission. As our submit button was enabled and the form submitted, we saw no reason for the event not to fire. I can raise a Jira if appropriate? Steve. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
