Announcements

Canvas v10 Release

Canvas v10 will be released on October 25th, 2023 with updates to Canvas Kit and the Canvas Figma libraries. An upgrade guide will be available once v10 goes live to assist product teams with upgrading to the newest version of Canvas.

The v10 release will focus on revamping Canvas tokens and components to support a Canvas theme, starting with Buttons! This Canvas theme will serve as the foundation for future theming work, which could include brand specific and user selected themes, like dark mode.

Release Overview

The table below contains a high-level overview of the updates that will be rolled out as part of the v10 release. The impact for designers and developers are defined as follows:

• None: inapplicable to the role or no actions are required for users to adopt the change; Updates will be applied automatically once users upgrade to Canvas Kit v9 and/or switch to the new v10 Canvas Web Figma library
• Low: minor changes are required for users to adopt the change
• Medium: a moderate amount of changes are required for users to adopt the change, such as switching out UI elements
• High: a large amount of changes are required for users to adopt the change, requiring product teams to make major design or development decisions

New Token Structure and Naming Convention

Canvas tokens will be restructured in Canvas v10 to:

• Enable scalable visual changes at the core token level that flows across all Canvas components
• Increase cohesion across Canvas components by standardizing token usage with semantic tokens
• Empower product teams to build custom components using semantic tokens that can evolve with Canvas tokens

There are three level of Canvas tokens, which includes:

• Base Tokens: tokens that represent hard coded values like a hex code or rem value. These tokens are maintained by the Canvas Design System team and should rarely be used by product teams.
• System Tokens: tokens that are intended to be used by product teams. They are semantic, meaning that they are named according to how they should be used. These tokens are the most similar to what is available in Canvas today (ex: type, depth).
• Brand Tokens: tokens that are used to set key brand colors and can be used by tenants to theme certain components to reflect their brand color.

With the current token structure, changing the hex value of Cinnamon 500 will result in a change to all components using Cinnamon 500, regardless of the context in which it is being used. This new three layer token structure along with the shift to a more semantic naming format allows the Canvas Design System to maintain and modify base tokens without impacting the intended use cases of system or brand tokens. As a result, teams using system tokens and brand tokens based on their intended use cases will be able to uptake those changes without the need for modifying their components.

Note: Color system tokens are still in development and will not be ready for the Canvas v10 release, but all other system tokens (ex: depth, space) will be available at the start of v10.

This new token set will also use rem as a unit of measurement instead of pixels to standardize Canvas tokens and improve the scalability of tokens across various screen sizes. All tokens will use rem as a unit of measurement, except for color tokens which will continue to utilize hex codes.

To support the new token structure, a new naming convention will also be implemented to help teams easily distinguish between different token levels.

This new token structure and naming convention will not result in breaking changes in code since the current set of tokens are not being modified or deprecated as part of v10. Instead, a new Canvas Tokens repo will be created to store the new set of tokens, which will also be ported into Canvas Kit React. The current token set will not be deprecated until Canvas fully migrates over to the new token structure and naming convention. However, developers will be able to use the new token set as part of v10.

For designers, the current Canvas Tokens Figma library will be renamed to “Canvas Tokens v1” and a new Canvas Tokens v2 Figma library will be created to store the new set of tokens and give designers more control with their token upgrades. Designers staying on Canvas v9 or older will still have access to the same token set and subsequent Figma styles. In order to use the new token set, designers upgrading to Canvas v10 will need to:

• Perform a library swap to the new Canvas v10 Figma library
• Turn on the new Canvas Tokens v2 Figma library
• And turn the old Canvas Tokens v1 library off

Please note that this work is ongoing and will span across multiple Canvas releases. However, the new token set is subject to change as they are rolled out across all Canvas components.

New Space and Shape Figma Variables

New Figma variables will be released with v10 for Canvas space and shape tokens. These Figma variables will contain the pre-set values of all Canvas space and shape tokens to help designers quickly switch between different space and shape tokens without needing to reference documentation or memorize the token values. Variables are only visible when using the associated design property. As such, space variables are only visible within the Auto Layout window while shape variables can only be utilized as corner radiuses in Figma.

To learn more about variables, view Figma’s tutorial on intro to variables.

This update is Figma specific and will not impact developers.

New Opacity System Token

A new opacity token will now be introduced with the new token structure. The opacity disabled token will be the only opacity system token introduced in v10. It is set to 40% opacity to be used with disabled states, which does not have to meet contrast requirements to be accessible.

This token will be available in code for developers with the new token set.

However, opacity tokens will not be available as a Figma as opacity is currently not supported in Figma as a style or variant.

New Styling Strategy for Buttons

A new styling strategy will start rolling out in Canvas v10 in parallel with the token and theming work, starting with Canvas buttons. Canvas will begin shifting towards static styling with the use of CSS variables as opposed to dynamic styling via Emotion to improve performance and reduce the need for full page style recalculations.

As part of this work, Canvas buttons styles will be refactored to use the new cs styling function. The style refactoring will allow Primary, Secondary, Tertiary, and Delete buttons to use the new tokens in the form of CSS variables through the CanvasProvider.

While Canvas will be moving away from styling with Emotion, Canvas users will still be able to use Emotion. This update will not impact developers. More information about the new styling strategy can be found in this GitHub discussion.

This is a code specific update and will not impact designers.

Token Rollout to Canvas Buttons

Canvas’s Primary, Secondary, Tertiary, and Delete buttons will be updated to use the new system and brand level tokens. Elements that are meant to be brandable, like the text color of Primary buttons, will be tied to a brand token. However, certain elements will be tied to base level tokens for the time being as new system tokens are created throughout the roll out process.

This update will not be a breaking change for developers, but developers will be able to see the new system and brand tokens being used to create Canvas buttons.

This will also not be a breaking change for designers as the Canvas buttons in the Canvas Web v10 Figma library will be linked to the new system and brand tokens automatically. Since Canvas components have always been structured to reference tokens, the new token set will also be rolled out across all Canvas components in the Canvas Web v10 Figma library. Please note that this will temporarily create a discrepancy between what is available in code as Canvas components must be refactored in code before they can uptake the new token set.

Tertiary Inverse Button Styling Standardization

The inverse variant of Tertiary buttons will be updated to align with the styling of the inverse variants of the Primary and Secondary buttons using the new token set.

By connecting the inverse variant of Tertiary buttons to the same set of tokens used by Primary and Secondary buttons, the background color for the hover state of the inverse Tertiary buttons will be updated from French Vanilla 100 to Soap 300.

The new background color will be applied automatically once designers upgrade to Canvas v10 and will not result in any breaking changes. This update will also be reflected in code, but no action will be required from developers to uptake this change.

Button Focus Ring Update

We found that focus rings were not consistent across all buttons. We've updated the focus ring on the inverse variant of PrimaryButton to display a consistent focus ring across PrimaryButton and SecondaryButton. The changes to PrimaryButton will need to be taken note of due to small visual changes with the inverse variant.

Also, colors will no longer support the focusRing option.

import {focusRing} from '@workday/canvas-kit-react/common';

// v9
<PrimaryButton
  colors={{
    // other colors
    focus: {
      // other colors
     focusRing: focusRing(/* options */)
    }
  }}
/>

// v10
<PrimaryButton
  colors={{
    // other colors
    focus: {
      // other colors
    }
  }}
  css={{
    ':focus-visible': focusRing(/* options */)
  }}
/>;

Removal of 13px Figma Font Styles

Previously deprecated 13px type styles will be removed in the Canvas Tokens v2 Figma library. These font sizes were deprecated in Canvas v5 and while they’ll still be available for designers through the Canvas Tokens V1 library, they will not be supported in the Canvas Tokens v2 Figma library.

When designers swap over to the Canvas Tokens v2 Figma library, type styles using 13px font size will no longer be available for use in the Figma styles menu. However, all other type styles will still be supported in the new Canvas Tokens v2 Figma library. Designs using the deprecated 13px text styles will persist after the library swap, but it is recommended for designers to switch over to using a supported text style to align with other Workday products.

This update is Figma specific and will not impact developers.

Tooltip Font Style Update

Tooltip will be updated in Figma to use the Subtext M - (400) Regular text style instead of the deprecated 13px text styles to align with what is available in code. The current 13px text styles have been deprecated since v5 and will be fully removed in v10. This update will not increase the line height of tooltip, but it will decrease the width of tooltip as the font size will decrease to 0.75 rem (the equivalent of 12px). The top and bottom padding will also increase from 0.375 to .5 rems (the equivalent of moving from 6 to 8px) in order to maintain the current height of the tooltip component.

This update is Figma specific and will not impact developers. However, it will result in a visual change for designers, but the update will be applied automatically once designers upgrade to v10.

Space and Depth Rem Conversion

The current space and depth tokens in Canvas Kit will be updated to use rem instead of pixels in order to maintain consistency across all Canvas tokens and align with the new unit of measurement that will be utilized by the new token set. spaceNumbers will continue to be based in pixels, but will be deprecated in v10 as part of the transition over to rem based tokens.

This update to rem will impact developers using string literals. Additional resources will be provided to help developers switch over to rem.

Please see the discussion on px to rem migration.

This is a code specific update and will not impact designers.

Deprecation of spaceNumbers

spaceNumbers will be deprecated in v10 as part of the move towards rem based tokens. Teams using spaceNumbers can continue to do so in v10, but deprecation warnings will appear when it is in use.

Please see the discussion on px to rem migration.

It is recommended for developers to switch over to using CSS calc() instead as spaceNumbers will eventually be removed.

This is a code specific update and will not impact designers.

Select Compound Component Conversion

The Select component in Main will be replaced with a Select compound component as part of an effort to standardize component APIs and give developers more flexibility with customizing Canvas components.

This new Select component will be visually similar to the Select in Preview, but with the following design changes:

• The focus ring, error ring, and warning ring will no longer wrap around the menu for Select. Instead, rings will only wrap around the Select input to better align borders across different web browsers.
• The spacing between the menu and its target element will increase from 0px to 4px in order to prevent the menu from overlapping with the focus, error, and warning rings. This change is being made to the Popup component directly, which will flow into Menu and Select as well.
• The maximum height of the menu has been increased from 200px to 300px to accommodate 7 single-line items (the minimum number of items we recommend including in a Select) without triggering overflow. The maximum height may be overriden.

Developers using the current Select component in Main will have to change the API to match the new compound component's API. It is also recommended for developers using the Select component in Preview to switch over to the compound component version of Select, which will give them more flexibility and control over Select.

The compound component conversion is a code specific change, but the visual changes will be applied to the Select component in the Canvas Web v11 Figma library. The Select component in Figma is reflective of the Select component in Preview, which is still available for use in v10. No changes will be made to the Select component in Figma for the time being to minimize the number of breaking changes for designers in this release.

Deprecation of Select in Preview

The Select component in Preview will be deprecated in Canvas Kit with the introduction of the new Select compound component in Main. Select in Preview will still be available for use in Canvas v10, but deprecation warnings will appear when it is in use.

Developers should start replacing all instances of Select in Preview with the new Select compound component in Main, which will be available as part of the v10 release.

This is a code specific update and will not impact designers.

Deprecation of InputIconContainer

InputIconContainer will be deprecated in Canvas Kit. It will still be available for use in Canvas v10, but deprecation warnings will appear when it is in use.

Developers using InputIconContainer should switch over to using InputGroup, which has an added bidirectionality feature and can support icons at the start of an input.

This is a code specific update and will not impact designers.

Deprecation of Table in Main

The Table component in Main will be deprecated in Canvas Kit. It will still be available for use in Canvas v10, but deprecation warnings will appear when it is in use.

Developers using the Table component in the Main package should switch over to using the new Table in Preview, which has been updated to be more flexible with a more modern design.

This is a code specific update and will not impact designers.

September 2023 Design Asset Release

The September 2023 Design Asset Release is now available for use through the Canvas Assets Figma library for designers and npm, Artifactory, or SAS (in all environments) for developers.

The following assets were updated as part of this release:

• Third Party Icons (upgrade @workday/third-party-icons-web to 1.0.9)
  • wd-icon-twitter-x.svg (twitterXIcon when using SystemIcon) is now available for use
  • wd-icon-glassdoor-2.svg (glassdoor2Icon when using SystemIcon) is now available for use

These third party icons will be released as net new icons. The existing twitterIcon and glassdoorIcon icons will continue to exist, but teams may begin utilizing the updated version of those icons with this release.

This release will not impact developers, and designers can upgrade to the latest version of the Canvas Asset Figma library without any impact to their existing designs.

For more information or to access these new icons in this update, please reference the Design Asset repo.

July 2023 Design Asset Release

The July 2023 Design Asset Release is now available for use through the Canvas Assets Figma library.

This month's design asset release will be Figma specific to catch up on icon updates from previous releases, which includes:

• An updated workdayCircleIcon third party icon with the correct dub and sunrise element

Please accept these changes in Figma to get access to the updated icons.

For more information, please reference the Design Asset repo.

Canvas Kit 9.1.0 Release

Canvas Kit 9.1.0 is now available!

Radio Compound Component

The Radio compound component is finally here! Teams using Radio in Main should start switching over to the new Radio compound component in Preview, which will give teams more control over individual sub-components within Radio.

CSS Scroll Attributes for Box, Flex, and Grid

New CSS scroll attributes have been added to Box, Flex, and Grid to enable product teams to configure Layout components with CSS.

Status Indicator Deprecation

The Status Indicator component in Main has been deprecated. Teams using the Status Indicator in Main should switch over to the updated Status Indicator component in the Preview package, which has been updated to improve globalization and accessibility! The Status Indicator in Main is still available for use, but it will be removed in v11 (April 2024).

This update will not impact developers. To access these changes, please upgrade to Canvas Kit 9.1.0.

June 2023 Design Asset Release

The April 2023 Design Asset Release is now available for use through the Canvas Assets Figma library for designers and npm, Artifactory, or SAS (in all environments) for developers.

This release contains the following updates:

• System Icons (upgrade @workday/canvas-system-icons-web to 3.0.16)

  • A new wd-icon-messaging.svg icon (messagingIcon when using SystemIcon)
  • A new wd-icon-lightbulb.svg icon (lightbulbIcon)
  • A fix to the wd-icon-exclamation-triangle.svg icon (exclamationTriangleIcon) to remove a small white outline that appears around the inner triangle when the icon is being filled

• Third Party Icons (upgrade @workday/third-party-icons-web to 1.0.8)

  • A new wd-icon-android.svg icon (androidIcon when using SystemIcon)
  • A new wd-icon-apple.svg icon (appleIcon)
  • A new wd-icon-react.svg icon (reactIcon)

The Canvas Assets Figma library has been updated to include this update. This release will not impact developers and designers can upgrade to the latest version of the Canvas Asset Figma library without any impact to their existing designs.

For more information or to access these new icons in this update, please reference the Design Asset repo.

Canvas v9 Release

Canvas v9 will be released on May 10th, 2023 with updates to Canvas Kit and the Canvas Figma libraries. An upgrade guide will be available once v9 goes live to assist product teams with upgrading to the newest version of Canvas.

Release Overview

The table below contains a high-level overview of the updates that will be rolled out as part of the v9 release. The impact for designers and developers are defined as follows:

• None: inapplicable to the role or no actions are required for users to adopt the change; Updates will be applied automatically once users upgrade to Canvas Kit v9 and/or switch to the new v9 Canvas Web Figma library
• Low: minor changes are required for users to adopt the change
• Medium: a moderate amount of changes are required for users to adopt the change, such as switching out UI elements
• High: a large amount of changes are required for users to adopt the change, requiring product teams to make major design or development decisions

Canvas Web Figma Library Versioning

Versioning will be available in the Canvas Web Figma Library! This will give anyone using Figma the ability to stay on an older version, or upgrade to the latest version of the Canvas Web Library. Most importantly, this will enable product teams to design, develop, and build using the same version of Canvas. This Canvas Web v9 Figma library versioning update will include:

• Automated version upgrade process in Figma
• Improved find and search capabilities in Figma
• Updated file structure for component organization
• Prototype interaction support for all applicable Figma components
• Canvas documentation direct in Figma through Gist plug-in

The current Canvas Web Library will be renamed to “Canvas Web v8” to indicate the version of Canvas Kit that it reflects. A new version of the Canvas Web Figma library will be released called “Canvas Web v9” to reflect the latest offers in Canvas Kit v9. No action is required for teams using Canvas Kit v8. Teams that are upgrading to Canvas Kit v9 should also upgrade their design files to use the Canvas Web v9 Figma library using the new Figma upgrade process.

Upgrading to a new version (Canvas Web v9) will introduce breaking changes to affected components in your files that are mentioned below The Canvas Design team will be available to support and advise on how to accept these breaking changes. There will also be documentation available on release day to help with this as well as a demo of these new features post release.

This update is specific to the Canvas Figma libraries and will not impact developers. However, developers should keep their designers updated on their upgrade timeline for Canvas v9 to ensure design and development are using the same version of Canvas.

Depth Token Modifications

Depth tokens will be updated to retract the changes made in Canvas v7, which introduced darker depth values that resulted in a higher contrast against light colored backgrounds. The depth values will not be reverted to pre-Canvas v7 levels, but they will be modified to reduce the visual impact of depth.

Only the values of Canvas depth tokens will be modified as part of this update. Canvas components will continue to use the default depth level they are currently tagged to for the time being.

The depth changes will be applied automatically once designers update to the new Canvas Tokens Figma Library. Changes made to customize the depth level of a component will still persist, but the value of that depth level will be updated to reflect the v9 changes. Designers should review active design files and modify the depth levels their designs are using accordingly. Designers using depth tokens for components or designs created outside of Canvas should also accept the changes in the Canvas Tokens Figma library.

This update will be applied automatically once developers upgrade to Canvas Kit v9.

Table Refactoring

A new styled Table component will be available in the Preview package. This Table component will be a more modernized and flexible version of the current Table component. The Canvas Table will contain the basic features needed for Tables such as:

• Displaying data in a row/column format
• Differentiated row header
• Customizable column width
• Customizable horizontal and vertical borders

For more complex use cases with the need for built-in features and functionality, please refer to Tables 2.0

This update will not impact developers as it will be released as a net-new Table component. However, it is recommended that teams switch over to this new Table component. It will be up to product teams to add additional functionalities like tooltips, truncated text, etc. and to get them reviewed and approved by accessibility.

It will also not impact designers since Table will be introduced as a new component in the Canvas Web v9 Figma library.

New Combobox System

A new Combobox sub-system will be created to help developers build components and features using Combobox, like autocomplete and Select. This new Combobox will be released into the Main package. Deprecation warnings will be added to the current Combobox component in Labs, but will not be removed in this release. Other Canvas components that are currently using the Combobox in Labs, like Search Form, will continue to do so in v9.

This update will not impact developers. However, developers should start migrating to the new Combobox component in Main once it is released in v9.

This update is specific to Canvas Kit and will not impact existing designs.

Modal Figma Updates

To align with Canvas Kit, the following updates will be made to the Modal component in Figma as part of the v9 release: The medium sized Modal variant will be removed as developers do not have pre-set sizes for Modal in Canvas Kit and are able to adjust the size of the Modal manually With the removal of the medium sized Modal, the small Modal variant will be renamed to “Web” to keep it distinct from the responsive Modal variant that is only displayed on smaller screen sizes An overlay will be added to the web Modal variant, which is always present when using the Modal in Canvas Kit

Once designers migrate to the new Canvas Web v9 Figma library, they will need to: Switch out the medium Modal variant with the newly renamed web Modal variant to maintain the connection to a supported version of the Modal component in the Canvas Web v9 Figma library The Modal Component will need to be resized so that the overlay covers the entire viewport, keeping the Modal align center, center on screen. Switch out all instances of Modal that do not need an overlay with the new Dialog component, which does not include an overlay and will allow users to interact with the rest of the page

This update is specific to the Canvas Web v9 Figma library and will not impact developers.

New Figma Dialog Component

A new Dialog component will be added to the Canvas Web Figma library. This component is visually similar to Modal, but will not contain an overlay and will allow users to interact with the rest of the page.

This update is specific to the Canvas Web Figma library and will not impact developers. The Dialog component is already available in Canvas Kit for developers to use.

It will also not impact designers as it will be a net new component in the Canvas Web Figma library.

Segmented Control Figma Updates

The Segmented Control component currently available in the Canvas Web Figma library will be replaced with the redesigned Segmented Control component released in Canvas v8, which includes support for both text and icons. Both Segmented Control components will still be available for use in Canvas Kit. View the Canvas v8 announcement for more information on the redesigned Segmented Control component.

This update will not impact developers as both versions of Segmented Control are currently available in Canvas Kit today and there will not be any changes made to either component in v9. However, it is recommended for teams to switch over to the redesigned Segmented Control component both in the Preview package of Canvas Kit and the new Canvas Web v9 Figma library once it becomes available as the outdated Segmented Control component will be deprecated and removed at a later date.

The contents of Segmented Control in Figma will not persist when designers swap to the Canvas Web v9 Figma Library. It will default to the text only, horizontal variant with four segments. Designers should reconfigure any overrides and variants to match previous designs if they choose to upgrade to v9.

Status Indicator Figma Updates

The Status Indicator component currently available in the Canvas Web Figma library will be replaced with the redesigned Status Indicator component released in Canvas v8, which includes globalization and accessibility enhancements. Both Status Indicator components will still be available for use in Canvas Kit. View the Canvas v8 announcement for more information on the redesigned Status Indicator component.

This update will not impact developers as both versions of Status Indicator are currently available in Canvas Kit today and there will not be any changes made to either component in v9. However, it is recommended for teams to switch over to the redesigned Status Indicator component both in the Preview package of Canvas Kit and the new Canvas Web v9 Figma library once it becomes available as the outdated Status Indicator component will be deprecated and removed at a later date.

Swapping to the Canvas Web v9 Figma library will automatically swap existing Status Indicators in a design file with the new Status Indicator containing the updated visual style. This will not override pre-set color, icons, or text. If a design file is using the old Status Indicators with an icon, designers may need to perform an additional instance swap within their file to ensure pre-set customizations persist.

Switch Refactoring and Consolidation Figma Updates

The Switch component will be consolidated into a single component with variants (no label, top label, left label) to standardize the way Canvas components are built across the Canvas Figma libraries.

The Switch will default to the No Label variant available when designers perform a library swap over to the new Canvas Web v9 Figma library. Designers should reconfigure the variant to match previous designs if they choose to upgrade to v9.

This update is specific to the Canvas Web v9 Figma library and will not impact developers.

Radio Variant Consolidation

The Radio component in Figma will be refactored to reduce a large number of redundant variants and improve memory usage. There will be no change to existing functionality, but this update will minimize future bugs and instances of breaking changes going forward.

Swapping to the Canvas Web v9 Figma library will automatically swap to the updated Radio Buttons with boolean and text props. Designers may need to perform an additional instance swap within their file to preserve pre-set customizations.

This update is specific to the Canvas Web v9 Figma library and will not impact developers.

Checkbox Variant Consolidation

The Checkbox component in Figma will be refactored to reduce a large number of redundant variants and improve memory usage. There will be no change to existing functionality, but this update will minimize future bugs and instances of breaking changes going forward.

Swapping to the Canvas Web v9 Figma library will automatically swap to the updated Checkboxes with boolean and text props. Designers may need to perform an additional instance swap within their file to preserve pre-set customizations.

This update is specific to the Canvas Web v9 Figma library and will not impact developers.

Delete Button Figma Updates

The Delete Button in the Canvas Web Figma library will be updated to standardize the component structure across all Canvas buttons. This will allow the size, text, and state of the button to persist when swapping between all Canvas button types. The following updates will be made: Properties will be reordered and standardized New icon and state variants will be added to align with other button types

This will not impact existing designs.

This update is specific to the Canvas Web Figma library and will not impact developers.

Layout Component Removal

The Layout component will be removed from Canvas Kit to reduce maintenance costs and minimize the confusion around the various types of Layout components. It will no longer be available for use in Canvas v9.

Developers using the Layout component should switch over to the Grid component, which will fulfill the same functionality as Layout. The original Layout examples have been recreated using the Grid component to help developers transition off of the Layout component.

This update is specific to Canvas Kit and will not impact existing designs. Designers can continue to use the Layout Grid component in the Canvas Web Figma library, which corresponds to the Grid component in Canvas Kit.

Drawer Component Removal

The Drawer component will be removed from Canvas Kit to reduce maintenance costs and minimize the confusion around other similar components, like Side Panel. It will no longer be available for use in Canvas v9.

Developers using the Drawer component should switch over to the Side Panel component in the Preview package, which will fulfill the same functionality as Drawer.

This update is specific to Canvas Kit and will not impact existing designs.

Stack Component Removals

The Stack, HStack and VStack components will be removed from Canvas Kit to reduce maintenance costs and minimize the confusion around the various types of Layout components. These Stack components will no longer be available to use in Canvas Kit v9.

Developers should switch over to using Flex instead, which will have the same functionality as Stack, HStack, and VStack. A codemod will be available to help developers migrate to Flex. However, teams using StackProps for custom components will also need to switch out the spacing prop for the gap prop in code.

This update is specific to Canvas Kit and will not impact existing designs.

Default Button Type Modifications

The default type attribute for Canvas buttons will be updated from type="submit" to type="button" to prevent forms from accidentally being submitted when using buttons inside a form element. This change will be applied to the following Canvas buttons:

• Primary Button
• Secondary Button
• Tertiary Button
• Delete Button
• Toolbar Button

Developers that want to continue to use type="submit" will need to manually make this adjustment.

This update is specific to Canvas Kit and will not impact existing designs.

useTheme Updates

The useTheme hook will be updated to generate an error when used outside of a hook. This error has been hidden in the past, which resulted in teams incorrectly using the useTheme hook.

Developers using the useTheme hook in a regular function will need to switch it out with the getTheme instead.

This update is specific to Canvas Kit and will not impact existing designs.

useThemedRing Promotion

The useThemedRing hook will be promoted from the Labs package to Main to prevent bi-directional dependencies between the Main package and other packages like Labs and Preview.

A codemod will be available to help developers handle the migration to the Main package.

This update is specific to Canvas Kit and will not impact existing designs.

useThemeRTL Deprecation

The useThemeRTL will be deprecated from Canvas Kit as it is no longer necessary with the introduction of logical CSS properties. This hook will still be available for use in Canvas v9, but deprecation warnings will appear when it is in use.

Developers should start replacing this hook with logical CSS properties as it will be removed from Canvas Kit in the near future.

This update is specific to Canvas Kit and will not impact existing designs.

useCanvasTheme and getCanvasTheme Removal

The utility functions useCanvasTheme and getCanvasTheme will be removed in favor of useTheme and getTheme, respectively. These functions were only intended for internal use and were predecessors of useTheme and getTheme. They are being removed to get rid of unnecessary duplicates.

Developers using these functions will need to update the name of the function.

This update is specific to Canvas Kit and will not impact existing designs.

Canvas Kit’s TypeScript Compiler Target Updates

The TypeScript compiler target for Canvas Kit will be updated from ES5 to ES2019. All modern browsers support ES2019, so this update will significantly reduce the Canvas Kit bundle size.

This will not impact designers or developers. However, developers should still confirm that tests are still passing and that their application is still compiling properly.

This update is specific to Canvas Kit and will not impact existing designs.

Toast Component Promotion

The Toast compound component in the Labs package will be promoted to the Main package to replace the current Toast component in Main and reduce the number of duplicative components in Canvas Kit.

A codemod will be available to help developers handle the migration to the Main package.

This update is specific to Canvas Kit and will not impact existing designs.

Enhanced QA & Testing Processes

The Canvas QA and testing processes will be enhanced and utilized in the Canvas v9 release. This will include:

• Adding visual test for different container widths to Action Bar and Breadcrumbs
• Adding all Cypress tests to Action Bar
• Adding Cypress tests for different container widths to Breadcrumbs
• Adding Cypress tests for touch modality to Tabs and Modal
• Adding visual tests for mobile screen to Tabs and Modal
• Adding visual tests for the overflow Tabs variant

In addition to enhancing code testing, the design QA process will also be revamped to include directly testing major design changes and regressions with Workday product teams. The updated QA process will be applied to the depth token updates prior to pushing out the change in this release. This will be followed by enhanced codemod testing with additional Workday product teams.

This update will not impact designers or developers.

Previous Releases

• Canvas v8 Announcements
• Canvas v7 Announcements
• Canvas v6 Announcements