You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Andy Pahne (JIRA)" <ji...@apache.org> on 2010/08/28 00:25:54 UTC
[jira] Created: (TAP5-1261) Tapestry adds event handlers not only
to form components, but also to simple forms
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
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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1261) Tapestry adds event handlers not only to
form components, but also to simple forms
Posted by "Andreas Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Andreou closed TAP5-1261.
---------------------------------
Fix Version/s: 5.2.1
Resolution: Fixed
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1261) Tapestry adds event handlers not only
to form components, but also to simple forms
Posted by "Andreas Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903904#action_12903904 ]
Andreas Andreou commented on TAP5-1261:
---------------------------------------
Yep, the error is:
Error: firstHidden is undefined
Source File: http://127.0.0.1:8080/tapestwitter/assets/1.0-SNAPSHOT/tapestry/tapestry.js
Line: 1462
and happens because tapestry assumes there are always inputs with type="hidden" in forms.
That's true for tapestry forms, but not always the case with manual forms
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1261) Tapestry adds event handlers not only
to form components, but also to simple forms
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903921#action_12903921 ]
Hudson commented on TAP5-1261:
------------------------------
Integrated in tapestry-5.2-freestyle #181 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/181/])
fixes TAP5-1261
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1261) Tapestry adds event handlers not only to
form components, but also to simple forms
Posted by "Andreas Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Andreou closed TAP5-1261.
---------------------------------
Fix Version/s: 5.2.1
Resolution: Fixed
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1261) Tapestry adds event handlers not only
to form components, but also to simple forms
Posted by "Andreas Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903904#action_12903904 ]
Andreas Andreou commented on TAP5-1261:
---------------------------------------
Yep, the error is:
Error: firstHidden is undefined
Source File: http://127.0.0.1:8080/tapestwitter/assets/1.0-SNAPSHOT/tapestry/tapestry.js
Line: 1462
and happens because tapestry assumes there are always inputs with type="hidden" in forms.
That's true for tapestry forms, but not always the case with manual forms
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1261) Tapestry adds event handlers not only
to form components, but also to simple forms
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903921#action_12903921 ]
Hudson commented on TAP5-1261:
------------------------------
Integrated in tapestry-5.2-freestyle #181 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/181/])
fixes TAP5-1261
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-1261) Tapestry adds event handlers not only
to form components, but also to simple forms
Posted by "Andreas Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Andreou reassigned TAP5-1261:
-------------------------------------
Assignee: Andreas Andreou
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-1261) Tapestry adds event handlers not only
to form components, but also to simple forms
Posted by "Andreas Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Andreou reassigned TAP5-1261:
-------------------------------------
Assignee: Andreas Andreou
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.