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
IMPORTANT: I could not reproduce the issue using plnkr, so I attached a small zip file ngx-modialog-demo.zip
I'm submitting a bug
Do you want to request a feature or report a bug?
Report a bug.
What is the current behavior?
If I open a modal in two more more tabs from a BroadcastChannelonMessage event, only one of the modals is opened and the rest of the tabs have a thin line (ie the modal template is not rendered). The modal html looks like the following
NOTE: I was able to reproduce the issue in Angular 4.
Browser: [Chrome XX | Firefox XX ]
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
I could workaround this issue if I click anywhere on the overlay. So I put the following hack inside my components temporarily
setTimeout(()=>{// Fixes the modal not rendering issue.document.body.click()})
The text was updated successfully, but these errors were encountered:
IMPORTANT: I could not reproduce the issue using plnkr, so I attached a small zip file ngx-modialog-demo.zip
I'm submitting a bug
Do you want to request a feature or report a bug?
Report a bug.
What is the current behavior?

If I open a modal in two more more tabs from a
BroadcastChannel
onMessage
event, only one of the modals is opened and the rest of the tabs have a thin line (ie the modal template is not rendered). The modal html looks like the followingnpm install
(ie Restore modules)ng serve --port 1234
) and open it in two or more tabs.What is the expected behavior?
You should see the modal in all opened tabs 2 seconds after the tab is opened.
What is the motivation / use case for changing the behavior?
I expect the modal to be shown in all tabs instead of a thin line.
Please tell us about your environment:
ng --version
NOTE: I was able to reproduce the issue in Angular 4.
I could workaround this issue if I click anywhere on the overlay. So I put the following hack inside my components temporarily
The text was updated successfully, but these errors were encountered: