Change Details

=== Background/Goal All available cursors need to be documented as part of the system's user-interface foundations. === User stories As a designer, I need to have access to the system's cursors, so I can reuse them creating system compliant designs. === Implementation note While it seems obvious to rely on browser default cursor values, there are a few decisions that include custom `cursor` values, like for example on specific custom DOM disabled elements (with `disabled` property a rare exception) or `pointer` carrying buttons and other inputs. Those are an opinionated choice and should for example be theme-able. Compare https://developer.mozilla.org/en-US/docs/Web/CSS/cursor ===Acceptance criteria to resolve [] The system's cursors are defined and documented

=== Background/Goal All available cursors need to be documented as part of the system's user-interface foundations. === User stories As a designer, I need to have access to the system's cursors, so I can reuse them creating system compliant designs. === Implementation note **Why tokenize cursors?** While it seems obvious to rely on browser default cursor values, there are a few decisions that include custom `cursor` values, like for example on specific custom DOM disabled elements (with `disabled` property a rare exception) or `pointer` carrying buttons and other inputs. Those are an opinionated choice and should for example be theme-able. Compare https://developer.mozilla.org/en-US/docs/Web/CSS/cursor **Which cursor theme values are necessary?** - default - grab - grabbing - help - move - not-allowed - pointer (also known as “hand”) - text All of above are currently in use by #OOUI widgets and will be needed in #Codex components over time too. ===Acceptance criteria to resolve [] The system's cursors are defined and documented

=== Background/Goal All available cursors need to be documented as part of the system's user-interface foundations. === User stories As a designer, I need to have access to the system's cursors, so I can reuse them creating system compliant designs. === Implementation note **Why tokenize cursors?** While it seems obvious to rely on browser default cursor values, there are a few decisions that include custom `cursor` values, like for example on specific custom DOM disabled elements (with `disabled` property a rare exception) or `pointer` carrying buttons and other inputs. Those are an opinionated choice and should for example be theme-able. Compare https://developer.mozilla.org/en-US/docs/Web/CSS/cursor **Which cursor theme values are necessary?** - default - grab - grabbing - help - move - not-allowed - pointer (also known as “hand”) - text All of above are currently in use by #OOUI widgets and will be needed in #Codex components over time too. ===Acceptance criteria to resolve [] The system's cursors are defined and documented