You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/02/03 15:20:14 UTC
[jira] [Commented] (TAP5-1261) Tapestry adds event handlers not
only to form components, but also to simple forms
[ https://issues.apache.org/jira/browse/TAP5-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889497#comment-13889497 ]
Jochen Kemnade commented on TAP5-1261:
--------------------------------------
This issue has come back in Tapestry 5.4.
> Tapestry adds event handlers not only to form components, but also to simple forms
> ----------------------------------------------------------------------------------
>
> Key: TAP5-1261
> URL: https://issues.apache.org/jira/browse/TAP5-1261
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Andy Pahne
> Assignee: Andreas Andreou
> Fix For: 5.2.1
>
>
> After upgrading to Tapestry 5.2.0 I experienced an Javascript error upon submitting a form. It's a plain form defined in the template, not a Form component.
> The error is:
> tapestry.js, line 1462: 'undefined' is null or not an object
> This happened in IE8. It's reproducible with and without enabling IE7 compatible mode. A user on the mailing list suggested that he saw similar error messages in his FF console.
> I saw this for the forst time after upgrading to Tapestry 5.2.0.
> I would expect, Tapestry not interacting with a form in the template, as long as it's plain markup and not a form component.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)