[jira] [Commented] (TAP5-2066) "tagName" property name in a form that renders a zone leads to an "Forms require that the request method be POST and that the t:formdata query parameter have values." error

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973545#comment-13973545 ] 

Howard M. Lewis Ship commented on TAP5-2066:
--------------------------------------------

This is a general problem, the roots are a client-side conflict between the property name, "tagName" which conflicts with JavaScript's Element.tagName property.

Without a stack trace or the details of what gets submitted in the request, I can't see why it would fail ... and given how much the client-side code in Tapestry 5.4

> "tagName" property name in a form that renders a zone leads to an "Forms require that the request method be POST and that the t:formdata query parameter have values." error
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-2066
>                 URL: https://issues.apache.org/jira/browse/TAP5-2066
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.6
>            Reporter: René Bernhardsgrütter
>            Assignee: Howard M. Lewis Ship
>
> When I name a property "tagName" that's used in a form which submission leads to a zone update, I get the following error: "Forms require that the request method be POST and that the t:formdata query parameter have values.".
> After I renamed the "tagName" property to "userTagName", it worked correctly.
> Example:
> Java: 
>     @Property
>     private String tagName;
>     @Component
>     private Zone tagZone;
> TML:
>     <t:zone t:id="userTagZone" id="userTagZone">
>         <!-- updated content -->
>         <t:form t:id="addForm" t:zone="userTagZone">
>             <t:textfield t:id="tagName" t:mixins="autocomplete"/>
>         </t:form>
>     </t:zone>
> It doesn't matter whether the form is in or out of the zone. I've tested the same also with this jumpstart page (http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/formmultiplezoneupdate) and a fresh Tapestry installation.
> This problem could be related to this:
> https://mail-archives.apache.org/mod_mbox/tapestry-users/201209.mbox/%3C504A3CC9.1000202@cerder.com%3E (I cannot reproduce this with the form/zone constellation here, but it goes in a similar manner.)
> http://tapestry.1045711.n5.nabble.com/t5-3-1-Heads-up-for-special-form-field-names-similar-to-InternalSymbols-PRE-SELECTED-FORM-NAMES-td5101482.html 
> The big problem is not the bug itself, but that it's very hard to find. I've spent almost one and a half days to find it.
> A simple warning or error message, that would be displayed when such critical property names are in use, would do it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)