Search and Top Navigation
#6685 closed bug (fixed)
Opened November 22, 2010 10:08PM UTC
Closed November 23, 2010 01:23PM UTC
Last modified December 08, 2010 06:39PM UTC
Combobox: Doesn't handle destroy
Reported by: | perlpunk | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.8.7 |
Component: | ui.autocomplete | Version: | 1.8.4 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
I decided to adapt your example of a combobox in the Autocomplete documentation for my interface and found a slight issue while using it.
1. While looking through the UI.Autocomplete widget I found that the option 'appendTo' is not in the documentation on the web site; which is very useful option by the way. It seems to be listed for some controls but not all that its available for. The follow is has appendTo as an undocumented option: Autocomplete, Selectable, and Sortable
2. The bug with the Combobox example comes when using it in an area on the page that has its content regularly reloaded, like on a timer. The autocomplete lists for the input/combobox become orphaned. This is because they are a child of the BODY not the parent of the SELECT, which is eventually unloaded. This really isn't a huge issue though I found just adding; 'appendTo: select.parent()' to the widget _create function fixed the issue.
Nevertheless- still love the interface, keep up the good work!
Thanks,
Brian
Attachments (0)
Change History (3)
Changed November 23, 2010 01:12PM UTC by comment:1
component: | [meta] ui.docs → ui.autocomplete |
---|---|
status: | new → open |
summary: | appendTo undocumented and Autocomplete Combobox Example bug → Combobox: Doesn't handle destroy |
Changed November 23, 2010 01:23PM UTC by comment:2
resolution: | → fixed |
---|---|
status: | open → closed |
Combobox: Added a destroy method. Fixes #6685 - Combobox: Doesn't handle destroy.
Changeset: d97add11b08227b3cbde76c2e93fe50c42a27123
Changed December 08, 2010 06:39PM UTC by comment:3
milestone: | 1.9 → 1.8.7 |
---|
Thanks, I've split the documentation bugs into separate tickets:
Autocomplete: #6687
Selectable: #6688
Sortable is already documented.