Closed Bug 819987 Opened 12 years ago Closed 6 years ago

Date picker: rethink use of colours, highlight etc. for days

Categories

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

defect
Not set
normal

Tracking

(blocking-basecamp:-)

RESOLVED WONTFIX
blocking-basecamp -

People

(Reporter: gerv, Unassigned)

Details

(Keywords: b2g-testdriver, unagi, Whiteboard: [interaction])

- Tapping a date beyond the beginning or end of the current month should select that day but then scroll you to that month. 

- Days in the past should not be greyed out, as there is no guarantee that the current date is correct, so the current date may be "in the past", and greying them out makes people think you can't select them.

- This means we should come up with another way of highlighting the currently-selected day.

- However, days which are outside the current month should be distinctive; this is normal on calendars and helps orient people. Perhaps we could fix this at the same time as the previous 2 bullet points?

Gerv
Could you split this into separate bugs? This sounds like multiple bugs in one.
Component: Gaia → Gaia::System
The last three are connected; let's keep this bug for them. I'll file a new one for the first one.

My concrete suggestion is to have all days in the current month as white text, days outside the current month as grey text, and the currently-chosen day highlighted in some way. If we need a "current choice" plus a different "choice if you click OK", then the current choice could be red text, and the "choice if you click OK could be a thick cursor-like border.

Gerv
Summary: Date picker bugs → Date picker: rethink use of colours, highlight etc. for days
Bug 820008 filed for the first issue listed.

Gerv
blocking- 

UX, please re-nominate or file new bugs if this is considered blocking
blocking-basecamp: ? → -
Whiteboard: [interaction]
Component: Gaia::System → Gaia::System::Window Mgmt
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.