Request: Better Support For <label> Tag's for= Attribute

Hi,

I consider it important to use ... elements for things like check boxes and radio buttons. Unfortunately, when the control associated with the is generated by, say, , the GSP editor fails to connect the value of the tag's for= attribute and the value of the ]]> tag's id= attribute and produces spurious "Invalid id reference" errors.

It would be nice if the GSP editor would look at id= attributes in the pertinent Grails tags so it would not show so many spurious "Invalid id reference" errors.


Randall Schulz

5 comments
Comment actions Permalink

Hehe,
things are way more complicated than that, since it is HTML plugin complaining, not jetgroovy:) We are searching for a way to make html validation less aggressive.

0
Comment actions Permalink

I don't think making validation "less aggressive" is the best answer, is it? It's no better to be given no indication of bad for= attribute value than it is to be told they're all wrong.

Is there no way for the GSP-specific processing to make the necessary information available to the HTML code? Or perhaps JetGroovy needs to handle GSP pages entirely itself?


Randall Schulz

0
Comment actions Permalink

No,there ain't a way to make HTML plugin aware of g:__ tags, at least none that I know. By less aggressive I mean no errors in this particular case, by telling HTML there is dynamic generation in this GSP.

0
Comment actions Permalink

Doesn't a similar problem arise for JSP with custom tag libraries?

Perhaps the answer is to improve the HTML plug-in so it can be told about content that originates in interleaved non-HTML code.

RRS

0
Comment actions Permalink

Yep, I'm having the same conjecture, and hopefully we can sort it out.

0

Please sign in to leave a comment.