You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In object1, calling object1.toJSDate() will throw toJSDate is not a function, whereas object2.toJSDate() works.
To me, that is unexpected, as I imagine that the absolute time can be inferred from e.g. DTSTART.
In an alarm set to trigger on the "START" of an event or to-do,
the "DTSTART" property MUST be present in the associated event or
to-do. In an alarm in a "VEVENT" calendar component set to
trigger on the "END" of the event, either the "DTEND" property
MUST be present, or the "DTSTART" and "DURATION" properties MUST
both be present. In an alarm in a "VTODO" calendar component set
to trigger on the "END" of the to-do, either the "DUE" property
MUST be present, or the "DTSTART" and "DURATION" properties MUST
both be present.
The text was updated successfully, but these errors were encountered:
I realize this is 4 years ago so it might not be relevant, but if this is still an issue I'd suggest a more condensed test case. The wrapper to Thunderbird adds some complexity, so figuring out if this is an issue with ical.js or the wrapper would be helpful. If you're no longer looking at this feel free to close the issue.
It looks like we haven't heard back on this issue, therefore we are closing this issue. If this problem persists in the latest version of ical.js, please re-open this issue.
When creating a VALARM in a VEVENT on Thunderbird, e.g.:
and this is feed into ical.js, then the parsed result looks like this when getting it as a property with ical.js:
object1
However, when feeding an absolute date, we get a different object as a result:
object2
In object1, calling
object1.toJSDate()
will throwtoJSDate is not a function
, whereasobject2.toJSDate()
works.To me, that is unexpected, as I imagine that the absolute time can be inferred from e.g.
DTSTART
.From https://tools.ietf.org/html/rfc5545#section-3.2.14
The text was updated successfully, but these errors were encountered: