tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Norris (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Created: (TAPESTRY-634) Cannot dynamically set the id for a Form
Date Fri, 09 Sep 2005 18:19:30 GMT
Cannot dynamically set the id for a Form

         Key: TAPESTRY-634
         URL: http://issues.apache.org/jira/browse/TAPESTRY-634
     Project: Tapestry
        Type: Sub-task
  Components: Framework  
    Reporter: Chris Norris

This was initially addressed in case 626 http://issues.apache.org/jira/browse/TAPESTRY-626

Justin's (who is a coworker of mine) real goal in that case was to be able to dynamically
create an id for a form.  We use that id for javascript functions and bug testing.  His issue
was that the framework was generating an ID as well and both were being written as attributes
in the html.  Howard's solution was to disallow informal id tags for Form components by making
"id" a reserved parameter.  I think what we were hoping for was for the framework to not write
a generated id if we specify one, so that the FormSupportImpl's render method would look like:

        	_writer.attribute("id", formId);

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

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

View raw message