pointer-events
An interaction-state shim. No longer maintained.
What it did
The script watched pointer events across the page and reflected interaction state onto elements as .hover and .active classes. It existed because touch devices handle the native CSS :hover and :active states inconsistently — a tap could leave an element stuck in a hover state, or skip the active state entirely.
By driving the state through classes instead, a stylesheet could target .hover and .active directly and get predictable behavior on both pointer and touch input.
Why it's deprecated
The design system now handles interaction states internally. Components carry their own hover and active styling, built to behave correctly on touch and pointer devices without a separate script.
Because the behavior is part of the framework, there is nothing to include and nothing to wire up — using the components is enough.
What to use instead
Use the framework components directly. Their interaction states are already correct. For a custom interactive element, style the standard :hover and :active pseudo-classes — modern browsers, including mobile ones, handle them reliably.