Closed Bug 306029 Opened 19 years ago Closed 19 years ago

Current day does not change at midnight

Categories

(Calendar :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: fbonny, Assigned: mostafah)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.7.10) Gecko/20050725 Firefox/1.0.6 (Ubuntu package 1.0.6)
Build Identifier: 

The current day does not change if you let Sunbird running at night.

Reproducible: Always

Steps to Reproduce:
1. Start Sunbird
2. Let it open for a night
3. Look at the current day

Actual Results:  
The current day is still the day you start Sunbird.

Expected Results:  
Sunbird have to change the current day at midnight.
It should change.  What version of Sunbird are you using?  You can find this in
Help->About.  If you originally reported this using Sunbird 0.2, please test
using a nightly build and see if the problem also occurs there.
Sorry, the UA in my report is from Firefox. Sunbird's version is:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050720 Mozilla
Sunbird/0.2+
(In reply to comment #2)
> Sorry, the UA in my report is from Firefox. Sunbird's version is:
> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050720 Mozilla
> Sunbird/0.2+

I think the problem you're describing was fixed in bug 256223, on 16 Aug.  Is
there a reason you're still using a build from 20 July?  Nightly builds are
available every night here:
http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk/
(In reply to comment #3)
> I think the problem you're describing was fixed in bug 256223, on 16 Aug.  Is
> there a reason you're still using a build from 20 July?

Yes, I use Sunbird for business so I can't update too much and be a early
adopter for this product. When I wasn't my own boss, I used to update Mozilla
every morning and know how it can be addictive. :-)

I'll try with a nightly this evening and tell you.

(In reply to comment #4)
> I'll try with a nightly this evening and tell you.

Another try with the 2005-08-25 nightly.

In fact I don't if it's a bug but it seems me very logical. I click on "go to
today" and friday is selected (blue background). I expect that at midnight
Saturday is selected (week view). Actually, "go to today" is "stateless".

I've never tried with a day view but I suppose the visible day stay up-to-date,
isn't it?
(In reply to comment #5)
> I've never tried with a day view but I suppose the visible day stay up-to-date,
> isn't it?

Ok, my supposition is false. Is there a way to keep a day view up-to-date?
(In reply to comment #6)
> (In reply to comment #5)
> > I've never tried with a day view but I suppose the visible day stay up-to-date,
> > isn't it?
> 
> Ok, my supposition is false. Is there a way to keep a day view up-to-date?

There currently isn't a way to do this.  To me, adding this functionality would
likely confuse more users than it helps.  Imagine working on your calendar
around midnight.  Some changes you're trying to make could end up on the wrong
day, because the selected day changed while you were working.

Clicking 'Go To Today' is fairly simple.  I don't feel that saving the user
these couple clicks is worth it.  As always, though, I'm open to counter arguments.

(In reply to comment #7)
> There currently isn't a way to do this.  To me, adding this functionality would
> likely confuse more users than it helps.  Imagine working on your calendar
> around midnight.  Some changes you're trying to make could end up on the wrong
> day, because the selected day changed while you were working.

In fact, I have a problem at the opposite: I sometimes write something for
yesterday instead of today. :-(

> Clicking 'Go To Today' is fairly simple.  I don't feel that saving the user
> these couple clicks is worth it.  As always, though, I'm open to counter
arguments.

Is there a way to make the current day more visible: different background,
symbol or something else? I'm thinking about a chrome CSS.
> Is there a way to make the current day more visible: different background,
> symbol or something else? I'm thinking about a chrome CSS.
The current day already has a thick border. If that's not enough I think you can
play around with the themes in calendar.jar to change it, I'm not sure though.
(In reply to comment #9)
> The current day already has a thick border. If that's not enough I think you can
> play around with the themes in calendar.jar to change it, I'm not sure though.

Wow, so discreet I've never seen it before. :-/

In calendar.jar/chrome/skin/classic/calendar-views.css, add
.week-view-hour-box-class[today="true"]
{
   background-color     : yellow;
}
is a good solution for me. Just wait for the night to see if it's the definitive
one.
(In reply to comment #10)
> In calendar.jar/chrome/skin/classic/calendar-views.css, add
> .week-view-hour-box-class[today="true"]
> {
>    background-color     : yellow;
> }
> is a good solution for me. Just wait for the night to see if it's the definitive
> one.

After a night with Sunbird running, the yellow day is... today! It works. :-)
RIP, bug 306029?
(In reply to comment #11)
> After a night with Sunbird running, the yellow day is... today! It works. :-)
> RIP, bug 306029?

I don't understand.  Are you proposing this as a code solution that should be
adopted?  Or are you saying that no work needs to be done on this bug and
theming is sufficient? (Change it to Resolved: INVALID)

(In reply to comment #12)
> I don't understand.  Are you proposing this as a code solution that should be
> adopted?  Or are you saying that no work needs to be done on this bug and
> theming is sufficient? (Change it to Resolved: INVALID)

I understand the reason why the selected day can't change automatically (comment
#7) and there's a way to make the current day more visible (my solution is
always up-to-date). So I think this bug can be invalided. An extension could be
done to make an UI to choose a color but there's no need for RFE just for that,
in my opinion.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.