current date not highlighted/wrong date highlighted

Bug #1280874 reported by Reece
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Ubuntu 13.10, x86_64, indicator-datetime 13.10.0+13.10.20131023.

indicator-datetime provides *no highlighting at all* for the current date. Worse, it provides faint highlighting for a different date (the date I logged in?). See attached screenshot.

This is related to to several other bugs (below), but the other issues are apx 2 years old and appear to be inactive.

Implications and related UI issues:
- It is too easy for a user to interpret the faint highlighting as today's date.
- If another day has previously been clicked (even days earlier), it remains highlighted. Users will likely expect that the highlighting corresponds to today's date, not that of a click days earlier.
- The lack of a "go to today" button makes it very difficult to focus the date for common use cases (What's today's date? What am I doing today? Tomorrow?)

Related:
https://bugs.launchpad.net/bugs/793450
https://bugs.launchpad.net/bugs/1017595
https://bugs.launchpad.net/bugs/740817
https://bugs.launchpad.net/bugs/1240251
https://wiki.ubuntu.com/TimeAndDate#menu-calendar
---
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2012-10-09 (495 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Tags: saucy third-party-packages
Uname: Linux 3.11.0-15-generic x86_64
UpgradeStatus: Upgraded to saucy on 2013-11-12 (97 days ago)
UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Reece (reece) wrote :
Revision history for this message
John Kim (kotux) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in indicator-datetime (Ubuntu):
status: New → Incomplete
tags: added: saucy
Revision history for this message
John Kim (kotux) wrote :

Also, please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
Reece (reece) wrote : Dependencies.txt

apport information

tags: added: apport-collected third-party-packages
description: updated
Revision history for this message
Reece (reece) wrote : ProcEnviron.txt

apport information

Revision history for this message
Reece (reece) wrote :

apport bug data sent

This is reproducible. Steps:

1) Boot ubuntu.
2) Go to calendar (click indicator-datetime). Select a day in the previous or next month (any day works, but this makes a good example).
3) Click indicator again. The clicked date remains highlighted.

The confusion occurs when there is a long duration between 2 and 3: I forget I've clicked and the highlighted day is NOT today. Personally, I don't see any reason to preserve the selected day between drop down events.

(As an aside, Launchpad has a big button that says "Report a bug". It might be worth recommending ubuntu-bug in that workflow if that's the preferred method for bug reporting. Thanks for your help and I'll use ubuntu-bug next time.)

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Reece, thanks for the report, and sorry for the confusion about ubuntu-bug. Well-meaning triagers sometimes assume that every bug report needs apport info, which ubuntu-bug provides. But sometimes, as in this case, apport info is not relevant at all.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.