[jira] Commented: (TAPESTRY-1131) Hidden Component (maybe all FormComonents?) don't get ids assigned on a page basis.

["Andreas Andreou (JIRA)" <ta...@jakarta.apache.org>]

    [ http://issues.apache.org/jira/browse/TAPESTRY-1131?page=comments#action_12446550 ] 
            
Andreas Andreou commented on TAPESTRY-1131:
-------------------------------------------

Yep, this indeed happens...

In tacos this was fixed by introducing a parameter in AjaxForm
that would make name and id generation depend on component's idPath (instead of id)
Here's the changeset: http://fisheye3.cenqua.com/changelog/tacos?cs=348

I'm thinking of a less intrusive solution for Tapestry... 
Perhaps in formSupport.getElementId...

> Hidden Component (maybe all FormComonents?) don't get ids assigned on a page basis.
> -----------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1131
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1131
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 4.1.1
>            Reporter: Patrick Moore
>
> 1. create a component with a form containing a hidden field
> 2. instantiate this component twice on the same page
> 3. look at generated source.
> notice that both hidden fields have the same id. This screws up javascript trying to use javascript functions to get the unique hidden field.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org