Closed
Bug 275213
Opened 20 years ago
Closed 19 years ago
Handle XForms initialization phase according to the specification
Categories
(Core Graveyard :: XForms, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 283737
People
(Reporter: aaronr, Assigned: aaronr)
References
()
Details
Attachments
(2 files, 1 obsolete file)
I will post a testcase for this. If you are using a group with a model and ref attribute and that model uses external instance data, then contained controls that key off of that ref attribute do not bind to the instance data. However, using the same testcase but moving the instance data into the xforms document, then there are no problems. This testcase has no problems in the Novell plugin beta.
testcase for bug. Used diff because this contains two seperate files, the xform and the external instance data.
|
||
Comment 2•20 years ago
|
||
In this case, I would expect an xforms-refresh event to occur once the external instance data is loaded. Perhaps that is not causing things to refresh properly.
|
|
||
Comment 3•20 years ago
|
||
|
|
||
Comment 4•20 years ago
|
||
|
|
||
Updated•20 years ago
|
Attachment #169069 -
Attachment is obsolete: true
|
||
Comment 5•20 years ago
|
||
Changing summary.
Summary: context doesn't work if secondary model uses extenal instance → Handle XForms initialization phase according to the specification
Works now. Probably fixed by 283737 *** This bug has been marked as a duplicate of 283737 ***
Status: NEW → 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
•