Closed Bug 280264 Opened 20 years ago Closed 20 years ago

XForms submission doesn't remove non-relevant instance-data.

Categories

(Core Graveyard :: XForms, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: doronr, Assigned: doronr)

Details

Attachments

(1 file, 3 obsolete files)

Also, bug 279449 adds another loop walking the data, which should be combined with the submission serialization code probably at one point.
-> moi
Assignee: aaronr → doronr
Attached patch first try (obsolete) — Splinter Review
Attachment #174313 - Flags: review?(aaronr)
Status: NEW → ASSIGNED
Comment on attachment 174313 [details] [diff] [review] first try +nsXFormsModelElement::IsInstanceDataValid(nsIDOMNode *aInstanceDataNode, PRBool *aResult) You should sign a value into aResult before you do NS_ENSURE_STATE nsXFormsModelElement::IsInstanceDataRelevant(nsIDOMNode *aInstanceDataNode, PRBool *aResult) same here nsXFormsModelElement::IsInstanceDataRequired(nsIDOMNode *aInstanceDataNode, PRBool *aResult) same here I'd also suggest, like we talked about, one function that can handle getting the nodestate just the once and all 3 tests and return the proper value. To get rid of all of the extaneous function calling.
Attachment #174313 - Flags: review?(aaronr) → review-
Attached patch 2nd try (obsolete) — Splinter Review
Attachment #174313 - Attachment is obsolete: true
Attachment #174393 - Flags: review?(aaronr)
Attachment #174393 - Attachment is obsolete: true
Attachment #174393 - Flags: review?(aaronr)
Attached patch 3rd try (obsolete) — Splinter Review
Attachment #174410 - Flags: review?(aaronr)
Attachment #174410 - Attachment is obsolete: true
Attachment #174410 - Flags: review?(aaronr)
Attachment #174414 - Flags: review?(aaronr)
Comment on attachment 174414 [details] [diff] [review] hopefully aaron has no more comments. for posterity sake, my comments were: In nsXFormsModelElement::HandleInstanceDataNode - make return values a const and give them similar names that make sense. - assign default return value. - Change test syntax so that you don't re-assign same return value that is already contained in the return parameter. - probably don't need the NS_ENSURE_ARG_POINTER tests because this function should only ever be called from one place where the passed in parameter pointer can be assured. Looks fine now
Attachment #174414 - Flags: review?(aaronr) → review+
Comment on attachment 174414 [details] [diff] [review] hopefully aaron has no more comments. Didn't test yet, but looks good. r=me
checked in.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: