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

Allow specify portal destination for all portaled components #3687

Open
menthol opened this issue Mar 26, 2025 — with Volta.net · 1 comment · May be fixed by #3688
Open

Allow specify portal destination for all portaled components #3687

menthol opened this issue Mar 26, 2025 — with Volta.net · 1 comment · May be fixed by #3688
Labels
v3 #1289

Comments

Copy link

menthol commented Mar 26, 2025

Currently, portal components (modals, popovers, etc.) are directly attached to the root of the body. It would be beneficial to allow specifying their destination within the configuration .This would provide greater control over rendering order and potential styling conflicts, especially in complex applications with open shadow Dom.

For instance, a developer might want to render a modal within a specific container to inherit styles or avoid interference with other elements on the page (I currently using Nuxt ui as a web component withing WordPress).

The proposed configuration option could be a CSS selector string, allowing for flexible targeting of any existing element in the DOM defaulting to 'body'.

@menthol menthol linked a pull request Mar 26, 2025 that will close this issue
8 tasks
@benjamincanac benjamincanac added the v3 #1289 label Mar 28, 2025
Copy link
Author

menthol commented Apr 2, 2025

@benjamincanac: I've updated the PR, can you check it out?

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

Successfully merging a pull request may close this issue.

2 participants