Opened 16 years ago

Closed 15 years ago

#1873 closed enhancement (fixed)

Improve DropdownContainer

Reported by: Eugene Lazutkin Owned by: bill
Priority: high Milestone: 0.9
Component: Dijit Version: 0.9
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by Eugene Lazutkin)

The TimePicker? widget requires up to 3 clicks to set time: one to select an hour, one to select AM/PM, and one to select minutes. It makes the DropdownTimePicker? cumbersome to use: after every click it closes, and has to be re-opened to select a next time component. (See #1872 for merging DatePicker? and TimePicker?, which will require the proposed functionality.)

The DropdownContainer? should support a special mode of operation specified by a separate parameter. After opening the container it should watch for following events:

  1. User pressed Esc button => close it.
  2. User clicked outside the container => close it.
  3. Containing widget requested to close the container (e.g., when user clicked a special "close" button, or made her selection) => close it.
  4. (optional) If a cursor is inside the container, close it when the cursor goes outside.

Change History (4)

comment:1 Changed 16 years ago by Eugene Lazutkin

Description: modified (diff)

comment:2 Changed 16 years ago by Adam Peller

let's also find a standard mechanism to clear out the data, if we decide that's a requirement, preferably in a language neutral way. (To replace the "any" in the current time picker)

comment:3 Changed 15 years ago by Adam Peller

Component: WidgetsDijit

Even with redesign of the timepicker (#599) similar issues may remain. It might be useful to have another gesture such that the user is able to click around the widget and see the results before making a selection.

comment:4 Changed 15 years ago by bill

Resolution: fixed
Status: newclosed

I agree that TimePicker? is painful to use. [ We've basically gotten rid of DropdownContainer? in dijit 0.9. You call PopupManager? to display a dropdown, and connect to onValueChanged. It's up to the "parent" widget about whether or not to close the dropdown on value selected. So I'm going to close this bug (about DropdownContainer?) because I think it's resolved.

Note: See TracTickets for help on using tickets.