329104 - Select1 problems when itemset changes

Status: RESOLVED WORKSFORME

(Core Graveyard :: XForms, defect)

Description

[Allan Beaufour]

I have two select1s on a page and the first select determines the contents of the second select. There is a bug so that selecting something in both selects, and then changing the first does not clear the second.

Comment 1

[Allan Beaufour]

Attachment: Testcase

Comment 2

[Allan Beaufour]

(In reply to comment #1)
> Created an attachment (id=213752) [edit]
> Testcase

As a bonus: It's not even possible to select new values with the arrow keys when a "wrong value" is shown

Comment 3

[aaronr]

well, I don't think that the original 'bug' is really a bug.  That is just XForms.  The value that is shown in the input field part is the bound node value of the second select1 which doesn't change just because the first select1 changed value.  It will go 'out of range', though.

However, the bonus that you mentioned, is a bug that we can fix here.

Comment 4

[Allan Beaufour]

(In reply to comment #3)
> well, I don't think that the original 'bug' is really a bug.  That is just
> XForms.  The value that is shown in the input field part is the bound node
> value of the second select1 which doesn't change just because the first select1
> changed value.  It will go 'out of range', though.

Heh. You are right. I was a bit too quick there.
 
> However, the bonus that you mentioned, is a bug that we can fix here.

:)

Comment 5

[Allan Beaufour]

Attachment: Testcase v2

(In reply to comment #3)
> well, I don't think that the original 'bug' is really a bug.  That is just
> XForms.  The value that is shown in the input field part is the bound node
> value of the second select1 which doesn't change just because the first select1
> changed value.  It will go 'out of range', though.

So now the stupid user (me) :), adds a setvalue to the first select.

That makes the second select clear, but try:
1. Select "Value 1" in the first select
2. Select "Value 11" in the second select
3. Select "Value 2" in the first select
4. Select "Value 21" in the second select

"Where's the spoon?"
"Aaahrhhaa!" :)

Comment 6

[aaronr]

(In reply to comment #5)
> Created an attachment (id=214890) [edit]
> Testcase v2
> 
> (In reply to comment #3)
> > well, I don't think that the original 'bug' is really a bug.  That is just
> > XForms.  The value that is shown in the input field part is the bound node
> > value of the second select1 which doesn't change just because the first select1
> > changed value.  It will go 'out of range', though.
> 
> So now the stupid user (me) :), adds a setvalue to the first select.
> 
> That makes the second select clear, but try:
> 1. Select "Value 1" in the first select
> 2. Select "Value 11" in the second select
> 3. Select "Value 2" in the first select
> 4. Select "Value 21" in the second select
> 
> "Where's the spoon?"
> "Aaahrhhaa!" :)
> 


You should probably listen for the xforms-select instead of xforms-value-changed on your xf:setvalue.  That works for me, too.

Comment 7

[Allan Beaufour]

(In reply to comment #6)
> (In reply to comment #5)
> > Created an attachment (id=214890) [edit]
> > Testcase v2
> > 
> > (In reply to comment #3)
> > > well, I don't think that the original 'bug' is really a bug.  That is just
> > > XForms.  The value that is shown in the input field part is the bound node
> > > value of the second select1 which doesn't change just because the first select1
> > > changed value.  It will go 'out of range', though.
> > 
> > So now the stupid user (me) :), adds a setvalue to the first select.
> > 
> > That makes the second select clear, but try:
> > 1. Select "Value 1" in the first select
> > 2. Select "Value 11" in the second select
> > 3. Select "Value 2" in the first select
> > 4. Select "Value 21" in the second select
> > 
> > "Where's the spoon?"
> > "Aaahrhhaa!" :)
> > 
> 
> 
> You should probably listen for the xforms-select instead of
> xforms-value-changed on your xf:setvalue.  That works for me, too.

"too"? The above does not work for me. I'm not looking for a work-around :) I have plenty of those already. Please point out to me if I am doing something wrong in the testcase, or else there must be a bug.

Comment 8

[aaronr]

Of course I finally get time to sit down with this and it is already working on the trunk.  Maybe I should do this with all my bugs :-)  Trying this with the nightlies shows that it was still broken in the 2006-03-19 nightly and fixed in the 2006-03-20 nightly.  If I had to guess, I'd say that it was bug 327985 that did the trick.