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.

Sign up for GitHub

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

Jump to bottom

Chat duplication #132

Open
zbeekman opened this issue Feb 5, 2015 · 2 comments
Open

Chat duplication #132

zbeekman opened this issue Feb 5, 2015 · 2 comments
Labels
ready

Comments

@zbeekman
Copy link
Contributor

zbeekman commented Feb 5, 2015

This seems to be client side:

screen shot 2015-02-05 at 10 25 11 am

JavaScript Console - not sure if this is useful at all…

I have no idea how to recreate this, so I guess there’s probably nothing to be done unless it happens again. A page refresh seems to have fixed this.
@zbeekman
Copy link
Contributor Author

zbeekman commented Jun 1, 2016

@martindale has anyone seen this recently? I haven't seen it in ages and am wondering if it has been resolved...

@martindale
Copy link
Member

This does happen when you perform /stream off and then /stream on again. It's just a doubly-bound event listener that someone needs to track down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ready
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martindale @zbeekman