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

NbToastrService: Notifications can't be closed in Firefox and Internet Explorer #865

Closed
1 of 2 tasks
minextu opened this issue Oct 5, 2018 · 2 comments · Fixed by #944
Closed
1 of 2 tasks

NbToastrService: Notifications can't be closed in Firefox and Internet Explorer #865

minextu opened this issue Oct 5, 2018 · 2 comments · Fixed by #944

Comments

@minextu
Copy link

minextu commented Oct 5, 2018

Issue type

I'm submitting a ... (check one with "x")

  • bug report
  • feature request

Issue description

Current behavior:

Notifications created using NbToastrService won't hide in Firefox and Internet Explorer 11.
It's working fine in Chrome.

Expected behavior:

The notification closes when you click on it or the timeout expires.

Steps to reproduce:

Show a notification using NbToasterService with default options in Firefox or Internet Explorer 11 and try to close it.

Can also be reproduced in the documentation: https://akveo.github.io/nebular/example/toastr/toastr-showcase.component

Other information:

Browser

Browser: Firefox 62, Internet Explorer 11

Nebular

nebular: 2.0.1
@Tibing
Copy link
Member

Tibing commented Oct 26, 2018

Hi all, the bug has to be resolved after the PR will be merged. If it will not work properly try to uncomment // import 'web-animations-js';. in your polyfills.ts

@issue-sh issue-sh bot added In Review and removed In Progress labels Oct 26, 2018
@issue-sh issue-sh bot removed the In Review label Oct 26, 2018
nnixaa pushed a commit that referenced this issue Oct 26, 2018
Angular animations have a bug. All properties have to be expanded to work properly in firefox and edge.

Closes #865
@codinronan
Copy link

@Tibing any way this can be merged into the 2.x version as 2.0.3 or something? I would like to incorporate this fix but can't upgrade to Angular 7 for now...

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

Successfully merging a pull request may close this issue.

5 participants