Switch

​

Known issues

​

Gaps in the current rules

• The Figma library confirms only three states, not the four seen on its siblings. Selected=True/False × State=Enabled/Disabled/Focused — versus the Default/Hover/Disabled/Focused seen on Checkbox and Radio. No Hover state is demonstrated anywhere in the library for this component, and the resting state is named Enabled rather than Default — a naming difference from its siblings, not just a missing state.
• No hover state is demonstrated for this component in the design library, unlike its siblings. Whether that’s intentional (a track/thumb may not need a hover cue the way a clickable icon does) or simply unmodeled is unconfirmed.
• No labeled composite (“Toggle + Label”) was found in the design library, unlike Checkbox and Radio, both of which have one. Many systems put a Switch’s label before the control, opposite Checkbox and Radio’s trailing convention, but this page does not have evidence either way for Titan specifically.
• FormInput has no type for Switch, confirmed directly from its source — its six types are text, radio, segmentedButton, select, checkbox, and custom. Every other field in this category composes a complete labeled field through FormInput; Switch has no equivalent, decided path to do the same.

​

Constraints Titan should enforce