tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Andreou (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-1261) Tapestry adds event handlers not only to form components, but also to simple forms
Date Sat, 28 Aug 2010 22:44:54 GMT

    [ 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:
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.

View raw message