Skip to content

Comments

SUR-506 - [Org Schema] Type dropdown is not working, conflict with ForceUI and code#317

Merged
vrundakansara merged 7 commits intostagingfrom
select-and-dropdown-component-improvement
May 2, 2025
Merged

SUR-506 - [Org Schema] Type dropdown is not working, conflict with ForceUI and code#317
vrundakansara merged 7 commits intostagingfrom
select-and-dropdown-component-improvement

Conversation

@jaieds
Copy link
Contributor

@jaieds jaieds commented May 2, 2025

Description

Screenshots

Types of changes

How has this been tested?

Checklist:

  • My code is tested
  • My code passes the PHPCS tests
  • I've created the npm build.
  • My code follows accessibility standards
  • My code has proper inline documentation
  • I've included any necessary tests
  • I've included developer documentation
  • I've added proper labels to this pull request

jaieds added 6 commits May 2, 2025 12:10
- Upgrade Floating-UI library.
- Changed strategy to `fixed`.
- Add visually hidden dismiss button for mobile devices.
- Introduced DropdownMenu.ContentWrapper for improved structure.
- Updated stories to demonstrate usage without DropdownMenu.Portal.
- Adjusted rendering logic to support new ContentWrapper.
- Added documentation for DropdownMenu usage within Dialogs, Drawers, and Popovers.
- Select component should be inside the Atom not molecule.
@vrundakansara vrundakansara merged commit a7359b8 into staging May 2, 2025
4 checks passed
@vrundakansara vrundakansara deleted the select-and-dropdown-component-improvement branch May 2, 2025 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants