accessing menu item attributes generated via template returns RDF variable name instead of value

RESOLVED EXPIRED

Status

()

Core
RDF
RESOLVED EXPIRED
16 years ago
12 years ago

People

(Reporter: Bugzilla Reviewers, Assigned: Chris Waterson)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
If I use a XUL template to generate the content of a menu, and then access its
menu items via DOM properties/methods like childNodes and
getElementsByAttribute, attributes populated with RDF variables contain the RDF
variable name rather than the value of the variable for that menu item.

For example:

var menu = document.getElementByID('my-menu');
var popup = menu.childNodes[1]; # the menupopup; childNodes[0] is the template
var item = popup.childNodes[0]; # a menu item
item.value;

Expected Results: the value of the item (f.e. "foo bar baz")
Actual Results: the RDF variable representing the values (f.e. "?blah")

Accessing the values works, however, for menu.selectedItem and when accessing
the menu item via document.getElementById:

menu.selectedItem.value; # the value of the item
document.getElementById('menu-item-id').value; # the value of the item

Tested on today's (2002-07-15) Linux nightly.
(Reporter)

Comment 1

16 years ago
Correction, this is the code that fails:

var menu = document.getElementById('my-menu');
var popup = menu.getElementsByTagName('menupopup');
popup = popup[0];
var item = popup.childNodes[0];
alert(item.value);

Comment 2

15 years ago
tever is not RDF QA anymore
QA Contact: tever → nobody
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.