Opened 9 years ago

Closed 7 years ago

#6152 closed bug (notabug)

datepicker ui-state-active should take precedence over ui-state-highlight

Reported by: dhx Owned by:
Priority: minor Milestone: 1.11.0
Component: ui.datepicker Version: 1.8.5
Keywords: Cc:
Blocked by: Blocking:

Description

Currently the datepicker CSS files place the rules for the .ui-state-active before .ui-state-highlight and thus the rules from .ui-state-highlight take precedence over the rules of .ui-state-active.

This poses a problem for the datepicker when the current day is highlighted using the .ui-state-highlight class. If a user selects the current day in the datepicker, the .ui-state-highlight rule is applied with precedence over .ui-state-active. Thus the user is unaware that they have selected the current day as all they see is the highlight style for the current day.

Ideally the CSS properties of the .ui-state-active selector should be applied with precedence over the properties of ui-state-highlight in the datepicker. This allows users to clearly see their selection for all days (including the current highlighted day).

Change History (3)

comment:1 Changed 9 years ago by dhx

Suggestion:

Redefine the ui-state-active rules in the datepicker section of the themes:

.ui-datepicker .ui-state-active {...}

This would ensure that the active selection style is applied with precedence over the currently highlighted day in the datepicker.

Perhaps this style could be different to inform the user that they have not only selected a particular day, but that day is also the current day?

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

Milestone: TBD1.11.0

comment:3 Changed 7 years ago by mikesherov

Resolution: notabug
Status: newclosed

This works as expected and is the desired behavior

Note: See TracTickets for help on using tickets.