#6029 closed bug (fixed)

Opened September 08, 2010 08:52AM UTC

Closed September 27, 2010 01:11PM UTC

Last modified November 19, 2010 06:26PM UTC

Autocomplete: Custom item can be activated (and result in error) on PageUp/PageDown key click

Reported by: dziastinux Owned by:
Priority: major Milestone: 1.8.6
Component: ui.autocomplete Version: 1.8.4
Keywords: Cc:
Blocked by: Blocking:
Description

The problem lies in unsafe functions:

  • ui.menu.nextPage
  • ui.menu.previousPage

There unsafe selectors are used (:first, :last)

Autocomplete demo with categories is provided. If first menu item is category than these selectors will select non menu item and try to activate it resulting in error.

next and previous function do not have this error (as they use .ui-menu-item:first selector).

Attachments (0)
Change History (4)

Changed September 27, 2010 12:22PM UTC by scottgonzalez comment:1

summary: Custum item can be activated (and result in error) on PageUp/PageDown key click → Autocomplete: Custom item can be activated (and result in error) on PageUp/PageDown key click

Changed September 27, 2010 01:11PM UTC by scottgonzalez comment:2

resolution: → fixed
status: new → closed

Fixed in dda7bcb.

Changed October 25, 2010 06:53PM UTC by scottgonzalez comment:3

milestone: 1.9 → 1.8.6

Changed November 19, 2010 06:26PM UTC by Scott González comment:4

Autocomplete (Menu): Only traverse through .ui-menu-item elements for paging. Fixes #6029 - Autocomplete: Custom item can be activated (and result in error) on PageUp/PageDown key click.

Changeset: dda7bcb6383ed0fee9dcd1ae5f0a6e1dcc160c6b