290246 - Get rid of binding assertions?

Status: RESOLVED WORKSFORME

(Core Graveyard :: XForms, defect)

Description

[aaronr]

If we put xforms elements with binding attributes in xbl bindings, we'll start
seeing assertions in the ::ProcessNodeBind code path.  This is because when the
.xbl file is parsed and xforms:output encountered, for example, XTF will go
ahead and start creating the xform element in the .xbl document which screws up
the assumptions made in FindParentContext().

So we probably need to decide if there is still value to having those errors
reported to standard out or not.

Comment 1

[aaronr]

Attachment: xbl file for testcase

Comment 2

[aaronr]

Attachment: main xform testcase document

Comment 3

[aaronr]

download both testcase files to the same directory.  Change the .xhtml file to
have the correct name for the .xbl file.  Load the .xhtml file.  You should see
3 items output via the repeat and a lot of warnings being output to stdout.

Comment 4

[Allan Beaufour]

(In reply to comment #0)
> So we probably need to decide if there is still value to having those errors
> reported to standard out or not.

IMHO, it's not a question about errors on the console. I/we have assumed that
the elements exist in a document, they may not. The same problem may occur when
our elements are cloned I guess.

So, yes, we need to differ between valid errors, and errors because the elements
are not properly inserted in a document.

Comment 5

[Allan Beaufour]

We do no longer generate these exceptions.