diff --git a/packages/react-bindings/src/accessibility/getAccessibility.ts b/packages/react-bindings/src/accessibility/getAccessibility.ts index 76906a98ef..db1bf49274 100644 --- a/packages/react-bindings/src/accessibility/getAccessibility.ts +++ b/packages/react-bindings/src/accessibility/getAccessibility.ts @@ -33,7 +33,7 @@ const getAccessibility = >( if (process.env.NODE_ENV !== 'production') { // For the non-production builds we enable the runtime accessibility attributes validator. // We're adding the data-aa-class attribute which is being consumed by the validator, the - // schema is located in @stardust-ui/ability-attributes package. + // schema is located in @fluent-ui-react/packages/ability-attributes. if (definition.attributes) { Object.keys(definition.attributes).forEach(slotName => { const validatorName = `${displayName}${slotName === 'root' ? '' : `__${slotName}`}` diff --git a/specs/Button.md b/specs/Button.md index c6324f45f5..393dffec24 100644 --- a/specs/Button.md +++ b/specs/Button.md @@ -43,7 +43,7 @@ The following are variants that exist because of the need of `Buttons` to reside - In Ant Design - In Semantic UI - In Shards React - - In Stardust UI + - In Fluent UI - `Button group/set` - In Ant Design - In Atlaskit @@ -54,7 +54,7 @@ The following are variants that exist because of the need of `Buttons` to reside - In React Bootstrap - In Semantic UI - In Shards React - - In Stardust UI + - In Fluent UI - `Conditional button` - In Semantic UI - `Floating action/Raised button` @@ -119,11 +119,11 @@ The following section documents links to different UI libraries implementations - [Shards React Button docs](https://designrevision.com/docs/shards-react/component/button) -- [Stardust Button docs](https://microsoft.github.io/fluent-ui-react/components/button/definition) +- [Fluent UI Button docs](https://microsoft.github.io/fluent-ui-react/components/button/definition) ## Props -The following section documents the properties that will become part of the new component, as well as the process for mitigating all changes when moving from Fabric and Stardust to Fluent UI. +The following section documents the properties that will become part of the new component, as well as the process for mitigating all changes when moving to Fluent UI. > TODO: Consult the prop wizard to derive consistently defined props. @@ -223,7 +223,7 @@ https://developer.microsoft.com/en-us/fabric#/controls/web/button | `toggled` | `boolean` | Already deprecated in favor of `checked`. | | `uniqueId` | `string \| number` | This is used for keytip support in Fabric. Maybe remove it until we add `Keytips` in Fluent UI? | -### Stardust Button props +### Fluent UI Button props #### ButtonProps interface @@ -306,7 +306,7 @@ https://developer.microsoft.com/en-us/fabric#/controls/web/button | `toggled` | Removing as it is already deprecated. | ☑ | No, because prop is already deprecated. | ❌ | | `uniqueId` | TBD | ❌ | ❌ | ❌ | -### Conversion process from Stardust to Fluent UI Button +### Conversion process from old Fluent UI to new Fluent UI Button #### ButtonProps interface @@ -632,7 +632,7 @@ None. - Has no built-in support for icons via props. -### Stardust Button +### Fluent UI Button #### Example DOM @@ -899,7 +899,7 @@ render() { | `endIconColorPrimaryHovered` | | | `endIconColorPrimaryPressed` | | -NOTE! Stardust does not follow this convention. Their `Button` currently uses these tokens: +NOTE! Fluent UI does not follow this convention. Their `Button` currently uses these tokens: ``` backgroundColor: string diff --git a/specs/Checkbox.md b/specs/Checkbox.md index 04af936b31..de84cc555c 100644 --- a/specs/Checkbox.md +++ b/specs/Checkbox.md @@ -12,11 +12,11 @@ The `Checkbox` component allows a user to choose between two mutually exclusive https://codesandbox.io/s/checkboxes-ggpx1 -Note about the Stardust example: there's some weirdness with how the theme providers are interacting with each other, the Stardust checkbox's styling is messing up as a result. +Note about the Fluent UI example: there's some weirdness with how the theme providers are interacting with each other, the Fluent UI checkbox's styling is messing up as a result. Fabric Checkbox [docs](https://developer.microsoft.com/en-us/fabric#/controls/web/Checkbox) -Stardust Checkbox [docs](https://microsoft.github.io/fluent-ui-react/components/checkbox/definition) +Fluent UI Checkbox [docs](https://microsoft.github.io/fluent-ui-react/components/checkbox/definition) Open UI Checkbox [docs](https://open-ui.org/components/checkbox) @@ -69,7 +69,7 @@ https://developer.microsoft.com/en-us/fabric#/controls/web/checkbox | styles | IStyleFunctionOrObject| | | theme | ITheme | | -### Stardust Checkbox props +### Fluent UI Checkbox props | Name | Type | Notes | @@ -91,7 +91,7 @@ https://developer.microsoft.com/en-us/fabric#/controls/web/checkbox | toggle | boolean | default false | | variables | any | | -### Differences of Fabric/Stardust to resolve +### Differences of Fabric/Fluent UI to resolve | Name | Type | Notes | | -------------------- | -------------------------------------------------------- | -------------------------------------------------------------------------------| @@ -147,7 +147,7 @@ Removing the following two props because the ARIA spec dictates role='checkbox' ### Conversion process from Fabric 7 to Fluent UI Checkbox -#### Fluent Checkbox recommended props interface +#### Fluent UI Checkbox recommended props interface | Name | To transition or not?| Property transitioned? | Breaking change? | Codemod/Shim created? | | -----------------------------| -------------------- | :--------------------: | :--------------: | :-------------------: | @@ -222,7 +222,7 @@ Could consider supporting an invalid state/error state but this might just be su ``` -### Stardust Checkbox example DOM +### Fluent UI Checkbox example DOM ```html ``` -### Stardust Slider example DOM +### Fluent UI Slider example DOM - Extra wrapper div - input element to receive focus @@ -411,7 +411,7 @@ render() { | trackColorPressed | | | trackSize | | -NOTE! Stardust does not follow this convention. Slider currently uses these tokens: +NOTE! Fluent UI does not follow this convention. Slider currently uses these tokens: ``` activeThumbColor: string