Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#6685 closed bug (fixed)

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:


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
  1. 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

Change History (3)

comment:1 Changed 12 years ago by Scott González

Component: [meta] ui.docsui.autocomplete
Status: newopen
Summary: appendTo undocumented and Autocomplete Combobox Example bugCombobox: Doesn't handle destroy

Thanks, I've split the documentation bugs into separate tickets:
Autocomplete: #6687
Selectable: #6688
Sortable is already documented.

comment:2 Changed 12 years ago by Scott González

Resolution: fixed
Status: openclosed

Combobox: Added a destroy method. Fixes #6685 - Combobox: Doesn't handle destroy.

Changeset: d97add11b08227b3cbde76c2e93fe50c42a27123

comment:3 Changed 12 years ago by Scott González

Note: See TracTickets for help on using tickets.