[TAPESTRY-634] Cannot dynamically set the id for a Form

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.1
• Component/s: Framework
• Assignee: Unassigned
• Reporter: Chris Norris
• Created: 10/Sep/05 03:19
• Updated: 23/Jul/06 15:34
• Resolved: 23/Jul/06 15:34

Description

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:

if(!_form.getBindingNames().contains("id"))

{ _writer.attribute("id", formId); }