Identifies the currently active element when DOM focus is on a composite widget, textbox, group, or application.
Indicates whether assistive technologies will present all, or only parts of, the changed region based on the change notifications defined by the aria-relevant attribute.
Indicates whether inputting text could trigger display of one or more predictions of the user's intended value for an input and specifies how predictions would be presented if they are made.
Indicates an element is being modified and that assistive technologies MAY want to wait until the modifications are complete before exposing them to the user.
Indicates the current "checked" state of checkboxes, radio buttons, and other widgets.
Defines the total number of columns in a table, grid, or treegrid.
Defines an element's column index or position with respect to the total number of columns within a table, grid, or treegrid.
Defines the number of columns spanned by a cell or gridcell within a table, grid, or treegrid.
Identifies the element (or elements) whose contents or presence are controlled by the current element.
Indicates the element that represents the current item within a container or set of related elements.
Identifies the element (or elements) that describes the object.
Identifies the element that provides a detailed, extended description for the object.
Indicates that the element is perceivable but disabled, so it is not editable or otherwise operable.
Indicates what functions can be performed when a dragged object is released on the drop target.
Identifies the element that provides an error message for the object.
Indicates whether the element, or another grouping element it controls, is currently expanded or collapsed.
Identifies the next element (or elements) in an alternate reading order of content which, at the user's discretion, allows assistive technology to override the general default of reading in document source order.
Indicates an element's "grabbed" state in a drag-and-drop operation.
Indicates the availability and type of interactive popup element, such as menu or dialog, that can be triggered by an element.
Indicates whether the element is exposed to an accessibility API.
Indicates the entered value does not conform to the format expected by the application.
Indicates keyboard shortcuts that an author has implemented to activate or give focus to an element.
A label to apply to the dialog. Either this or the aria-labelledby prop
							are required for accessibility.
An id pointing to an element that is a label for the dialog. Either this or
							the aria-label prop are required for accessibility.
Defines the hierarchical level of an element within a structure.
Indicates that an element will be updated, and describes the types of updates the user agents, assistive technologies, and user can expect from the live region.
Indicates whether an element is modal when displayed.
Indicates whether a text box accepts multiple lines of input or only a single line.
Indicates that the user may select more than one item from the current selectable descendants.
Indicates whether the element's orientation is horizontal, vertical, or unknown/ambiguous.
Identifies an element (or elements) in order to define a visual, functional, or contextual parent/child relationship between DOM elements where the DOM hierarchy cannot be used to represent the relationship.
Defines a short hint (a word or short phrase) intended to aid the user with data entry when the control has no value. A hint could be a sample value or a brief description of the expected format.
Defines an element's number or position in the current set of listitems or treeitems. Not required if all elements in the set are present in the DOM.
Indicates the current "pressed" state of toggle buttons.
Indicates that the element is not editable, but is otherwise operable.
Indicates what notifications the user agent will trigger when the accessibility tree within a live region is modified.
Indicates that user input is required on the element before a form may be submitted.
Defines a human-readable, author-localized description for the role of an element.
Defines the total number of rows in a table, grid, or treegrid.
Defines an element's row index or position with respect to the total number of rows within a table, grid, or treegrid.
Defines the number of rows spanned by a cell or gridcell within a table, grid, or treegrid.
Indicates the current "selected" state of various widgets.
Defines the number of items in the current set of listitems or treeitems. Not required if all elements in the set are present in the DOM.
Indicates if items in a table or grid are sorted in ascending or descending order.
Defines the maximum allowed value for a range widget.
Defines the minimum allowed value for a range widget.
Defines the current value for a range widget.
Defines the human readable text alternative of aria-valuenow for a range widget.
The animation classNames applied to the component as it enters or exits.
							A single name can be provided and it will be suffixed for each stage: e.g.
classNames="fade" applies fade-enter, fade-enter-active,
						fade-exit, fade-exit-active, fade-appear, and fade-appear-active.
Each individual classNames can also be specified independently like:
classNames={{
  appear: 'my-appear',
  appearActive: 'my-appear-active',
  appearDone: 'my-appear-done',
  enter: 'my-enter',
  enterActive: 'my-enter-active',
  enterDone: 'my-enter-done',
  exit: 'my-exit',
  exitActive: 'my-exit-active',
  exitDone: 'my-exit-done'
}}
					An optional component to use instead of the default
							LayoutCloseNavigationButton in the header.
Any additional props to provide the LayoutCloseNavigationButton.
An optional className to apply to the dialog container when the type is
								set to "centered" or when the forceContainer prop is enabled. You
							probably don't want to use this prop in most cases.
An optional style to apply to the dialog container when the type is set
								to "centered" or when the forceContainer prop is enabled. You probably
							don't want to use this prop in most cases.
Either the "first" or "last" string to focus the first or last focusable element within the container or a query selector string to find a focusable element within the container.
Boolean if the ability to close the dialog via the escape key should be disabled. You should really not be using this as it breaks accessibility in most cases.
Note: When the modal prop is enabled, this flag will be considered true
						as well so that the escape keypress no longer closes the dialog.
By default, the focus container will try to maintain a cache of the focusable elements that is updated only when this component re-renders. If the children are extremely dynamic and focusable elements can be removed/added without this component updating, you should disable the cache so that the focusable elements are updated each time the tab key is pressed. Disabling the cache will be slightly slower for larger focusable areas, but it might not be too bad.
NOTE: The only important elements are the first and last elements in this list. So if your children aren't changing the first and last elements, there's no need to disable the cache.
Boolean if the dialog's focus container logic should be disabled. This
								should normally be kept at the default of false unless implementing a
							custom dialog that does not require consistent user focus.
The default behavior for the focus container is to focus an element once it
								is mounted and the disabled prop is not enabled. This behavior can be
							disabled if this is not wanted for some reason.
Boolean if the element that gets focused on mount should try to not scroll
								the focused element into view which is the default behavior. This should
								normally remain false, but it is useful to set to true if the
							FocusContainer is within a transition that appears offscreen.
The default behavior for the focus container is to attempt to focus the element that was focused before the focus container was mounted since it is generally used for temporary material. If there are cases where this behavior is not wanted, you can enable this prop.
The Dialog component will attempt to automatically fix nested dialogs
								behind the scenes using the NestedDialogContextProvider component. This
								prop will disable that feature if it does not seem to be working as
							expected.
Boolean if the appear, enter, and exit transitions should be disabled
								for the dialog.  This is just a shortcut so all three of those props don't
							need to be disabled.
Enable or disable enter transitions.
Enable or disable exit transitions.
An optional header element to display before the navigation tree and
								children. When this is omitted, it will default to the
							LayoutNavigationHeader component with some reasonable defaults.
Any additional props to provide to the default LayoutNavigationHeader
							component.
An optional title to display within the LayoutNavigationHeader component
							that will be wrapped in an AppBarTitle.
Any additional props that should be passed to the AppBarTitle that
							surrounds the headerTitle.
The size to use for sheets that have been positioned left or right. The default supported values are:
min-width is set to be the entire viewport width minus a
								touchable area and max-width is set to 20rem and is normally
							recommended for mobile devices.16rem and generally used for
							landscape tablets and desktops.The id to use for the main navigation sheet element. When this is omitted,
							this will be defaulted to: ${baseId}-nav-container.
Show the component; triggers the enter or exit states
Hints at the type of data that might be entered by the user while editing the element or its contents
Specify that a standard HTML element should behave like a defined custom built-in element
Boolean if being rendered as the mini variant. This will override some
							other behavior and styling within this component.
By default the child component is mounted immediately along with the
								parent Transition component. If you want to "lazy mount" the component on
								the first in={true} you can set mountOnEnter. After the first enter
								transition the component will stay mounted, even on "exited", unless you
							also specify unmountOnExit.
Callback fired before the "entering" status is applied. An extra
													parameter isAppearing is supplied to indicate if the enter stage is
												occurring on the initial mount
Callback fired after the "entered" status is applied. An extra parameter isAppearing is supplied to indicate if the enter stage is occurring on the initial mount
Callback fired after the "entering" status is applied. An extra parameter isAppearing is supplied to indicate if the enter stage is occurring on the initial mount
Callback fired before the "exiting" status is applied.
Callback fired after the "exited" status is applied.
Callback fired after the "exiting" status is applied.
Boolean if there should be an overlay displayed with the sheet. This is recommended/required on mobile devices.
An optional className to apply to the overlay.
Boolean if the overlay should be "hidden" from the user once it's visible
								be keeping the opacity set to 0. This is really only used for custom
							dialogs like the FixedDialog.
An optional style to apply to the overlay.
Boolean if the portal should be used.
The location that the sheet should be located within the viewport.
Boolean if the mini navigation should be treated as a "sticky" element.
								This should really only be true if disabling the fixed AppBar behavior
							in the Layout.
The tab index for the sheet. This should normally stay at -1.
When this is omitted, the default navigation tree will not be rendered and
								the only content that will be displayed will be the optional header
							element and any provided children.
When the focus container unmounts, it will attempt to re-focus the element
								that was focused before the focus container was mounted unless the
								disableFocusOnUnmount prop is enabled. There might be cases where
								unmounting the focus container causes the page to re-render and the
								previous element no longer exists. When this happens keyboard users might
								have a problem navigating through the page again depending on how the
								browser implemented the native tab behavior so this prop allows you to
							ensure that a specific element is focused in these cases.
This can either be a query selector string, a specific HTMLElement, or a function that finds a specific HTMLElement to focus.
By default the child component stays mounted after it reaches the
								'exited' state. Set unmountOnExit if you'd prefer to unmount the
							component after it finishes exiting.
The size to use for sheets that have been positioned top or bottom. The supported sizes are:
Generated using TypeDoc
Normally a component is not transitioned if it is shown when the
<Transition>component mounts. If you want to transition on the first mount set appear to true, and the component will transition in as soon as the<Transition>mounts. Note: there are no specific "appear" states. appear only adds an additional enter transition.