Closed
Bug 355016
Opened 18 years ago
Closed 8 years ago
group inside repeat creates some connection between input boxes (makes troubles also by deleting)
Categories
(Core Graveyard :: XForms, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: pokusak, Unassigned)
References
Details
Attachments
(1 file)
1.61 KB,
application/xhtml+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060930 Minefield/3.0a1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060930 Minefield/3.0a1 Repeating xforms:group with attribute ref (exactly ref=".") creates connection between repeated input boxes. Deleting don't work right as well. Reproducible: Always Steps to Reproduce: 1.Hit "addLast" trigger 2.Change value in second input box 3.Click into first input box Actual Results: Value in last input box is changed to value entered in second input box. Expected Results: Add one input box (with groups and labels) and not to change value in last input box
Updated•18 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
on trunk the testcase doesn't seem to have the 'actual results' as indicated above, but the controls and their bound values don't behave correctly w.r.t. the instance data. For example, if I load the testcase, focus the first input and click on 'lastAdd' trigger, I should have 3 inputs, the first with the value of '1' and two with the value of '2'. If I then focus the first input element and select the 'lastDelete' trigger, I should have two inputs, both with the value of 2. Neither currently happen.
Now I'm completely confused. Are you saying the test case is wrong or it is really bug? I'm trying this test case under Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070324 Minefield/3.0a3pre with Mozilla XForms 0.7 and Mozilla/5.0 (Windows; U; Windows NT 5.1; sk; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 with Mozilla XForms 0.7.0.1 For me ist still has the 'actual results'. (under last Minefield and Firefox too) And even more. It seems to work fine in scenario you described.
I guess those were my observations at the time. Nothing wrong with your testcase. When I try it using yesterday's trunk, I now see the 'actual results' that you described. I tried this with the patch I did for bug 357569 and the problem seems to be gone which makes sense given what that patch fixes. Please verify that this is indeed fixed after this patch goes in. Thanks.
Depends on: 357569
Comment 5•8 years ago
|
||
RIP xforms
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
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
•