397572 - AA.COM "SEND TO OUTLOOK" won't import

Status: RESOLVED WONTFIX

(Calendar :: Import and Export, defect)

Description

[Robert Eden]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: 2007092504

American Airlines (AA.COM) offers a "SEND TO OUTLOOK" feature for your itinerary. That button generates a ICS file for importing in to your calendar.

Importing that ICS into Lightning gives a "this.startDate has no properites" exception.



Reproducible: Always

Steps to Reproduce:
1. Load the attached ICS (or try to)

Actual Results:  
Exception popup with a non-user-friendly message

Expected Results:  
add event to calendar

Comment 1

[Robert Eden]

Attachment: reservation event from American Airlines

Comment 2

[cmtalbert]

Confirmed with latest nightly on Mac OS X, Thunderbird: version 2.0.0.6 (20070728)
Lightning: 2007092503

The times in this ICS file are in floating time.  Did we somehow regress our support for floating time?

Marking blocking ?
I believe that a regression range was sought for this in a related bug 397559 and was not found.  Not sure what was going on there.  Do we need to look for another regression range here?

We also need to do a better job showing a more understandable error message.  Especially in lightning on mac this is a giant stream of "uncomprehendable" (so sayeth the end user) data across the top of your screen.  Not a good user experience in the least.

Good find.

Comment 3

[Stefan Sitter [:ssitter]]

The error is not related to floating times. If you change the two lines from

    DTSTART: 20071002T181500
    DTEND: 20071008T201500

to 

    DTSTART:20071002T181500
    DTEND:20071008T201500

the .ics file imports/opens fine.
-> error is caused by the spaces between property name and value.

Comment 4

[Daniel Boelzle [:dbo]]

RFC 2445 doesn't allow that whitespace. IMO this bug falls into the same category as bug 397559. Do we already have a good whiteboard tag to group those bugs?

Comment 5

[Philipp Kewisch [:Fallen][📱📆]]

We have enough bugs on utf8 issues and making the parser more understanding. Closing this one.