Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#6029 closed bug (fixed)

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

Change History (4)

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

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

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

Resolution: → fixed
Status: new → closed

Fixed in ​dda7bcb.

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

Milestone: 1.9 → 1.8.6

comment:4 Changed 9 years ago by Scott González

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

Note: See TracTickets for help on using tickets.