W3C XForms 1.1 Test Suite — Coverage Status
Source: tests/xforms/w3c/STATUS.md

W3C XForms 1.1 Test Suite — Coverage Status

Source: https://www.w3.org/MarkUp/Forms/Test/XForms1.1/Edition1/

Engine Gaps

The following categories of W3C test failures reflect known limitations in the Saxon-Forms engine. These are tracked here to guide future development.

Recently resolved

The following gaps were resolved and are listed here for reference:

Insert/delete action semantics (13 tests)

Root causes vary across the cluster:

Toggle action scoping in repeats (1 test)

xf:toggle inside a repeat iteration toggles ALL iterations’ switches instead of just the current one. The toggle action’s $source-control scoping mechanism (lines 6018–6024 in saxon-xforms.xsl) exists but $source-control is not being passed through the event dispatch chain (applyActionsaction-toggle) from the clicked button’s DOM element.

Affected: 9.3.1.f.

Toggle case-child precedence (1 test)

The <xforms:case> child element of <xforms:toggle> (which specifies the target case with optional @value attribute) is not parsed by the toggle action. The action map builder (line 932–933) stores case text content but does not handle @value attribute precedence. The <xforms:case> child may also be incorrectly matched by the case rendering template (line 1545).

Affected: 10.6.1.b.

Model-event message dispatch (10 tests)

xforms:message elements that listen for model-level events (xforms-rebuild, xforms-reset, xforms-recalculate, xforms-revalidate, xforms-help, xforms-hint) do not produce modal dialogs when the event fires. The event itself may dispatch correctly, but the xforms:message handler does not invoke alert() / modal output.

Affected tests: 10.13.a (reset), 10.8.1.a/b (rebuild), 8.1.8.a (DOMActivate message), 8.2.2.a–c (help), 8.2.3.a–c (hint).

Submission features (4 tests)

Processing model behavioral failures (3 tests)

Container control edge cases (1 test)

Miscellaneous (4 tests)