Closed
Bug 499540
Opened 15 years ago
Closed 15 years ago
Multiweek View: changing Number of Weeks via View menu fails
Categories
(Calendar :: Calendar Frontend, defect)
Calendar
Calendar Frontend
Tracking
(Not tracked)
VERIFIED
FIXED
1.0b1
People
(Reporter: ssitter, Assigned: mschroeder)
Details
Attachments
(1 file)
892 bytes,
patch
|
ssitter
:
review+
|
Details | Diff | Splinter Review |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090621 Calendar/1.0pre (BuildID: 20090621002041) Steps to Reproduce: 1. Start Sunbird 2. Switch to Multiweek View 3. Change displayed weeks via menu View > Number of Weeks. Actual Results: Change fails. Number of weeks stay the same. Console shows: WARNING: Trying to set pref calendar.weeks.inview to with the wrong type!: file e:/dev/comm-central/src/mozilla/modules/libpref/src/prefapi.cpp, line 722 JavaScript error: , line 0: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch2.setCharPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://calendar/content/calUtils.js :: setPref :: line 524" data: no] This fails in older 1.0pre builds too, therefore the regression range is somewhere between Sunbird 0.9 and 1.0pre.
Assignee | ||
Comment 1•15 years ago
|
||
In the property setter for 'weeksInView' in calendar-views.xml, you get for 'typeof(val)' 'string'.
Reporter | ||
Comment 2•15 years ago
|
||
Comment on attachment 384419 [details] [diff] [review] Patch v1 r=ssitter
Attachment #384419 -
Flags: review?(ssitter) → review+
Assignee | ||
Comment 3•15 years ago
|
||
Pushed to comm-central <http://hg.mozilla.org/comm-central/rev/19225b221840> -> FIXED
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
OS: Windows XP → All
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → 1.0
Comment 4•14 years ago
|
||
verified with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9pre) Gecko/20100305 Calendar/1.0b2pre
Status: RESOLVED → VERIFIED
Comment 5•13 years ago
|
||
These bugs are likely targeted at Lightning 1.0b1, not Lightning 1.0. If this change was done in error, please adjust the target milestone to its correct value. To filter on this bugspam, you can use "lightning-10-target-move".
Target Milestone: 1.0 → 1.0b1
You need to log in
before you can comment on or make changes to this bug.
Description
•