Details
Bug
Closed
Major
Description
All g:form tag elements, including remote tags (like remoteField) that support a NAME parameter should also support or imply the ID parameter. Some of the g:form tags do support or imply the ID parameter with a pattern similar to:
attrs.id = attrs.id ? attrs.id : attrs.name
That is, if the id is set, use the parameter, else set the id parameter to the name parameter.
This really came back to bite me trying to use AJAX and the remoteField. I had to add the following fix to g:remoteField:
def remoteField = { attrs, body ->
def paramName = attrs.paramName ? attrs.remove('paramName') : 'value'
def value = attrs.remove('value')
if(!value) value = ''
// FIX ON NEXT TWO LINES
attrs.id = attrs.id ? attrs.id : attrs.name
out << "<input type=\"text\" id=\"$
\" name=\"$
{attrs.remove('name')}\" value=\"$
{value}\" onkeyup=\""
...
A few other tags in the library(-ies), like g:checkbox, also are missing proper name/id support.
The fix presented above isn't the best for remote tags. I noticed that the "real" problem is that Grails makes an assumption about what the "id" is, namely it's part of the controller-action-id trio. Thus, the remote tags expect and use id current to build the URI for the remote call. If the programmer wants to assign the actual DOM id of the resultant tag in the HTML view, he cannot. The fix above grants the second ability, but removes the current ability to specify controller-action-id.
A more proper fix would be to make the remote* tags accept another ID, perhaps MYID, which is output as the ID of the tag:
attrs.myid = attrs.myid ? attrs.myid : attrs.name
{attrs.remove('myid')}out << "<input type=\"text\" id=\"$
\" name=\"$
{attrs.remove('name')}\" value=\"$
{value}\" onkeyup=\"