If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Allow overriding of menu "value" in overlay menu items

VERIFIED WONTFIX

Status

()

Core
XUL
P3
normal
VERIFIED WONTFIX
18 years ago
15 years ago

People

(Reporter: Charles Manske, Assigned: Chris Waterson)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
When we use a menu item in an overlay, the menu text ("value" attribute)
is set in the overlay XUL either directly or in an associated observer.
We need to be able to allow different text by setting the value in the "user"
of the overlay item by setting a different "value" string.
E.g.: in the overlay:
<broadcaster id="cmd_1" value="item1" oncommand="foo()">
<menuitem id="menu_1" observes="cmd_1">
User of the overlay:
<menuitem id="menu_1" value="My name">

The text on the menu should be "My name", not "item1", but the command would
still be "foo()"
Note that this currently works when you set an alternate name for a titledbutton
in a toolbar, though hyatt thinks this is actually a bug!

Updated

18 years ago
Assignee: hyatt → waterson

Comment 1

18 years ago
reassigning to waterson per hyatt.
(Reporter)

Comment 2

18 years ago
I discussed this with Chris and if there's no clear way to know which "setter"
of a value attribute should be used, we can live with repeating the value and
oncommand attributes in cases where we need to have different "value" text,
so we don't reference the overlay item for that case.
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: M15
(Assignee)

Comment 3

18 years ago
lemme know if this is a problem
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 4

18 years ago
No problem. I've figure out ways to do what I need.
mass-verifying WontFix bugs which haven't changed since 2001-12-31.

use the search string "BoletusEdulis" if you want to filter out this msg.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.