Context & The Bug: I am experiencing a persistent engine bug with Interactive Components. Under random, untraceable conditions during regular design work, the Mouse down trigger permanently corrupts on a specific Master Component.
Instead of holding the [Pressed state] while the mouse button is physically held down, the component flashes the [Pressed state] and immediately reverts back to the [Default state]. It effectively degrades into an On click behavior, ignoring the continuous Mouse down input.
Important - What I have already ruled out: Please do not advise checking layer names or parent interactions, as I have already completely isolated the issue:
-
NO Parent Interceptions: The bug persists even when the instance is placed on a completely empty canvas with no parent frames or conflicting interactions.
-
NO Layer Mismatches: The layer hierarchy and naming are identical.
-
NO Hidden Triggers: There are no rogue
Mouse leaveorAfter delayinteractions forcing a reset.
Proof of engine bug: To prove this is a system-side corruption, I built an absolutely identical Master Component from scratch right next to the broken one. The new component has the exact same layers and the exact same interaction settings (Mouse down, Dissolve, 300ms). The new one works flawlessly, while the old one remains permanently broken.
This clearly indicates that the component's internal state machine or cache is getting corrupted by Figma's engine over time. Can you escalate this to the engineering team to investigate what causes this state degradation?