Closed Bug 533358 Opened 15 years ago Closed 12 years ago

ASSERTION FAILED: caught exception getting value for ``cmd.change-value.help''

Categories

(Other Applications Graveyard :: Venkman JS Debugger, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sgautherie, Assigned: Gijs)

References

()

Details

(Keywords: assertion, regression)

Attachments

(1 file)

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.7pre) Gecko/20091207 SeaMonkey/2.0.2pre] (comm-1.9.1-win32-unittest/1260219994) (W2Ksp4)
{
vnk: init {** ASSERTION FAILED: caught exception getting value for ``cmd.change-value.help''
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://venkman/content/venkman-msg.js :: getMsgFrom :: line 115"  data: no]
}
when I enable Venkman in bug 504730.

Bug 396142 removed the "cmd.change-value.help" property...

"You are not authorized to access bug #396142." :-(
Keywords: regression
The help was removed because the command could no longer be usefully used in the interactive session (arguments changed such that objects were needed), I believe, but this doesn't appear to have been correct - I was unfamiliar with this requirement of Vnk when reviewing it :(. Looking at other Venkman commands, it should have help added back (for code users, presumably).
(In reply to comment #0)
> Bug 396142 removed the "cmd.change-value.help" property...
> "You are not authorized to access bug #396142." :-(

That was http://hg.mozilla.org/venkman/rev/406aa2c44ff8.

(In reply to comment #1)
> Looking at other Venkman
> commands, it should have help added back (for code users, presumably).

{
     1.2 +++ b/locales/en-US/chrome/venkman.properties

    1.23 -cmd.change-value.params  = <parent-value> <property-name> [<new-value>]
    1.24 -cmd.change-value.help    = Changes the value of the property named <property-name> of the jsdValue <parent-value>.  If the jsdValue <new-value> is specified, this will become the new value of the property, otherwise a dialog box is displayed, allowing the user to enter a new expression for the value.
    1.25 +cmd.change-value.params  = <jsd-value> <property-name> <expression> [<new-value>]
}

What should the new help text be?
Keywords: helpwanted
Whiteboard: [ToDo: answer comment 2 question]
Attached patch PatchSplinter Review
Attachment #513048 - Flags: review?(mnyromyr)
Status: NEW → ASSIGNED
Keywords: helpwanted
OS: Windows 2000 → All
Hardware: x86 → All
Whiteboard: [ToDo: answer comment 2 question]
Comment on attachment 513048 [details] [diff] [review]
Patch

> cmd.change-value.label
>+cmd.change-value.help
> cmd.change-value.params

Nit: .help seems to usually be after .label and .params.
Comment on attachment 513048 [details] [diff] [review]
Patch

r=me with .help moved after the .params.
Attachment #513048 - Flags: review?(mnyromyr) → review+
Note, SeaMonkey2.1 is in string freeze, so would be best if we can hold off this landing. Because of that I don't find this l10n-impact strong enough to break string-freeze, so not wanted.
http://hg.mozilla.org/venkman/rev/bc430c9235af
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Just FYI, as no venkman release has been made since, we are still not shipping this change in SeaMonkey.
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: