In order to keep you up to date, you will be informed about the changes of the HTML5 chat here, this will be updated every time there is a new version.
The HTML5 chat is currently accessible by typing ?new after the chat name, e.g.: https://xat.com/html5?new
To see the version number in the chat, click at your profile > settings. If it doesn't show the latest version, you may have to clear your cache.
Bug: If you want to report a bug, you can do so here: https://forum.xat.com/bug-tracker/html5-chat/
Feedback: If you want to leave your feedback or make a suggestion, you can do so here: https://forum.xat.com/forum/223-html5/
Changelog - Version July 4, 2020
You can now quote messages or add bold/italic/striketrough/link formatting to your text.
More information on the new markdown feature here.
8ball - smilies:
When using search, smilies which are the main power smiley, will now be indicated with a different style.
After using search, clicking on the main power smiley will now show all the smilies of this power.
When using smilies form the “other” list, they will now show up regardless of a gback setting such as (clear).
When click on a power, there’s now a return button which brings you right at the previous position.
You can now use up to 512 characters on your name! This only works if your name contains codes such as smilies or glow. Otherwise, it will be limited 90.
We have added a user setting that allows you to change the text direction to RTL (right to left) and vice versa. This can also be changed with a command, by simply sending /rtl or /ltr in the chat.
On friendlist-search, search by regname should now work for most users.
In the 8ball window, when an element is loading it will now show a loader.
On Firefox, a new scroll bar has been added.
A critical issue has been fixed that would prevent your messages from being sent after watching a Youtube video on the side-app.
An issue has been fixed where a tooltip button would show up when switching chat tabs.
Smilies within the 8ball window would not show for unregistered users, this issue is now fixed.
See older changelog: