These are the remaining tasks before we can start using @wordpress/ui components in the Gutenberg app. Any other blockers will be added to this list as we discover them.

• Fix common/form CSS situation @wordpress/ui: Add global CSS defense module #76783
• Lint rule to restrict certain component imports ESLint: Add use-recommended-components rule #76222
• Stabilize and confirm text overflow behavior (especially Button, Badge)
• Tabs: Indicator color consistency with legacy tab components Tabs, TabPanel: Align styles with wp-ui #78418
• VisuallyHidden: Needs to work with [isElementVisible()] Expand support for isElementVisible (VisuallyHidden) #77191(

  gutenberg/packages/block-editor/src/utils/dom.js

  Line 83 in 9eec223

  function isElementVisible( element ) {

  )
• Apply new focus ring styles to @wordpress/components
• Overlay components (popovers, dialogs, modals, tooltips, dropdowns...) need a compat layer
• Update cursor styles in @wordpress/components Theme: Change default control cursor to pointer #76762
• Lint rule to use consistent import names for @wordpress/components with conflicting names ESLint: Add use-import-as rule #77389

The official introduction of ThemeProvider and design tokens stylesheet needs separate planning, but is not technically a blocker to start component adoption.