If you are on mobile you can get to it by clicking the side bar thing. And it will have chat below where it says forums.
Put it back
If you're concerned about user-retention, then I imagine a lot of people would find it obnoxious if there's no on-site method to turn off the chat. I thank you for remedying that issue.
While you're here, I (and many others) would appreciate a fix to this:
This is still a significant problem, so I looked into it with the limited information I have available.
messageEdit uses .innerHTML to get the edit input field's content, which outputs escaped HTML. Messages send from the normal input field are processed using .textContent to get the input's content, so this is why there are no escaping issues in normal messages.var messageEdit = function messageEdit(messageEl) {
messageEditReverse();
messageEl.classList.add("chat-message--editing");
var contentEl = messageEl.querySelector(".message");
messageEl.originalMessage = contentEl.outerHTML;
var formEl = document.getElementById("new-message-form").cloneNode(true);
formEl.id = "edit-message-form";
var inputEl = formEl.querySelector(".chat-input");
inputEl.id = "edit-message-input";
var submitEl = formEl.querySelector("button.submit");
//submitEl.id = "edit-message-input";
submitEl.remove();
contentEl.replaceWith(formEl);
inputEl.innerHTML = messageEl.rawMessage;
inputAddEventListeners(inputEl);
inputEl.addEventListener("keydown", function(event) {
switch(event.key){
case "Escape":
event.preventDefault();
messageEditReverse();
return false;
case "Enter":
event.preventDefault();
messageSend("/edit " + JSON.stringify({
id: parseInt(messageEl.dataset.id, 10),
message: this.innerHTML
}));
messageEditReverse();
return false;
}
});
// Apparently, .focus() doesn't work on contenteditable=true until one frame after.
inputFocusEnd(inputEl);
};document.getElementById("new-message-input").addEventListener("keydown", function(event) {
switch(event.key){
case "Enter":
event.preventDefault();
messageSend(this.textContent);
this.innerHTML = "";
return false;
case "ArrowUp":
if (!this.innerHTML) {
event.preventDefault();
var messageEls = document.getElementById("chat-messages").querySelectorAll(".chat-message[data-author='".concat(APP.user.id, "']"));
if (messageEls.length > 0) {
var messageEl = messageEls[messageEls.length - 1];
messageEdit(messageEl);
}
return false;
}
}
});.textContent or unescaping the .innerHTML result would most likely fix this.
Or how about stop bitching? Ever consider that?
Just get banned from it and it'll stop appearing.
Any chance I can get you to make this one line change?
I and many others in chat would appreciate it greatly.
I noticed the chat opens a totally new connection for every single tab. If I've got 5 tabs open, that's 5 separate sockets and 5 handshakes spamming the server. You might want to look into moving the socket to a SharedWorker. It lets the browser share just one connection across all open tabs, which should cut down the CPU load from handshakes significantly.