Unable to get it work with IE11

[madanv]

Hi, I have implemented the toasty as suggested in example and it not working in IE11. However, I was able to get it work on Firefox.

Is there something I have missed in configuring it properly. Please help.

[mydearxym]

IE 8 is also unsupported ~ these angluar flash-like plugins seems unfriendly to IEs ...

[Krazymins]

Hi,

It definitely doesn't work with IE11. Is there any fix issue scheduled?

Thanks a lot

[Ehesp]

Hello, what's the error? Don't have the means to test on IE11 at the moment.

[Krazymins]

Hello,

Thanks for your answer Actually when several events are dispatched sequentially, toasty messages are not systematically displayed.

For instance :

• (1) We click on the button. The first toasty message is displayed
• (2) We click on the button. The second toasty message is NOT displayed
• (3) We click on the button. The second toasty message is displayed
• (4) We click on the button. The third toasty message is displayed
• (5) We click on the button. The fourth AND the fifth toasty message are displayed.

EDIT : we've found a solution for this display issue : by encapsulating the push with $apply, it seems working :

scope.$apply(function () {
  // Push up a new toast item
  scope.toasty.push(toast);
});

[Ehesp]

@Krazymins does this fix all issues with the $apply?

[Krazymins]

Hi Ehesp,

Actually it came with another issue. Unfortunately sometimes we have a "$digest already in progress" message. This stinks. So we rollbacked to the previous situation, and removed $apply(...)

We have been able to resolve it by using a $timeout :

$timeout(function () {
    // Push up a new toast item
    scope.toasty.push(toast);
});

It also works if the fix is in our own code, when we call this.toasty.error(...), instead of using the $timeout in the component code.

The issue is when several toasties with the same message are displayed, there can be display issues as explained above.

With the $timemout workaround, everything works perfectly, including on IE11.

It may not be the most beautiful way to resolve the issue, but it works as expected.

Thanks a lot.

[Ehesp]

I suspect the timeout is pushing it onto the next "tick". Can you make a PR for me with the update? I'll test it on Chrome and things.

Cheers

[redwyre]

I seem to be having this issue in chrome, just calling toasty.success every 5 seconds with the same details. The $timeout workaround works for me too.