{|
| {{flag|Germany}} || {{N/A}}
| {{flag|Germany}} || {{1x|1=data-style="border:1px solid red"{{!}}x{{!}}{{!}}}} {{N/A}}
| {{flag|Germany}} || {{1x|1=data-style="border:1px solid red"}} {{N/A}} <!-- SCENARIO 1: THIS IS NOT HANDLED -->
|}

This is a gap in the TableFixups handler which attempts to "collect" strings from unparsed template strings, reparse them via the tokenizer and update the attributes.

For scenario 1, the failure is because the 2 separate transclusions {{1x|..}} and {{N/A}} produce different attributes of the same HTML element (table cell). We need to update the data-mw representation for this case. The existing parts representation might suffice. But, right now, because of this representation gap, the handler aborts with [error/dom/tdfixup] Unhandled TD-fixup scenario. Encountered multiple transclusion children of a <td> error message.

Bonus points:
The original bug report used the following test case for Scenario 1.

{|
| {{flag|Germany}} || {{nts|0}} {{N/A}}
|}

This test case introduces an addition quirk where the {{nts|0}} generates a string that is an invalid table attirbute string (it generates a <span ..>...</span>) that should be simply ignored.