Consecutive calling with different position values

[danosaure]

The position attribute on the call makes it feel like it can be placed at different position. But when I make a call, it seems the first position wins and all future toast are put at the same place.

Is this intentional or a bug?

If intentional, it seems like it would be better served to have a $.toast.init({...}) function.

[picotrain]

This bug still exists. First call position over rules next call position. Any fix ideas other than to $.toast().reset('all'); before calling the next toast?

Nice work though otherwise, dig it.