Comment 15 for bug 758731

I am not sure what is the best strategy in general for the autocomplete.
I guess that the current JS approach has been an easy way to ensure that all fields identified as indis are correctly converted to autocomplete fields. It is falling indeed if you want to be a bit more complex in your actions (cf. bug #1018272, for which the solution I propose is a bit cumbersome...).
Each field could indeed own its own script & initialisation, but if so I would advocate for a generic flexible component (configured by its parameters) that would allow a consistent code .

Anyway, in my previous patch, the autocomplete.js is only used for its first lines (the HTML extension), not the part transforming the input fields. I then post another patch for this specific bug, which allows taking into account the associated gedcom.