Closed Bug 236690 Opened 21 years ago Closed 21 years ago

Help\For Internet Explorer Users displays a blank page

Categories

(SeaMonkey :: Help Documentation, defect)

x86
Windows Server 2003
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: vedran, Assigned: neil)

References

Details

(Keywords: regression)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7b) Gecko/20040306 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7b) Gecko/20040306 Help\For Internet Explorer Users, when clicked, displays a blank page. Reproducible: Always Steps to Reproduce: Just click the menu item. Actual Results: Help opens, and blank page is displayed. Expected Results: Help for IE users should be displayed.
QA Contact: stolenclover → rivanvx
Keywords: regression
Could be seen also in firefox 0.8.0+ / WinXP-Sp1 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040306 Firefox/0.8.0+ (MozJF)) built from today's source. But it seems to happen only on first try ?!
WORKSFORME on 20040306 that I compiled about 15 minutes ago. Build could contain regressions from a risky patch, but nothing that should effect Help Viewer. Reporter: Can we get more detailed steps on how to reproduce this or maybe some extra information to help repro the bug? BTW, why was QA changed? The reporter of a bug shouldn't be QA Contact.
Confirmed in (official) build 2004030605 on Mac OS X 10.2.8
I still can't reproduce this, but others (stephend) can. Does anyone know when this regression started?
Error: uri has no properties Source File: chrome://help/content/help.js Line: 264
261 262 function loadURI(uri) 263 { 264 if (uri.substr(0,7) != "chrome:") 265 uri = helpBaseURI + uri; 266 const nsIWebNavigation = Components.interfaces.nsIWebNavigation; 267 getWebNavigation().loadURI(uri, nsIWebNavigation.LOAD_FLAGS_NONE, null, null, null); 268 } I haven't yet figured out why the variable 'uri' is coming up null yet. Is this fallout from something Benjamin has changed in chrome?
stephend: It looks like it is trying to find the topic from the RDF file (which has the ID of "forieusers"), and it is returning null, therefore passing null to the function. display topic is here -> http://lxr.mozilla.org/seamonkey/source/extensions/help/resources/content/help.js#115 Which is getting the parameter from here -> http://lxr.mozilla.org/seamonkey/source/extensions/help/resources/content/contextHelp.js#52 which is received from the menuitem. The only explanation is a RDF toc problem, but the ieusers item is right here -> http://lxr.mozilla.org/seamonkey/source/extensions/help/resources/locale/en-US/help-toc.rdf#11, which is where it should read it from. I'll do some more testing/debugging over the weekend to see if I can find the problem. If anyone finds any leads, please post a comment to this bug. Maybe I helped someone find a lead.
Sorry if it is some "spam", but it is a JS console error I get on first time when trying to open "Help\For Internet Explorer Users" menu option : Error: window.XULBrowserWindow has no properties Hope it helps.
Reporter, is this problem in Firefox and Seamonkey? That would make things much more stranger if it is. Frederic: Thanks for posting that. I haven't had time to do any debugging on this bug. That is an interesting error. It looks like everyone is having different problems on difference machines. Are you running firefox or seamonkey?
Here is my user agent, you'll have your answer ;o) Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040312 Firefox/0.8.0+ 6 hours CVS based build for your info :o)
I noticed this in SeaMonkey at first, I'm haven't tried Firefox at all.
I now see this on Seamonkey (2004031309), but not on Firefox (20040310). There doesn't seem to be any leads.
This is getting weirder as time goes by :). I can sometimes reproduce this bug every odd time I open For IE Users (1st try, 3rd try, etc.) but not on even times (2nd try, 4th try). I also see this when opening help through Help -> Help Contents.
>This is getting weirder as time goes by :). I can sometimes reproduce this bug >every odd time I open For IE Users (1st try, 3rd try, etc.) but not on even >times (2nd try, 4th try). Exactly what I'm seeing. This bug is very weird, and always this error in JS Console. Is Firefox cursed ? ;o)
*** Bug 237522 has been marked as a duplicate of this bug. ***
Maybe someone's busted RDF.GetDataSourceBlocking? getLink is called synchronously as the help window opens; I put in a dump in getLink to query the DS, the resource and the target, and for a resource of chrome://help/locale/help-toc.rdf#welcome the target was null. I put in the same dump in onselect_loadURI (which obviously needs to wait for me to click on the tree) and it returned a target (I didn't bother to query the value). Note that onselect_loadURI actually cheats and doesn't use raw RDF to get the target, someone should file a bug on that ;-)
Attached patch Proposed patchSplinter Review
Assignee: rlk → neil.parkwaycc.co.uk
Status: NEW → ASSIGNED
Comment on attachment 144162 [details] [diff] [review] Proposed patch r=me. bsmedberg changed the tree to load the datasources asynch on modification of the attribute. So in order to load synch, one has to kick off the load before modifying the attribute.
Attachment #144162 - Flags: review+
Comment on attachment 144162 [details] [diff] [review] Proposed patch Trying sr from bug 235866 first as this is a regression from that bug.
Attachment #144162 - Flags: superreview?(bryner)
Severity: normal → critical
Attachment #144162 - Flags: superreview?(bryner) → superreview+
Comment on attachment 144162 [details] [diff] [review] Proposed patch Needed to fix highly visible help regression - help loads contents but no start page.
Attachment #144162 - Flags: approval1.7?
Comment on attachment 144162 [details] [diff] [review] Proposed patch a=asa (on behalf of drivers) for checkin to 1.7
Attachment #144162 - Flags: approval1.7? → approval1.7+
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
This isn't fixed for Firefox yet. If I understand this right, it's covered by http://mozdev.org/bugs/show_bug.cgi?id=6030 and will be included in the Firefox Help 1.1 landing before 0.9 ships, see bug 238221 and http://mozdev.org/bugs/show_bug.cgi?id=5983.
*** Bug 239648 has been marked as a duplicate of this bug. ***
*** Bug 239879 has been marked as a duplicate of this bug. ***
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: