Make sure that whatever condition enables the text field on the client
side is followed on the server-side.
That is, it's possible that the data is being submitted just fine, but
server-side, the textfield component is checking disabled, finding
that the condition which specifies whether the component should be
disabled is met, and so discards the data. So, whatever condition
client-side enables the field needs to trigger something to occur on
the server-side so that the server knows, on form submission, that the
field is enabled. There's a good reason for this: it's pretty trivial
to edit a page with a disabled field and enable it, or even use
plugins like firebug to enable the field, against your intentions.
Thus, the submission checks disabled to make sure no tampering has
occurred.
Robert
On Jul 7, 2009, at 7/710:19 AM , haipeng du wrote:
I have TextField component which is disabled when template is
rendered. It
will be enabled from javascript and submit data to server. But the
data
change is not bound back to server. I must render TextField as
enabled to
get data back and I can not use javascript to change the status. Is
that
true? If yes, it does not make any sense.
Also, for hidden field, it does not render id attribute for me with
<input
type="hidden" t:type="hidden" id="someId" value="someValue" /> if I
change
id="someId" to t:id="someId", it will render name attribute instead
of id
attribute.
Thanks.
--
Haipeng Du
Salt Lake City
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
