First I'd like to thank Markus for this module and all of the modules he has contributed to the community and continues to diligently support -- they have really allowed us to build some great and intuitive web apps for internal use within our company.
The issue we are consistently having with this module is that following the creation of a new node via the 'Create and Reference' functionality provided by the Node Relationships (Extras) module (when the child window has been submitted, and automatically closed), the parent window's autocomplete fields no longer function appropriately. Basically, when search criteria are entered into these fields, the results display, but do not clear once a selection is made. They ONLY clear when the submit button has been pressed. The first time submit is pressed the results from all autocompletes having entered search criteria clear, and the second time submit is pressed the form actually submits.
I'm guessing there is an issue with how the autocomplete javascript is triggering off the submittal of the child / modal form which is causing these issues in the parent form. My hope is this is a quick fix for someone familiar with the autocomplete js -- my assumption is that we somehow need to 'reset' the state of the parent form/window after the modal/child has submitted and closed.
I have reproduced this issue with both JQuery 1.2.6 JQUI 1.6 as well as with JQuery 1.3.x and JQUI 1.7
We have documented this issue as occuring with any field supporting the autcomplete widget (taxonomy, node reference, user reference etc).
Comments
Comment #1
markus_petrux commentedOops! I can also reproduce this issue. It seems related to mouse events of autocomplete widgets on the parent window, broken by just opening and closing a Modal Frame.
Not sure when (too busy right now), but I'll try to debug this issue when I have the time, if no one else has in the meantime.
Marking the issue as needs work, so I know I already visited this issue, and it probably needs a patch...
Comment #2
markus_petrux commentedWell, it seems onblur() events attached by autocomplete behavior are not fired after a Modal Frame has been closed. I've spent a lot of time trying to figure out the cause, but I've been unable to. :(
There's a quick fix however, that seems to solve the issue. I'm not enterily happy with it, but...
I have committed to CVS the following:
http://drupal.org/cvs?commit=306544
We may re-open this issue when we have a better solution, though. For now, the problem seems to be fixed on our end.