Closed
Bug 1142261
Opened 9 years ago
Closed 9 years ago
Don't split interfaces between libical and ical.js
Categories
(Calendar :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
4.0.0.1
People
(Reporter: Fallen, Assigned: Fallen)
References
Details
Attachments
(1 file, 1 obsolete file)
46.46 KB,
patch
|
darktrojan
:
review+
Fallen
:
approval-calendar-aurora+
|
Details | Diff | Splinter Review |
Dynamically loading the xpt file like we do makes the packager cry when it attempts to link xpts. We don't actually have to do that if we just have an extra interface that extends the base and adds the [notxpcom] methods.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8576268 -
Flags: review?(geoff)
Comment 2•9 years ago
|
||
Comment on attachment 8576268 [details] [diff] [review] Fix - v1 Review of attachment 8576268 [details] [diff] [review]: ----------------------------------------------------------------- I'm no expert on the C++ side of things, but this looks good to me. FWIW more lines of context would've been really useful here. ::: calendar/base/backend/libical/calRecurrenceRule.cpp @@ +211,1 @@ > aRecurEnd->GetInTimezone(cal::UTC(), getter_AddRefs(dt)); What does |dt| do in this method now? Did you mean to use icaldt here?
Attachment #8576268 -
Flags: review?(geoff) → review+
Assignee | ||
Comment 3•9 years ago
|
||
What a great find. Not only was the C++ code wrong, but also it uncovered a bug in ical.js. Here is a new patch with more context and a unit test.
Attachment #8576268 -
Attachment is obsolete: true
Attachment #8576593 -
Flags: review?(geoff)
Updated•9 years ago
|
Attachment #8576593 -
Flags: review?(geoff) → review+
Assignee | ||
Updated•9 years ago
|
Attachment #8576593 -
Flags: approval-calendar-aurora+
Assignee | ||
Updated•9 years ago
|
Keywords: checkin-needed
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → 4.1
Assignee | ||
Updated•9 years ago
|
Target Milestone: 4.1 → 4.0
You need to log in
before you can comment on or make changes to this bug.
Description
•