Closed
Bug 333044
Opened 19 years ago
Closed 19 years ago
select1 with itemset filtered by instance doesn't filter correctly
Categories
(Core Graveyard :: XForms, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 327985
People
(Reporter: bkc, Assigned: aaronr)
References
()
Details
Attachments
(1 file)
7.42 KB,
application/xhtml+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
See details of attached standalone .xhtml file that demonstrates this bug and sizing bug (to be filed shortly as a different select1 bug)
I have two select1 elements. The 2nd of the two has a itemset with an xpath condition used to filter it's items. The filtering is based on the currently selected value of the 1st select1 element. Depending on whether the bound instance has initial data during form load, and depending on the order in which the selects are toggled, sometimes the 2nd select shows the wrong choices.
Reproducible: Always
Steps to Reproduce:
1. load demonstration .xhtml file from url or attachment
2 [review]. follow instructions on page
Actual Results:
2nd select1 doesn't always filter it's choices when first select1 is changed.
Expected Results:
2nd select1 should always only show choices limited by the 1st select1 element. Also, the 1st select1 has an xforms-value-changed action that resets the 2nd select1 to the non-selected value to ensure that instance data isn't contradicting the valid itemset list.
I am running 0.4 of the mozilla xforms extension.
Reporter | ||
Comment 1•19 years ago
|
||
Comment 2•19 years ago
|
||
This works on trunk, and was fixed by bug 327985.
*** This bug has been marked as a duplicate of 327985 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•