SetPropagateKeyboardInput is treated as protected function on first call in combat

[seblindfors]

Minimal reproducible example: 1) Enter combat 2) /run UIParent:SetPropagateKeyboardInput(true)

ADDON_ACTION_BLOCKED is only triggered on the first call. After that, setting propagation works normally. This seems to only affect the Classic forks. It does not matter whether the frame is protected or not.

Affects:

• 1.14.4.50252
• 3.4.2.50172

Does NOT affect:

• 10.1.0.50000
• 1.14.3.49821

[seblindfors]

This seems to be an intended change to prevent selective propagation in combat. My guess is to counteract automation that could work by key spam and using an insecure frame with selective propagation to eat key bindings.