Jump to content


Popular Content

Showing content with the highest reputation since 01/24/19 in Bug Comments

  1. 2 points
    This is not an issue actually. The timestamp for pawns has expired and since HTML5 doesn't use this system, it works like a charm I emailed admins with explanations about this and should be fixed soon.
  2. 2 points
  3. 2 points
    @Blacky The issue has been fixed now. Thank you for reporting.
  4. 1 point
    @Leandro oh, so you are talking about html5 not flash, my bad yes there are some issues that still have to be fixed, we're aware thanks
  5. 1 point
    The Hat power currently have some issues with the flash version of xat, many hats from powers aren't working, however you can still use the hat#t, hat#x .
  6. 1 point
    Hi, thanks for reporting. Currently any extra hats that are outside of the (hat) power aren't functioning. Please be patient until this is resolved. Thank you
  7. 1 point
    It will be fixed in a future update of the HTML5 chat.
  8. 1 point
    This is not something new and a similar issue was opened by Leandro a few months ago. To answer you, this is a lack of feature which is NOT added yet and not a bug. Since it was already reported, I'm closing this thread.
  9. 1 point
    This issue is already known, no need to re-report it.
  10. 1 point
    Thanks for reporting this, @DJFUNNY. We're already aware of this bug and it should be fixed in the next update.
  11. 1 point
    Hello, There is currently a bug with nameglow and namecolor which is forcing you to have HAT power to have both powers working. We are looking to fix it very soon! Thank you for reporting, you will be noticed when it is fixed.
  12. 1 point
    Changed Status to Fixed
  13. 1 point
    This has been fixed now. The fix is as follows: Using an old register link will redirect you to the new register page, containing the user id / k1 / k2 info in the link already (full redirect). So should just be able to register on the new web. Thank you for letting us know.
  14. 1 point
    @Kaay your chat is back now. Sorry for the inconveniences.
  15. 1 point
    Has been fixed now. @HelperNate
  16. 1 point
    Thank you for reporting. This has been forwarded.
  17. 1 point
    Ok, this information has now been added to the article: https://util.xat.com/wiki/index.php?title=Single Other editors can review before it's marked for translation, if they want.
  18. 1 point
  19. 1 point
  20. 1 point
    This is not a HTML5 bug. @Angelo The bug he reported is when you add a "<3" on status, it will change your name (for other people) to "nope" which was done by purpose. Since this is not a HTML5 bug, i'm closing this thread.
  21. 1 point
    Ok, catch it. Seems that CSP is blocking something to be loaded correctly. When logging storage isn't being fully stored. What I did: I've logged-in using Google Chrome, copied all HTML5 data storage and replaced on Firefox, it worked fine. I've checked both and seems that Firefox's data isn't being stored "k3". Firefox shows "0", on Chrome shows correctly.
  22. 1 point
    @xLaming what is this about? happens on new web too?
  23. 1 point
    This was fixed on the new web registration. Thank you.
  24. 1 point
    It has been fixed on the newest version of the HTML5 chat.
  25. 1 point
    We have found out that this is related to a chrome pop-up setting. If you click on a link while linkvalidator setting is enabled, Chrome will show up the "pop-up" blocked message indicating that the linkvalidator page is blocked from being opened automtically. The problem is that linkvalidator is already being opened regardless. So if the user chooses "Always allow pop-up", clicking any links will open the page twice henceforward. That being said, we do not think this is a bug related to the HTML5 chat. This rather seems to be a Chrome Browser issue, especially since no other browser is doing this behavior.
  26. 1 point
    Both (hearts) and (switch) should be playable now.
  27. 1 point
    This should now be fixed (pending one more upload to fix default en to default international).
  28. 1 point
    Yeah, other users are experiencing this too. LaFleur has told it's due a websocket and they are trying to fix it.
  29. 1 point
    I've tried something. Please let me know if the problem persists. @LaFleur @Leandro @SLOom @6
  30. 1 point
    Ah this bug on Firefox! I see. But we are already aware about this bug already! Thank you for reporting.
  31. 1 point
    Thank you for reporting. We have reported already this bug on our board. Info about this bug: Extras pawns are not implemented in private chats yet.
  32. 1 point
    Changed Priority to Priority: Trivial This a known fact and will be implemented in the future. Thanks.
  33. 1 point
    Update: This is happening on Windows as well by now. It could be caused by a Google Chrome / Chromium update which was rolled out slowly
  34. 1 point
  35. 1 point
    Changed Status to Fixed Fixed on an upcoming release.
  36. 1 point
    Hello, We are fully aware with the issue on Edge and the homepage. I'll mail the administrators to take a look at that. Other issues are already reported on our bugs board. We do not have official dates for when it will be fixed. Thank you.
  37. 1 point
    Can we get another update? These games are some of the best multiplayer games offered on flash and can be beneficial for hosting game events while HTML5 is still being developed. We need something that can entertain us in the meantime. @Admin
  38. 1 point
    We will need more evidence or details before we’re able to proceed! Thinks such as event logs could be useful, perhaps. Are you sure the tempmodded users weren’t kicked/dunced/yellowcarded etc ?
  39. 0 points
    Changed Status to Fixed
  40. 0 points
    Paysefcard is now fixed. Please test @Bau
  41. 0 points
    Thanks for reporting @Bau, we will fix this shortly.
  42. 0 points
    It didn't happen again. This can be closed.
  43. 0 points
    Any news about this ? Did it happen again? Or can we close?
  44. 0 points
    Didn't know he reported this. I never followed up on him asking if this was intentional or not. @xLaming
  45. 0 points
    @LaFleur I don’t remember them all but xat.com/Kaay is one. @Kaay
  46. 0 points
  47. 0 points
    This is still happening and is very very very annoying also happens when replying to a status
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.