[slots-imperative-slot-api.tentative.html]
  [Imperative slot API can assign nodes in manual slot assignment.]
    expected: FAIL

  [Assignment with the same node in parameters should be ignored, last one wins.]
    expected: FAIL

  [attachShadow can take slotAssignment parameter.]
    expected: FAIL

  [Assigning invalid nodes causes exception and slot returns to its previous state.]
    expected: FAIL

  [Imperative slot API throws exception when not slotAssignment != 'manual'.]
    expected: FAIL

  [Order and assignment of nodes are preserved during multiple assignment in a row.]
    expected: FAIL

  [Previously assigned node should not be assigned if slot moved to a new shadow root. The slot remains empty when moved back, trigger recalc.]
    expected: FAIL

  [Previously assigned node should not be assigned if slot moved to a new shadow root. The slot remains empty when moved back, no trigger recalc.]
    expected: FAIL

  [A slot should be cleared of assigned nodes even if it's re-inserted into the same shadow root.]
    expected: FAIL

  [Imperative slot API throws exception when slottable parentNode != slot's host.]
    expected: FAIL

  [Moving a slot to a new host, the slot loses its previously assigned slottables.]
    expected: FAIL

  [Order of slottables is preserved in manual slot assignment.]
    expected: FAIL

  [Moving a slot's tree order position within a shadow host has no impact on its assigned slottables.]
    expected: FAIL

  [Appending slottable to different host, it loses slot assignment. It can be re-assigned within a new host.]
    expected: FAIL

  [Removing a slot from DOM resets its slottable's slot assignment.]
    expected: FAIL

  [Previously assigned slottable is moved to new slot when it's reassigned.]
    expected: FAIL