@workday/canvas-kit-docs 9.1.1 → 9.1.3

package/dist/es6/lib/docs.js

@@ -1245,7 +1245,7 @@ export const docs = (typeof window !== 'undefined' && window.__docs) ||
         {
           "name": "Target",
           "symbol": "ExpandableTarget",
-          "description": "`Expandable.Target` creates a heading and a button. The heading is a semantic heading to\ndescribe the associated content. The button provides users the ability to toggle the\nassociated content.\n\nAs according to the [W3 disclosure\nspecification](https://www.w3.org/TR/wai-aria-practices-1.1/#disclosure), the button has\n`aria-expanded` and `aria-controls` attributes set by default\n\nThis component should hold an `Expandable.Icon`, an optional `Expandable.Avatar`, and an\n`Expandable.Title`.",
+          "description": "`Expandable.Target` creates a heading and a button. The heading is a semantic heading to\ndescribe the associated content. The button provides users the ability to toggle the\nassociated content.\n\nAs according to the [W3 disclosure\nspecification](https://www.w3.org/WAI/ARIA/apg/patterns/disclosure/), the button has\n`aria-expanded` and `aria-controls` attributes set by default\n\nThis component should hold an `Expandable.Icon`, an optional `Expandable.Avatar`, and an\n`Expandable.Title`.",
           "declarations": [
             {
               "name": "Target",
@@ -7169,7 +7169,7 @@ export const docs = (typeof window !== 'undefined' && window.__docs) ||
   {
     "name": "DeprecatedMenu",
     "fileName": "/home/runner/work/canvas-kit/canvas-kit/modules/preview-react/menu/lib/Menu.tsx",
-    "description": "As of Canvas Kit v8, Menu is being deprecated.\nIt will be removed in v10. Please see the [upgrade\nguide](https://workday.github.io/canvas-kit/?path=/story/welcome-upgrade-guides-v8-0--page) for\nmore information.\n\n`DeprecatedMenu` renders a styled `<ul role=\"menu\">` element within a {@link Card} and follows\nthe [Active Menu\npattern](https://www.w3.org/TR/wai-aria-practices/examples/menu-button/menu-button-actions-active-descendant.html)\nusing `aria-activedescendant`.\n\nUndocumented props are spread to the underlying `<ul>` element.",
+    "description": "As of Canvas Kit v8, Menu is being deprecated.\nIt will be removed in v10. Please see the [upgrade\nguide](https://workday.github.io/canvas-kit/?path=/story/welcome-upgrade-guides-v8-0--page) for\nmore information.\n\n`DeprecatedMenu` renders a styled `<ul role=\"menu\">` element within a {@link Card} and follows\nthe [Active Menu\npattern](https://www.w3.org/WAI/ARIA/apg/patterns/menu-button/examples/menu-button-actions-active-descendant/)\nusing `aria-activedescendant`.\n\nUndocumented props are spread to the underlying `<ul>` element.",
     "declarations": [
       {
         "name": "DeprecatedMenu",
@@ -77499,7 +77499,7 @@ export const docs = (typeof window !== 'undefined' && window.__docs) ||
   {
     "name": "useListItemRovingFocus",
     "fileName": "/home/runner/work/canvas-kit/canvas-kit/modules/react/collection/lib/useListItemRovingFocus.tsx",
-    "description": "This elemProps hook is used for cursor navigation by using [Roving\nTabindex](https://w3c.github.io/aria-practices/#kbd_roving_tabindex). Only a single item in the\ncollection has a tab stop. Pressing an arrow key moves the tab stop to a different item in the\ncorresponding direction. See the [Roving Tabindex](#roving-tabindex) example. This elemProps hook\nshould be applied to an `*.Item` component.\n\n```ts\nconst useMyItem = composeHooks(\n  useListItemRovingFocus, // adds the roving tabindex support\n  useListItemRegister\n);\n```",
+    "description": "This elemProps hook is used for cursor navigation by using [Roving\nTabindex](https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#kbd_roving_tabindex). Only a single item in the\ncollection has a tab stop. Pressing an arrow key moves the tab stop to a different item in the\ncorresponding direction. See the [Roving Tabindex](#roving-tabindex) example. This elemProps hook\nshould be applied to an `*.Item` component.\n\n```ts\nconst useMyItem = composeHooks(\n  useListItemRovingFocus, // adds the roving tabindex support\n  useListItemRegister\n);\n```",
     "declarations": [
       {
         "name": "useListItemRovingFocus",
@@ -79029,7 +79029,7 @@ export const docs = (typeof window !== 'undefined' && window.__docs) ||
   {
     "name": "useListModel",
     "fileName": "/home/runner/work/canvas-kit/canvas-kit/modules/react/collection/lib/useListModel.tsx",
-    "description": "The List model contains the the state and events necessary to track items, selection, and a cursor.\nVarious hooks can be used for a List model to create common behaviors associated with lists, such as\nnavigating a list with a keyboard, selection (single and multiple), and virtualization.\n\nA list also has a \"cursor\". A cursor is often represented by focus, but it is not always a 1:1\nmapping. Think of the cursor as the focus item within the list. If the list has browser focus, the\ncursor will map to browser focus. Behaviors such as `useListRovingFocus` will map the cursor to the\nactive tab stop of the list. For more information, see\n[Roving Tabindex](https://w3c.github.io/aria-practices/#kbd_roving_tabindex). `useListRovingFocus`\nadds keyboard events that map to navigation events. A [Navigation Manager](#navigation-manager) is\nused to map new cursor ids to these events. The `ListModel` takes an optional `navigation`\nconfiguration to change the default navigation behavior. The default navigation manager is a\n[wrappingNavigationManager](#wrappingnavigationmanager) meaning the cursor will wrap around the\nbeginning and the ends. The cursor also provides a [navigationManager](#navigationmanager) that does\nnot wrap. This is the default navigation for grids.\n\nThe cursor also adds the concept of `orientation` which defaults to `'vertical'`. A Tab list is an\nexample of a `'horizontal'` list.\n\n```tsx\nconst list = useListModel({\n  // custom handling for selection. single and multi select are provided\n  selection: mySelectionManager,\n  // wrapping and non-wrapping navigation are provided\n  navigation: myNavigationManager,\n  items: [{ id: '1', text: 'First'}, { id: '2', text: 'Second' }],\n  getId: item => item.id, // get the unique identifier of your item\n})\n```",
+    "description": "The List model contains the the state and events necessary to track items, selection, and a cursor.\nVarious hooks can be used for a List model to create common behaviors associated with lists, such as\nnavigating a list with a keyboard, selection (single and multiple), and virtualization.\n\nA list also has a \"cursor\". A cursor is often represented by focus, but it is not always a 1:1\nmapping. Think of the cursor as the focus item within the list. If the list has browser focus, the\ncursor will map to browser focus. Behaviors such as `useListRovingFocus` will map the cursor to the\nactive tab stop of the list. For more information, see\n[Roving Tabindex](https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#kbd_roving_tabindex). `useListRovingFocus`\nadds keyboard events that map to navigation events. A [Navigation Manager](#navigation-manager) is\nused to map new cursor ids to these events. The `ListModel` takes an optional `navigation`\nconfiguration to change the default navigation behavior. The default navigation manager is a\n[wrappingNavigationManager](#wrappingnavigationmanager) meaning the cursor will wrap around the\nbeginning and the ends. The cursor also provides a [navigationManager](#navigationmanager) that does\nnot wrap. This is the default navigation for grids.\n\nThe cursor also adds the concept of `orientation` which defaults to `'vertical'`. A Tab list is an\nexample of a `'horizontal'` list.\n\n```tsx\nconst list = useListModel({\n  // custom handling for selection. single and multi select are provided\n  selection: mySelectionManager,\n  // wrapping and non-wrapping navigation are provided\n  navigation: myNavigationManager,\n  items: [{ id: '1', text: 'First'}, { id: '2', text: 'Second' }],\n  getId: item => item.id, // get the unique identifier of your item\n})\n```",
     "declarations": [
       {
         "name": "useListModel",
@@ -79483,7 +79483,7 @@ export const docs = (typeof window !== 'undefined' && window.__docs) ||
   {
     "name": "ListModel",
     "fileName": "/home/runner/work/canvas-kit/canvas-kit/modules/react/collection/lib/useListModel.tsx",
-    "description": "The List model contains the the state and events necessary to track items, selection, and a cursor.\nVarious hooks can be used for a List model to create common behaviors associated with lists, such as\nnavigating a list with a keyboard, selection (single and multiple), and virtualization.\n\nA list also has a \"cursor\". A cursor is often represented by focus, but it is not always a 1:1\nmapping. Think of the cursor as the focus item within the list. If the list has browser focus, the\ncursor will map to browser focus. Behaviors such as `useListRovingFocus` will map the cursor to the\nactive tab stop of the list. For more information, see\n[Roving Tabindex](https://w3c.github.io/aria-practices/#kbd_roving_tabindex). `useListRovingFocus`\nadds keyboard events that map to navigation events. A [Navigation Manager](#navigation-manager) is\nused to map new cursor ids to these events. The `ListModel` takes an optional `navigation`\nconfiguration to change the default navigation behavior. The default navigation manager is a\n[wrappingNavigationManager](#wrappingnavigationmanager) meaning the cursor will wrap around the\nbeginning and the ends. The cursor also provides a [navigationManager](#navigationmanager) that does\nnot wrap. This is the default navigation for grids.\n\nThe cursor also adds the concept of `orientation` which defaults to `'vertical'`. A Tab list is an\nexample of a `'horizontal'` list.\n\n```tsx\nconst list = useListModel({\n  // custom handling for selection. single and multi select are provided\n  selection: mySelectionManager,\n  // wrapping and non-wrapping navigation are provided\n  navigation: myNavigationManager,\n  items: [{ id: '1', text: 'First'}, { id: '2', text: 'Second' }],\n  getId: item => item.id, // get the unique identifier of your item\n})\n```",
+    "description": "The List model contains the the state and events necessary to track items, selection, and a cursor.\nVarious hooks can be used for a List model to create common behaviors associated with lists, such as\nnavigating a list with a keyboard, selection (single and multiple), and virtualization.\n\nA list also has a \"cursor\". A cursor is often represented by focus, but it is not always a 1:1\nmapping. Think of the cursor as the focus item within the list. If the list has browser focus, the\ncursor will map to browser focus. Behaviors such as `useListRovingFocus` will map the cursor to the\nactive tab stop of the list. For more information, see\n[Roving Tabindex](https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#kbd_roving_tabindex). `useListRovingFocus`\nadds keyboard events that map to navigation events. A [Navigation Manager](#navigation-manager) is\nused to map new cursor ids to these events. The `ListModel` takes an optional `navigation`\nconfiguration to change the default navigation behavior. The default navigation manager is a\n[wrappingNavigationManager](#wrappingnavigationmanager) meaning the cursor will wrap around the\nbeginning and the ends. The cursor also provides a [navigationManager](#navigationmanager) that does\nnot wrap. This is the default navigation for grids.\n\nThe cursor also adds the concept of `orientation` which defaults to `'vertical'`. A Tab list is an\nexample of a `'horizontal'` list.\n\n```tsx\nconst list = useListModel({\n  // custom handling for selection. single and multi select are provided\n  selection: mySelectionManager,\n  // wrapping and non-wrapping navigation are provided\n  navigation: myNavigationManager,\n  items: [{ id: '1', text: 'First'}, { id: '2', text: 'Second' }],\n  getId: item => item.id, // get the unique identifier of your item\n})\n```",
     "declarations": [
       {
         "name": "useListModel",
@@ -80643,7 +80643,7 @@ export const docs = (typeof window !== 'undefined' && window.__docs) ||
   {
     "name": "ListModelConfig",
     "fileName": "/home/runner/work/canvas-kit/canvas-kit/modules/react/collection/lib/useListModel.tsx",
-    "description": "The List model contains the the state and events necessary to track items, selection, and a cursor.\nVarious hooks can be used for a List model to create common behaviors associated with lists, such as\nnavigating a list with a keyboard, selection (single and multiple), and virtualization.\n\nA list also has a \"cursor\". A cursor is often represented by focus, but it is not always a 1:1\nmapping. Think of the cursor as the focus item within the list. If the list has browser focus, the\ncursor will map to browser focus. Behaviors such as `useListRovingFocus` will map the cursor to the\nactive tab stop of the list. For more information, see\n[Roving Tabindex](https://w3c.github.io/aria-practices/#kbd_roving_tabindex). `useListRovingFocus`\nadds keyboard events that map to navigation events. A [Navigation Manager](#navigation-manager) is\nused to map new cursor ids to these events. The `ListModel` takes an optional `navigation`\nconfiguration to change the default navigation behavior. The default navigation manager is a\n[wrappingNavigationManager](#wrappingnavigationmanager) meaning the cursor will wrap around the\nbeginning and the ends. The cursor also provides a [navigationManager](#navigationmanager) that does\nnot wrap. This is the default navigation for grids.\n\nThe cursor also adds the concept of `orientation` which defaults to `'vertical'`. A Tab list is an\nexample of a `'horizontal'` list.\n\n```tsx\nconst list = useListModel({\n  // custom handling for selection. single and multi select are provided\n  selection: mySelectionManager,\n  // wrapping and non-wrapping navigation are provided\n  navigation: myNavigationManager,\n  items: [{ id: '1', text: 'First'}, { id: '2', text: 'Second' }],\n  getId: item => item.id, // get the unique identifier of your item\n})\n```",
+    "description": "The List model contains the the state and events necessary to track items, selection, and a cursor.\nVarious hooks can be used for a List model to create common behaviors associated with lists, such as\nnavigating a list with a keyboard, selection (single and multiple), and virtualization.\n\nA list also has a \"cursor\". A cursor is often represented by focus, but it is not always a 1:1\nmapping. Think of the cursor as the focus item within the list. If the list has browser focus, the\ncursor will map to browser focus. Behaviors such as `useListRovingFocus` will map the cursor to the\nactive tab stop of the list. For more information, see\n[Roving Tabindex](https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#kbd_roving_tabindex). `useListRovingFocus`\nadds keyboard events that map to navigation events. A [Navigation Manager](#navigation-manager) is\nused to map new cursor ids to these events. The `ListModel` takes an optional `navigation`\nconfiguration to change the default navigation behavior. The default navigation manager is a\n[wrappingNavigationManager](#wrappingnavigationmanager) meaning the cursor will wrap around the\nbeginning and the ends. The cursor also provides a [navigationManager](#navigationmanager) that does\nnot wrap. This is the default navigation for grids.\n\nThe cursor also adds the concept of `orientation` which defaults to `'vertical'`. A Tab list is an\nexample of a `'horizontal'` list.\n\n```tsx\nconst list = useListModel({\n  // custom handling for selection. single and multi select are provided\n  selection: mySelectionManager,\n  // wrapping and non-wrapping navigation are provided\n  navigation: myNavigationManager,\n  items: [{ id: '1', text: 'First'}, { id: '2', text: 'Second' }],\n  getId: item => item.id, // get the unique identifier of your item\n})\n```",
     "declarations": [
       {
         "name": "useListModel",
@@ -149484,7 +149484,7 @@ export const docs = (typeof window !== 'undefined' && window.__docs) ||
   {
     "name": "Menu",
     "fileName": "/home/runner/work/canvas-kit/canvas-kit/modules/react/menu/lib/Menu.tsx",
-    "description": "`Menu` is a combination of a popup and a list. It usually has some type of target element that\nexpands/collapses the menu and a `menu` role and and several `menuitem` roles. Focus is managed\nusing [roving tabindex](https://w3c.github.io/aria-practices/#kbd_roving_tabindex) for maximum\ncompatibility. A `Menu` can have two modes: `single` and `multiple`. This mode determines both\nhow many items can be selected as well as the default behavior when a `menuitem` is clicked. For\nthe `single` mode, selecting a `menuitem` will select and close the menu. For the `multiple`\nmode, clicking a `menuitem` will toggle selection and will not close the menu.\n\n```tsx\n<Menu>\n  <Menu.Target>Open</Menu.Target>\n  <Menu.Popper>\n    <Menu.Card>\n      <Menu.List>\n        <Menu.Item data-id=\"first\">First Item</Menu.Item>\n        <Menu.Item data-id=\"second\">Second Item</Menu.Item>\n      </Menu.List>\n    </Menu.Card>\n  </Menu.Popper>\n</Menu>\n```",
+    "description": "`Menu` is a combination of a popup and a list. It usually has some type of target element that\nexpands/collapses the menu and a `menu` role and and several `menuitem` roles. Focus is managed\nusing [roving tabindex](https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#kbd_roving_tabindex) for maximum\ncompatibility. A `Menu` can have two modes: `single` and `multiple`. This mode determines both\nhow many items can be selected as well as the default behavior when a `menuitem` is clicked. For\nthe `single` mode, selecting a `menuitem` will select and close the menu. For the `multiple`\nmode, clicking a `menuitem` will toggle selection and will not close the menu.\n\n```tsx\n<Menu>\n  <Menu.Target>Open</Menu.Target>\n  <Menu.Popper>\n    <Menu.Card>\n      <Menu.List>\n        <Menu.Item data-id=\"first\">First Item</Menu.Item>\n        <Menu.Item data-id=\"second\">Second Item</Menu.Item>\n      </Menu.List>\n    </Menu.Card>\n  </Menu.Popper>\n</Menu>\n```",
     "declarations": [
       {
         "name": "Menu",

package/dist/es6/lib/specs.js

@@ -516,6 +516,21 @@ module.exports = {specifications: [
                         ]
                       }
                     ]
+                  },
+                  {
+                    "type": "describe",
+                    "name": "when the user types in a value not found",
+                    "children": [
+                      {
+                        "type": "describe",
+                        "name": "when the user hits the enter key",
+                        "children": []
+                      },
+                      {
+                        "type": "it",
+                        "name": "should not clear the input"
+                      }
+                    ]
                   }
                 ]
               }

package/dist/mdx/preview-react/menu/Menu.mdx

@@ -37,7 +37,7 @@ how you might implement that behavior using a [`Popup`](/components/popups/popup
 closing the `DeprecatedMenu`.
 
 `DeprecatedMenu` follows the
-[Actions Menu pattern](https://www.w3.org/TR/wai-aria-practices/examples/menu-button/menu-button-actions-active-descendant.html)
+[Actions Menu pattern](https://www.w3.org/WAI/ARIA/apg/patterns/menu-button/examples/menu-button-actions-active-descendant/)
 using `aria-activedescendant`. Below is table of supported keyboard shortcuts and associated
 actions.
 

package/dist/mdx/react/collection/Collection.mdx

@@ -76,10 +76,11 @@ along to the collection component.
 #### Roving Tabindex
 
 The list system also includes a cursor that extends the list. A cursor is mostly used for focusing
-items. The [roving tabindex](https://w3c.github.io/aria-practices/#kbd_roving_tabindex) is a
-well-supported way to accomplish accessibility requirements for focusing items within a list. This
-example shows how to use `useListRovingFocus`. This example uses the `ListBox` component, but the
-default `ListBox.Item` is very basic. We have two options, we can either pass additional
+items. The
+[roving tabindex](https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#kbd_roving_tabindex)
+is a well-supported way to accomplish accessibility requirements for focusing items within a list.
+This example shows how to use `useListRovingFocus`. This example uses the `ListBox` component, but
+the default `ListBox.Item` is very basic. We have two options, we can either pass additional
 functionality via `elemPropsHook` or by creating a new item using our elemProps hook primitives.
 Both will be demonstrated. Creating a custom item is recommended if you create a custom component
 and export it. Using `elemPropsHook` with `ListBox.Item` is recommended only for one-off instances.

package/dist/mdx/react/menu/Menu.mdx

@@ -31,7 +31,7 @@ yarn add @workday/canvas-kit-react
 model which composes a list model and a popup model and sets up accessibility features for you.
 
 `Menu` follows the
-[Actions Menu pattern](https://www.w3.org/TR/wai-aria-practices/examples/menu-button/menu-button-actions.html)
+[Actions Menu pattern](https://www.w3.org/WAI/ARIA/apg/patterns/menu-button/examples/menu-button-actions/)
 using roving tabindex. Below is table of supported keyboard shortcuts and associated actions.
 
 | Key                | Action                                                                                                       |

package/dist/mdx/react/tabs/Tabs.mdx

@@ -33,7 +33,7 @@ yarn add @workday/canvas-kit-react
 
 `Tabs` includes a container `Tabs` component and the following subcomponents which can be composed
 in a variety of ways: `Tabs.List`, `Tabs.Item` and `Tabs.Panel`. It follows the
-[W3 Tabs specification](https://www.w3.org/TR/wai-aria-practices/#tabpanel).
+[W3 Tabs specification](https://www.w3.org/WAI/ARIA/apg/patterns/tabs/).
 
 In this example, we set up a basic `Tabs` component with five tabs. This example uses a static API
 that does not support overflow.

package/dist/mdx/react/tooltip/Tooltip.mdx

@@ -31,7 +31,7 @@ yarn add @workday/canvas-kit-react
 ## Usage
 
 This component follows the
-[W3 Tooltip specification](https://www.w3.org/TR/wai-aria-practices/#tooltip). Tooltips are used to
+[W3 Tooltip specification](https://www.w3.org/WAI/ARIA/apg/patterns/tooltip/). Tooltips are used to
 label buttons with icons and provide additional context to elements.
 
 ### When to use tooltips

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@workday/canvas-kit-docs",
-  "version": "9.1.1",
+  "version": "9.1.3",
   "description": "Documentation components of Canvas Kit components",
   "author": "Workday, Inc. (https://www.workday.com)",
   "license": "Apache-2.0",
@@ -44,9 +44,9 @@
   "dependencies": {
     "@emotion/styled": "^11.6.0",
     "@storybook/csf": "0.0.1",
-    "@workday/canvas-kit-labs-react": "^9.1.1",
-    "@workday/canvas-kit-preview-react": "^9.1.1",
-    "@workday/canvas-kit-react": "^9.1.1",
+    "@workday/canvas-kit-labs-react": "^9.1.3",
+    "@workday/canvas-kit-preview-react": "^9.1.3",
+    "@workday/canvas-kit-react": "^9.1.3",
     "@workday/canvas-system-icons-web": "^3.0.0",
     "markdown-to-jsx": "^6.10.3",
     "ts-node": "^10.9.1"
@@ -57,5 +57,5 @@
     "mkdirp": "^1.0.3",
     "typescript": "4.2"
   },
-  "gitHead": "1fd1ede048d1977dbf565ad9e78dcd3786a7b5c2"
+  "gitHead": "e05ca047d5cb85ed194a626c92d143e9e0805733"
 }