-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Let the user choose where to place a DynamicDialog rather than in body #9546
Comments
I would also like this feature. I implemented a global context-menu (for translating labels and stuff), and it doesn't work on dynamicdialog. Now there are possible solutions to this, but it would be much cleaner to append the dynamicdialog to a top-level div (or something). The contextmenu does work in the (plain) dialog component. |
Hi, So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you reopen the issue so we can include it in our roadmap? Best Regards, |
The issue is still relevant, although as a workaround I'm closing all dialogs when the app displays the "reconnecting" overlay. |
@mertsincan I have created a PR for this request |
I'm submitting a ... (check one with "x")
Current behavior
When creating a DynamicDialog, PrimeNG creates an element as a direct child of the element. This is non-configurable.
Expected behavior
It'd be nice to have a parameter like
appendTo
to specify which element to attach the dialog to. I need to wrap every element created in a<div>
but right now it's not possible.What is the motivation / use case for changing the behavior?
The aim is to block the entire UI with a graphic filter when the app is in the "reconnecting" state. The filter can be applied to a divider that contains the entire UI.
Angular version: 9
PrimeNG version: 9.1.3
The text was updated successfully, but these errors were encountered: