Hi, Tapestry 4 is documented as supporting the "disabled" attribute of HTML Form elements (e.g., INPUT, SELECT, TEXTAREA). Has anyone ever achieved this?
(1) For me, Tapestry puts for component IDs into the hidden "formids" field. However, disabled form elements are by definition not submitted by the web browser. Hence, Tapestry replies to the user with "Stale Link" exceptions. Is this a Tapestry bug? It seems to completely prevent the use of the "disabled" attribute with Tapestry, despite it being documented in the Tapestry framework docs. If this is a bug, I can report it. but I also wonder if I am simply "misuing" the feature. (2) An even more important problem for me is whether anyone could advise how I can implement a workaround? i would happily patch the FormSupport class, except I think I would have to completely supply a new Form.jwc to have my new Form/FormSupport subclasses used. Since that file is quite large and could be subject to change, I want to keep my overrides to a minimum. All I want to do is override the names of the Java classes. I don't think I should have to supply the whole Form.jwc with all the parameter definitions, etc. Is it possible to merely override the class name in the component-specification? (3) Another problem with the handling of disabled form elements is that client-side JavaScript cannot be used to dynamically enable or disable form elements as this will also disrupt the handling of formids :-( This can be overcome with a subclass, if part (2) can be resolved. Thanks for any ideas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
