Closed
Bug 87027
Opened 23 years ago
Closed 23 years ago
help from prefs displays no content
Categories
(SeaMonkey :: Help Documentation, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bugzilla, Assigned: oeschger)
Details
Attachments
(1 file)
found this with 8:07pm debug mozilla build on linux. 1. bring up Preferences dialog. 2. click Help button. observe: the resulting Help window doesn't display any content in the righthand panel. shouldn't there...be something there? also, after clicking the Help button, i get the following assertion: Enabling Quirk StyleSheet Enabling Quirk StyleSheet loading help content: chrome://help/locale/cs_nav_prefs_navigator.html#Navigator###!!! ASSERTION: NS_ENSURE_TRUE(NS_SUCCEEDED(LoadURI(uri, 0, aLoadFlags))) failed: '(!((LoadURI(uri, 0, aLoadFlags)) & 0x80000000))', file nsDocShell.cpp, line 2163 ###!!! Break: at file nsDocShell.cpp, line 2163 JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.loadURI]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://help/content/help.js :: loadURI :: line 177" data: no] frame: Box (0x8ad2574) style: 0x8ad2540 {} Wrong parent style context: style: 0x89223fc {} should be using: style: 0x8844380 {}
Assignee | ||
Comment 2•23 years ago
|
||
Ah, darnit. I didn't get these dummy files into the mozilla side. There in source, but didn't update the jar.mn Accepting. Patch to follow.
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•23 years ago
|
||
Assignee | ||
Comment 4•23 years ago
|
||
Note that the dummy files I am adding with the previous patch don't have real content, they just throw up a thing that says: context-sensitive help: write me! and give the name of the file (e.g. mozilla/extensions/help/resources/locale/en-US)
Assignee | ||
Comment 5•23 years ago
|
||
Checked in dummies. Marking FIXED.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•