138921 - uri has no properties

Status: VERIFIED FIXED

(SeaMonkey :: Help Documentation, defect)

Description

[Brant Gurganus]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.9+)
Gecko/20020419
BuildID:    2002041903

The javascript link that opens Mozilla Help for Labels does not work.

Reproducible: Always
Steps to Reproduce:
1. Open preferences.
2. Navigate to Mail & Newsgroups > Labels.
3. Click Help.

Actual Results:  Mozilla Help opens, but page does not open.

Expected Results:  Page opens.

In the JavaScript console, the following appears when the button is pressed:
Error: uri has no properties
Source File: chrome://help/content/help.js
Line: 275

Comment 1

[Ian Oeschger (gone)]

All of these are examples of help buttons for which no help has yet been
created. Most of these are mozilla-only UI, too, like the DOM Inspector pref
panel and so on. ACCEPTING. We can at least put pointers to some basic help
content for these in the UI (e.g, in pref-help.js, where the context keys for
the pref panel are listed), even if there is as yet no specific contextual help.

Comment 2

[Brant Gurganus]

I am nominating this for 1.0 since it will give users a bad message if they
click help and don't receive any.

Comment 3

[Ian Oeschger (gone)]

Patch for these bugs is over in 129540:
http://bugzilla.mozilla.org/attachment.cgi?id=83604&action=view
Where there is not help content for the panels listed here, I open the Welcome page.

Comment 4

[Ian Oeschger (gone)]

These are FIXED with 145331, which sets the default topic properly when the
context ID is not available.

Comment 5

[Arnoud Berendsen]

Using 1.1beta:
A Javascript error still occurs here, though a different one than it used to be.

The error is now:
Error: uncaught exception: [Exception... "Not enough arguments
[nsIWebProgress.addProgressListener]"  nsresult: "0x80570001
(NS_ERROR_XPC_NOT_ENOUGH_ARGS)"  location: "JS frame ::
chrome://help/content/help.js :: init :: line 121"  data: no]

Comment 6

[Arnoud Berendsen]

Actually this behaviour happens in the other bugs like this one too (bugs 138920
thru 138929).
It seems silly to reopen all of them tho.

Comment 7

[Brant Gurganus]

This is fixed in 2002072514.

Comment 8

[Terri Preston]

Verified fixed branch build 2002072908