Ticket #4240 (closed bug: fixed)

Opened 4 years ago

Last modified 4 years ago

Datepicker: destroy, disable, and enable methods affect sibling datepickers

Reported by: ihumanable Owned by: rdworth
Priority: critical Milestone: 1.7.2
Component: ui.datepicker Version: 1.7.1
Keywords: Cc:
Blocking: Blocked by:

Description

When $(...).datepicker('destroy'); is issued all image buttons (buttons defined during initialization with a buttonImage and buttonImageOnly: true) for all datepickers are removed.

An example is attached, clicking the init startdate and init enddate will place two images on the screen in the correct position and wired properly. Clicking either of the remove buttons, removes both of the images instead of just the one associated with the datepicker being destroyed.

Attachments

datepicker.html Download (954 bytes) - added by ihumanable 4 years ago.
Datepicker HTML Test Case
cal.gif Download (127 bytes) - added by ihumanable 4 years ago.
Sample image used by test case

Change History

Changed 4 years ago by ihumanable

Datepicker HTML Test Case

Changed 4 years ago by ihumanable

Sample image used by test case

comment:1 Changed 4 years ago by joern.zaefferer

  • Priority changed from minor to major
  • Summary changed from Datepicker Destroy Bug to Datepicker destroy affects other datepickers
  • Milestone changed from TBD to 1.7

comment:2 Changed 4 years ago by rdworth

  • Milestone changed from 1.7 to 1.8

comment:3 Changed 4 years ago by rdworth

  • Owner set to rdworth
  • Status changed from new to assigned

Added visual test  http://jquery-ui.googlecode.com/svn/trunk/tests/visual/datepicker/datepicker_ticket_4240.html in r2302

comment:4 Changed 4 years ago by rdworth

  • Status changed from assigned to closed
  • Resolution set to fixed

Fixed in r2303

comment:5 Changed 4 years ago by rdworth

  • Summary changed from Datepicker destroy affects other datepickers to Datepicker: destroy, disable, and enable methods affect sibling datepickers

This also affects 'enable' and 'disable' methods. For all three (destroy, enable, disable) it only affects sibling datepickers. So as a work-around, you can put each datepicker input or div in a wrapper element.

comment:6 Changed 4 years ago by rdworth

  • Priority changed from major to critical

comment:7 Changed 4 years ago by rdworth

  • Milestone changed from 1.8 to 1.7.1

merged to 1.7.1 in r2327

comment:8 Changed 4 years ago by rdworth

  • Status changed from closed to reopened
  • Version changed from 1.6rc6 to 1.7.1
  • Resolution fixed deleted
  • Milestone changed from 1.7.1 to 1.8

appendText is also affected

comment:9 Changed 4 years ago by rdworth

  • Status changed from reopened to closed
  • Resolution set to fixed

fixed in r2350

comment:10 Changed 4 years ago by rdworth

  • Milestone changed from 1.8 to 1.7.2
Note: See TracTickets for help on using tickets.