Toastr Container

[tbragaf]

Hi all!

It seems to me that after a toast is rendered (and then disappears) the container also disappears with it.
And, after that, my old container stops existing, and following toasts will render inside the default container with fixed position.

Is there anything I should be aware of?

Stay awesome,
tbragaf

[appjitsu]

I have the same issue.

https://github.com/CodeSeven/toastr/blob/master/toastr.js

line 422:

$container.remove();

I believe that is the issue.

#378

[tbragaf]

I hacked this behaviour with an empty span inside the container xD

[appjitsu]

@tbragaf hah nice!

[acshef]

The container should be RECREATED once a new toast appears. Specifically, the toastr.xxxxxx() functions will internally call the notify() function. Within notify(), it gets the container using the internal function getContainer(options,true). The second parameter being true means that it will first try to find an existing container, and if not then it will create the container and return that.

[TimFerrell]

This isn't an issue - the container is removed by design once there are no remaining toasts.

[tbragaf]

@TimFerrell So how can I achieve my purpose?

[TimFerrell]

What's your problem, specifically?

[tbragaf]

@TimFerrell I don't want the container to disappear from my div element.
I only managed to do that by spawning a span element inside the container, which is an ugly hack.

[TimFerrell]

Why are you trying to prevent the container from closing?

[tbragaf]

@TimFerrell because I want the toasts to always appear inside it.

[TimFerrell]

The container will recreate itself automatically. Maybe I'm not asking the right questions here but can you please explain why you don't want this to happen?

[tbragaf]

In my sample, the container recreates at the default position: body
And I need it inside another tag

[TimFerrell]

Sorry for the slow response. You can specify the element that the container appears within - is that not happening for you?

[tbragaf]

@TimFerrell How so?

I tried with:

<div id="toast-container">
    <!-- Only way to prevent the destruction -->
    <span></span>
</div>

[JasonLawrenceDuncan]

I ran into this same issue today. @tbragaf 's hack does work, but this sure seems like a bug to me. If the user provides a "target", you shouldn't delete it (or at least add an option to override deletion). I want to position the container relative to a parent div, not have it be dynamically injected at the bottom of the DOM.