multiple DESCRIPTION entries per each VEVENT

RESOLVED INVALID

Status

Calendar
General
RESOLVED INVALID
8 years ago
8 years ago

People

(Reporter: bl8n8r, Unassigned)

Tracking

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Lightning creating multiple description entries between VEVENT tags

Lighting seems to be creating multiple DESCRIPTION entries in between VEVENT tags in the calendar file.

Reproducible: Always

Steps to Reproduce:
1.add an event to remote calendar file via lightning
2.cat ics file on calendar server
3.scratch head/look confused when noticing two DESCRIPTION entries in output
Actual Results:  
multiple DESCRIPTION entries

Expected Results:  
only one DESCRIPTION entry per VEVENT

Can't tell if this is actually allowed per the RFC (http://www.ietf.org/rfc/rfc2445.txt).  I don't see anything about *not* having multiple DESCRIPTION properties:


BEGIN:VEVENT
CREATED:20100427T171558Z
LAST-MODIFIED:20100427T171602Z
DTSTAMP:20100427T171602Z
UID:8c1a9dea-fcfa-4cf1-9c79-c4d3e1e71b78
SUMMARY:test24
DTSTART;TZID=America/Chicago:20100429T130000
DTEND;TZID=America/Chicago:20100429T140000
DESCRIPTION:test24                           <<<<< here
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-PT15M
DESCRIPTION:Default Mozilla Description       <<<<< here
END:VALARM
END:VEVENT
(Reporter)

Comment 1

8 years ago
Thunderbird version: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3

Lightning version: Lightning 1.0b1
Component: General → General
Product: Thunderbird → Calendar
QA Contact: general → general

Comment 2

8 years ago
Only one DESCRIPTION property belongs to the VEVENT component. The other DESCRIPTION property belongs to the contained VALARM component. As you can read on <http://tools.ietf.org/html/rfc5545#section-3.6.6> description is a valid property for the alarm component.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.