Open Bug 359527 Opened 20 years ago Updated 3 years ago

Unifinder shows invalid start date for recurring event set

Categories

(Calendar :: Internal Components, defect)

defect
Not set
major

Tracking

(Not tracked)

People

(Reporter: damian.publicemail, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061103 Calendar/0.4a1 pasted event is not displayed, this is one of many event's which is not visible in main view - only unifinder shows it Reproducible: Always Steps to Reproduce: paste following event: BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN BEGIN:VEVENT CREATED:20061104T180944Z LAST-MODIFIED:20061104T181239Z DTSTAMP:20061104T181239Z SUMMARY:MBO: JVM RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=SA DTSTART;TZID=/mozilla.org/20050126_1/Europe/Warsaw:20061105T194500 DTEND;TZID=/mozilla.org/20050126_1/Europe/Warsaw:20061105T204500 CATEGORIES:Task END:VEVENT BEGIN:VTIMEZONE TZID:/mozilla.org/20050126_1/Europe/Warsaw X-LIC-LOCATION:Europe/Warsaw BEGIN:DAYLIGHT TZOFFSETFROM:+0100 TZOFFSETTO:+0200 TZNAME:CEST DTSTART:19700329T020000 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3 END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:+0200 TZOFFSETTO:+0100 TZNAME:CET DTSTART:19701025T030000 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD END:VTIMEZONE END:VCALENDAR Actual Results: except 5th is presented as 4th and first occurence is skipped (4th is treated as exception) - see in month view event created with the latest nightly build
4th of Nov is not shown and should not be shown, because it is before start date. The start date is 5th of Nov, which is a Sunday --> no display because recurrence rule BYDAY=SA from RFC 2445: The recurrence rule, if specified, is used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained within the iCalendar object. The "DTSTART" property defines the first instance in the recurrence set. --> 5th of Nov should be shown. Probably there is already a bug on this, but I couldn't find it.
Component: Calendar Views → Internal Components
Summary: event is not displayed properly (skips day + exception) → start date not considered in creation of recurrence set
From the draft-ietf-calsify-rfc2445bis-03: The "DTSTART" property value SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value that doesn't match the pattern of the rule is undefined. according to the calsify draft, the current behaviour is correct.
Whiteboard: [qa discussion needed]
This is working as per the spec (2445). Closing as WFM
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Whiteboard: [qa discussion needed]
Testing on Sunbird, I suddenly see the issue that this bug concerns. In the Unifinder on Sunbird, this ICS causes a listing to show up at the "start date" of the recurrence which is on November 5, 2006, which is not even a day that the recurring pattern would fall upon, as Sebastian noted. So, the bug here is as follows: 1. Create this event in sunbird 2. View the unifinder 3. Note that an invalid event occurrence is stated as the starting occurrence in the unifinder. Actual: Invalid start date for recurrence set shown in unifinder Expected: True "next occurrence" date should be shown in the unifinder as the starting of the recurrence set, for this event that should be November 11, 2006. Tested with: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.5pre) Gecko/20070605 Calendar/0.5pre Reopening bug since my searching did not turn up any instances of this bug already being filed. But, I have a feeling it might still be a dupe. Dumpe me?
Severity: major → normal
Status: RESOLVED → REOPENED
Component: Internal Components → Sunbird Only
Resolution: WORKSFORME → ---
Summary: start date not considered in creation of recurrence set → Unifinder shows invalid start date for recurring event set
Might be a dupe of bug 310853, but until we're certain, I'm setting "Depends On"
Severity: normal → major
Component: Sunbird Only → Internal Components
Depends on: 310853
(In reply to comment #2) > From the draft-ietf-calsify-rfc2445bis-03: > > The "DTSTART" property value SHOULD match the pattern of the recurrence rule, > if specified. The recurrence set generated with a "DTSTART" property value that > doesn't match the pattern of the rule is undefined. > > according to the calsify draft, the current behaviour is correct. > Right. Just to mention bug 381415 here which states a related problem: specifying a DTSTART with [multiple] RDATES currently only shows the RDATEs, not the DTSTART. I plan fix calRecurrenceInfo::calculateDates by simply always adding DTSTART to the set of expanded dates. This would also comply with rfc2445bis (sebo's comment).
Status: REOPENED → NEW
OS: Windows XP → All
QA Contact: views → base
Hardware: PC → All
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.