-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
BlockUI does not unblock blockable-div after blocking. #14855
Comments
Hi Guys, just wondering if any updates on this issue. Kind Regards, Roland @ Sothecom |
Hello All, hope all is well. Just checking for any updates. Thanks Roland |
I'm also experiencing this bug after updating PrimeNG, are there any updates or workarounds? Thanks @Sothecom @mehmetcetin01140 It's not just the console error, the overlay fails to be removed |
Hi! @jbkly @Sothecom @mehmetcetin01140 I had similar issue after updating PrimeNG, but I imported BrowserAnimationsModule, the issue is gone. |
I had the same issue. I use Angular's v17+ I would appreciate a fix, so that it works with async version as well. |
Thanks @SergeyGor85 This worked. |
Thanks @shaman-apprentice This also works and does seem a cleaner solution, even before the async version |
I'm experiencing this problem in an Angular v16 project using PrimeNG LTS v16.9.11-LTS. Really annoying.... |
In our case there where missing styles causing the blockui to not unblock .p-component-overlay-leave { @Keyframes p-component-overlay-leave-animation { |
Hi Team, |
Thank you, using primeng 17.18.9 and this is the only thing that helped. 🥳 |
Thank you so much!! That solved my problem as well. |
Describe the bug
I set simple p-blockUI which targets a simple blockable-div (which implements BlockableUI).
There are also 2 buttons which set a boolean value to the [locked] property of the p-blockUI.
When I click to block, the overlay is applied as expected.
However when I click to unblock, I get the console error
"ERROR DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node"
On inspection of the DOM elements, it looks like the overlay div, with display: none, nestled under the p-blockUI on load.
After blocking is triggered, the overlay div appears to be moved to under the blockable-div.
It looks as if when I want to unblock, the overlay div is being searched for in it's original location ...where it no longer is.
The above is a simplified example of what is happening on a Live application.
Environment
Windows 10 Enterprise
64-bit operating system, x64-based processor
Reproducer
https://github-rnckdv.stackblitz.io
Angular version
17.2.0
PrimeNG version
17.7.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.11.0
Browser(s)
Edge 120.0.2210.121 (Official build) (64-bit), Chrome Version 120.0.6099.225 (Official Build) (64-bit)
Steps to reproduce the behavior
Issue is shown in Stackblitz (Component Parent1 and BlockabledIV).
However, this what it looks liKe locally...
Then on unblocking, I get...
NB: The issue happens with or without the textfield.
Just for quick reference, this is the relevant bit of the code...
Expected behavior
The text was updated successfully, but these errors were encountered: