Closed Bug 289229 Opened 20 years ago Closed 20 years ago

[RFE] New Event defaults to current date rather than date selected on calendar

Categories

(Calendar :: Internal Components, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 275357

People

(Reporter: furrealpaw, Assigned: shaver)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20050203 Mozilla Sunbird/0.2

[RFE] When entering a new event, I have the habit of clicking on the date of the
event on the large calendar, if it is in view, or the small calendar, if in a
different week range or month.  But when I bring up the "new event" screen, the
default date that appears is the current (today's) date.  It would seem more
"natural" to me if the default new event date were the date that is
selected/highlighted on the large calendar.

Reproducible: Always

Steps to Reproduce:
1.Click on any date on a multiweek or monthly large calendar
2.Click on the 'new event' icon
3.

Actual Results:  
In the New Event window, the date that appears is today's date

Expected Results:  
In the New Event window, show the date highlighted on the large calendar
Reporter:
    Sunbird already seems to be functioning exactly as you desired, for me.  I'm
also running Sunbird 0.2 (20050203) on WinXP.  I tried everything I could think
of to confuse it about the date (clicking somewhere else in between clicking a
date and selecting new event), but it always opened the new event window with
the correct date of the selected day.  I checked all views and they behave
appropriately.  Could you try and provide additional information about how to
reproduce this?  If it's happening to you, as you described, I'd call it more of
a bug than an RFE.
Maybe it's really New Task (Bug 275357) ?
On geka's suggestion, I'll give the reporter the benefit of the doubt and mark
this a duplicate of bug 275357.

*** This bug has been marked as a duplicate of 275357 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.