Closed
Bug 387527
Opened 17 years ago
Closed 17 years ago
Change weekview to 'workweek days only' -> weekview gets unuseble
Categories
(Calendar :: Calendar Frontend, defect)
Calendar
Calendar Frontend
Tracking
(Not tracked)
VERIFIED
FIXED
0.7
People
(Reporter: andreas.treumann, Assigned: Fallen)
References
Details
(Keywords: regression)
Attachments
(1 file)
1.53 KB,
patch
|
dbo
:
review+
|
Details | Diff | Splinter Review |
STEPS TO REPRODUCE: =================== - start thunderbird with the 7-days-weekview - change the view to 'weekview days only' - try to create a event via drag and drop RESULT: ======= - the new event isn't visible in the weekview EXPECTED RESULT: ================ - the event should be visible REPRODUCIBLE: ============= - always JS-Console: kid has no properties chrome://calendar/content/calendar-multiday-view.xml line 2969 Bug 369848 seems to be the root cause.
Comment 1•17 years ago
|
||
Philipp, as your patch seems to have caused this, can you please take a look.
Comment 2•17 years ago
|
||
Confirmed as regession from Bug 369848: Works in sunbird-0.5pre.en-US.win32-2007-06-29-05-mozilla1.8 Fails in sunbird-0.5pre.en-US.win32-2007-06-29-09-mozilla1.8 Checkins between 2007-06-29 05:00 and 2007-06-29 10:00 : Bug 369848, Bug 264150 [http://tinyurl.com/39qj5s]
Blocks: 369848
Keywords: regression
Assignee | ||
Comment 3•17 years ago
|
||
This fixes it. I used the wrong iterator for childNodes.
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Attachment #272628 -
Flags: review?(daniel.boelzle)
Updated•17 years ago
|
Attachment #272628 -
Flags: review?(daniel.boelzle) → review+
Updated•17 years ago
|
Flags: blocking-calendar0.7+
Target Milestone: --- → 0.7
Assignee | ||
Comment 4•17 years ago
|
||
Checked in on HEAD and MOZILLA_1_8_BRANCH -> FIXED
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•17 years ago
|
||
Verified with lightning build 2007071904 (windows, linux) and Sunbird 20070719 at linux -> task is fixed.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•