Improve xul_selectcontrol.js test

NEW
Unassigned

Status

()

Toolkit
XUL Widgets
3 years ago
3 years ago

People

(Reporter: Ms2ger, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox40 affected)

Details

(Reporter)

Description

3 years ago
::: toolkit/content/tests/chrome/xul_selectcontrol.js
@@ +132,5 @@
>    test_nsIDOMXULSelectControlElement_States(element, testid + "removeItemAt", 1,
>          selectionRequired ? seconditem : null, selectionRequired ? 0 : -1,
>          selectionRequired ? secondvalue : "");
>  
> +  is(removeditem.control, undefined, testid + "control not set");

From all the examination of instances of "control" (with quotes) in toolkit/content/widgets, I can't find a reason for this to ever be the case (let alone *always* be the case).  Please file a followup and investigate the circumstances under which this happens.

(Note that because removeditem is firstitem from line 131, and firstitem had a control a ways up in this file, this does *not* appear to just be a totally non-existent property detection.  What exactly is wrong here, I wouldn't know without some debugging beyond visual inspection.)
You need to log in before you can comment on or make changes to this bug.