opened
ViRuSTriNiTy
username_0
... and updated tests (children.js still shows issues)

see issue #9
Fixes issue #9 - added unique event name "showandtell"
issue
created
hypesystem
username_1
This looks pretty good. Are the tests still passing?

I think I might prefer the events to be namespaced, eg. `showandtell.remove` instead of `remove` (and also instead of your proposed `showandtell` with reason: remove). What do you think about that?

Thanks for taking the time to make a PR :-)
comment
created
ViRuSTriNiTy
username_0
All tests are passing but i can't get `children.js` to work. Would you mind taking a look what`s the issue there? 

As for the namespaced event name, i initialy opted towards this solution but i found some issues with it like:

https://stackoverflow.com/questions/4718841/namespaced-custom-events-trigger

Maybe i should just try it out, perhaps this issue isn't there anymore.
comment
created
hypesystem
username_1
Fair, let's go with the model for event naming you have implemented for now.

What output is children.js giving you?
comment
created
hypesystem
username_1
Oh! I think maybe children.js never worked, so you're ok leaving it broken :-) (I know this is really bad practice, but it is as-yet unfixed...)
comment
created
hypesystem
username_1
I will just merge your code :-)
comment
created
ViRuSTriNiTy
username_0
Side note: i've tested namespace events with jQuery 2.1.4 and jQuery 3.0, seems to work properly, so the stackoverflow issue does not exist anymore.
comment
created
ViRuSTriNiTy
username_0
Another side note: the `children.js` test was never working as you added these tests in an issue discussion, see here: https://github.com/username_1/showandtell.js/issues/7#issuecomment-34924762
comment
created
hypesystem
username_1
Cool. I think maybe we should go for the namespaced events before we make a release, if there aren't any issues with them? What do you say?
comment
created
ViRuSTriNiTy
username_0
Namespace incoming in PR #12, see also issue #11
comment