You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ X ] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35
Current behavior
With the new overlay behavior, when using appendTo="body", the menu/tieredmenu overlay appended to the body disappears while the one that would be created inside the element appears within the duration of the fade-out animation. This can cause misalignment issues when dismissing the overlay.
PROBLEM: As of version 6.0.2, the stackblitz template IS NOT SHOWING ANY OF THE MENU OVERLAYS (couldn't figure why). Reverting to 6.0.1 solves this issue, but makes impossible to reproduce the problem, as it only happens with the changes in 6.0.2.
Angular version: 6.X
PrimeNG version: 6.0.2
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Plunkr Case (Bug Reports)
https://stackblitz.com/edit/github-ek8bvt-gt4kxu?file=src/app/app.component.html
Current behavior
With the new overlay behavior, when using
appendTo="body"
, the menu/tieredmenu overlay appended to the body disappears while the one that would be created inside the element appears within the duration of the fade-out animation. This can cause misalignment issues when dismissing the overlay.Expected behavior
Minimal reproduction of the problem with instructions
https://stackblitz.com/edit/github-ek8bvt-gt4kxu?file=src/app/app.component.html
PROBLEM: As of version 6.0.2, the stackblitz template IS NOT SHOWING ANY OF THE MENU OVERLAYS (couldn't figure why). Reverting to 6.0.1 solves this issue, but makes impossible to reproduce the problem, as it only happens with the changes in 6.0.2.
The text was updated successfully, but these errors were encountered: