W3C action sequences not interleaved by tick - key actions execute before pointer actions

[kfertitta]

Description

W3C action sequences are processed sequentially by input source type (all key actions, then all pointer actions) instead of being interleaved by tick as required by the W3C WebDriver specification.

Expected behavior

Actions at the same tick index across different input sources should execute together. For example:

Tick 0: KeyDown(Ctrl)
Tick 1: Click(element)
Tick 2: KeyUp(Ctrl)

Should produce: Ctrl pressed → Click while Ctrl held → Ctrl released (i.e., a Ctrl+Click).

Actual behavior

All key actions are dispatched first (Ctrl down, Ctrl up), then all pointer actions (Click). The click executes after Ctrl is already released, resulting in a plain click instead of a Ctrl+Click.

Impact

This breaks any action sequence that relies on modifier keys being held during pointer actions, including:

• Ctrl+Click for multi-selection in tree views and list controls
• Shift+Click for range selection
• Any combined keyboard+mouse interaction in a single action chain

Workaround

Split the action chain into separate performActions calls:

// Instead of one chain:
actions.keyDown(Key.Control).click(element).keyUp(Key.Control).perform();

// Use three separate calls:
actions.keyDown(Key.Control).perform();
element.click();
actions.keyUp(Key.Control).perform();

Environment

• appium-novawindows-driver: 1.3.1
• Appium: 3.2.2