Change Details

== Background We've inherited some ways of building our components from OOUI. One of these is represented in `position-offset` token category, currently used in Radio. The negative position offset is building the focus outline on selected Radios. We've got a second token with negative value, which is used to construct border overlaps, `@position-offset-border-width-base`. The biggest issue, aside of the SFC, is currently user text zooming limitations. | Before (very large user text zoom) | After | {F35892204 width=50%} | {F35892206 width=50%} == Acceptance criteria [] Replace Radio offset with relative size [] Replace Message offset SFCs with size tokens

== Background We've inherited some ways of building our components from OOUI. One of these is represented in `position-offset` token category, currently used in Radio. The negative position offset is building the focus outline on selected Radios. We've got a second token with negative value, which is used to construct border overlaps, `@position-offset-border-width-base`. The biggest issue, aside of the SFC, is currently user text zooming limitations. | Before (very large user text zoom) | After | {F35892204 width=50%} | {F35892206 width=50%} == Acceptance criteria [x] Replace Radio offset with relative size [x] Replace Message offset SFCs with size tokens

== Background We've inherited some ways of building our components from OOUI. One of these is represented in `position-offset` token category, currently used in Radio. The negative position offset is building the focus outline on selected Radios. We've got a second token with negative value, which is used to construct border overlaps, `@position-offset-border-width-base`. The biggest issue, aside of the SFC, is currently user text zooming limitations. | Before (very large user text zoom) | After | {F35892204 width=50%} | {F35892206 width=50%} == Acceptance criteria [x] Replace Radio offset with relative size [x] Replace Message offset SFCs with size tokens