Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug - Dropdown Next - Unable to specify an appendTo target for the menu bug #9564

Closed
wise-king-sullyman opened this issue Sep 1, 2023 · 1 comment · Fixed by #9652
Closed
Assignees
Milestone

Comments

@wise-king-sullyman
Copy link
Contributor

Describe the problem
Currently we can't customize what the menu appends to in Dropdown next.

How do you reproduce the problem?
Attempt to have the dropdown menu append anywhere in the DOM other than the default location.

Expected behavior
A clear and concise description of the expected behavior.
We should be able to have the menu append elsewhere in the DOM.

This issue is for the "Next" implementation of Dropdown in PF4

@github-project-automation github-project-automation bot moved this to Needs triage in PatternFly Issues Sep 1, 2023
@wise-king-sullyman wise-king-sullyman moved this from Needs triage to Backlog in PatternFly Issues Sep 15, 2023
@adamviktora adamviktora self-assigned this Sep 20, 2023
@adamviktora adamviktora moved this from Backlog to In Progress in PatternFly Issues Sep 20, 2023
@adamviktora adamviktora moved this from In Progress to PR Review in PatternFly Issues Sep 20, 2023
@adamviktora adamviktora moved this from PR Review to In Progress in PatternFly Issues Sep 20, 2023
@wise-king-sullyman wise-king-sullyman moved this from In Progress to Done in PatternFly Issues Sep 20, 2023
@tlabaj tlabaj modified the milestones: Prioritized Backlog, 2023.Q4 Sep 28, 2023
@adamviktora adamviktora moved this from Done to PR Review in PatternFly Issues Oct 2, 2023
@adamviktora adamviktora moved this from PR Review to Done in PatternFly Issues Oct 9, 2023
@adamviktora
Copy link
Contributor

closing the issue manually, as #9652 was merged, and it somehow did not link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants