Closed
Bug 517700
Opened 15 years ago
Closed 15 years ago
Lightning Categories Pref pane not showing any categories
Categories
(Calendar :: Lightning: SeaMonkey Integration, defect)
Calendar
Lightning: SeaMonkey Integration
Tracking
(Not tracked)
RESOLVED
FIXED
1.0b1
People
(Reporter: iannbugzilla, Assigned: philip.chee)
References
Details
Attachments
(1 file)
1.51 KB,
patch
|
mschroeder
:
review+
|
Details | Diff | Splinter Review |
Using SeaMonkey with Lightning the preferences pane for categories is not showing any categories. Error console shows: Error: parentPrefWindow is null Source File: chrome://calendar/content/preferences/categories.js Line: 64
Should be able to use document.documentElement.instantApply?
Comment 2•15 years ago
|
||
Well, you might want to keep the parentPrefWindow variable, but yes.
Assignee | ||
Comment 3•15 years ago
|
||
(Comment #1 From Ian Neal) > Should be able to use document.documentElement.instantApply? (Comment #2 From neil) > Well, you might want to keep the parentPrefWindow variable, but yes. This patch switches to using document.documentElement. I've tested this and it works in TB+Lighting, SM+Lightning, and in Sunbird.
Assignee: nobody → philip.chee
Status: NEW → ASSIGNED
Attachment #403111 -
Flags: review?(mschroeder)
Updated•15 years ago
|
Attachment #403111 -
Flags: review?(mschroeder) → review+
Comment 4•15 years ago
|
||
Comment on attachment 403111 [details] [diff] [review] Patch v1.0 Use document.documentElement instead. r=mschroeder
Assignee | ||
Updated•15 years ago
|
Keywords: checkin-needed
Assignee | ||
Comment 5•15 years ago
|
||
Checked in to comm-central http://hg.mozilla.org/comm-central/rev/96065ab23c15
Updated•15 years ago
|
Target Milestone: --- → 1.0
Comment 6•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
•