Potential Problem with the Grails RichUI Plugin AutoComplete Tag

I’ve been using the Grails RichUI plugin and have found a few of the tags it provides to be very useful. The one I’m using the most is the AutoComplete tag which I may well be writing more about in the near future. However, tonight I found a potential issue with the way it creates the YUI data source for the component – it seems it always gives it the same name: ‘autoCompleteDataSource’.

It appears that in common use it’s not a problem. Even if you have multiple AutoComplete tags in the page the YUI components are all initialised correctly, so it will only be an issue if you have your own global variable named autoCompleteDataSource.

Not a major issue, but I raised a bug in the Grails JIRA since the AutoComplete tag already allows you to set the name of the component using the yuiVariableName attribute so it’s a pretty easy fix.

Advertisements

One thought on “Potential Problem with the Grails RichUI Plugin AutoComplete Tag

  1. “The one I’m using the most is the AutoComplete tag which I may well be writing more about in the near future. However, tonight I found a potential issue with the way it creates the YUI data source for the component – it seems it always gives it the same name: ‘autoCompleteDataSource’.”
    How much is it true?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s