Closed (works as designed)
Project:
Hierarchical Term Reference Autocomplete
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Apr 2015 at 22:12 UTC
Updated:
6 Apr 2015 at 19:46 UTC
Jump to comment: Most recent
Comments
Comment #1
arpieb commentedThe main reason we went with the autocomplete vs a select-based option was that some of the vocabularies in question were incredibly large, and rendering a JS-interpreted version of very large select field was causing performance issues on the browser side.
If Chosen + Taxonomy Container provide a solution that works better now, glad to hear there is another solution available!