[
https://issues.apache.org/jira/browse/TAPESTRY-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621499#action_12621499
]
Sean Redmond commented on TAPESTRY-2575:
----------------------------------------
Well, I was creating a demo page to recreate the problem and couldn't. I
tracked it down to my method of submitting forms.
I created a SubmitLink component which embeds a hidden submit button and
triggers it's click event via javascript.
The render section of the component is
// now the submit
writer.element("input", "type", "submit", "name", elementName, "id",
getClientId(), "style","display:none;");
writer.end();
// now the link
writer.element("a", "href", "#", "name", elementName +
"Link","onclick",
"javascript:document.getElementById('"+getClientId()+"').click()");
_resources.renderInformalParameters(writer);
Up until now, this has worked very well and enables one to create better image
based buttons with dynamic text vs the standard submit button currently
available.
So the problem is really related to javascript triggered submit's from other
events.
> Disabled fields still perfom client side validation in 5.0.13
> -------------------------------------------------------------
>
> Key: TAPESTRY-2575
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2575
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.13
> Reporter: Sean Redmond
> Assignee: Howard M. Lewis Ship
> Fix For: unspecified
>
>
> When disabling Fields (eg. TextField) by setting disabled=true to use them
> as displaying only components, those components still perform client side
> validation and show error messages
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
