Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 03/05/16 in Bug Comments

  1. 4 points
    i reported a fix for this ages ago Fix (just incase they forgot):
  2. 3 points
  3. 3 points
    I found the quickfix for Chrome users: 1. Go here - chrome://flags/#autoplay 2. select how it is selected in this printscreen: http://prntscr.com/jhqe68 or more simply "No user gesture required."
  4. 3 points
    Fix was submitted earlier today and is applied whenever @Admins get to it. Done.
  5. 3 points
    will fix at next release
  6. 3 points
    Issue is caused because after going away or invis you dont get sent the scroller message again so on <i it resets scroller to empty or Live Mode stuff Fix: File: network.as Function: myOnXML (towards the end of the if statement "if (e.nodeName == "i")"
  7. 3 points
    This is related to the Dunce power. Dunce allows a moderator to dunce another moderator, hence the "Kick" menu is available. Regarding the "Ban" menu, Dunce was originally placed on that menu and it seems like the administrators have forgotten to make this option unavailable when they moved it onto "Kick". Dunce power enabled Dunce power disabled
  8. 2 points
    The forum is now running on the latest release. If you're still experiencing this issue then link to the exact content and I'll address it.
  9. 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.
  10. 2 points
  11. 2 points
    @Blacky The issue has been fixed now. Thank you for reporting.
  12. 2 points
  13. 2 points
    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 ?
  14. 2 points
    Users have been complaining about this in help chats. I wouldn't classify its priority as "normal" since users find it very inconvenient that they can't browse chats in a specific language.
  15. 2 points
    A self note: you still can access the chat through the /go command. The bug has been transmitted to the administrators. I will post when it is fixed. Thank you for reporting.
  16. 2 points
  17. 2 points
    Thank you for reporting. This bug seems to appear also on HTML5. I will post when this bug is fixed.
  18. 2 points
    Changed Status to Status: Fixed
  19. 2 points
    Changed Status to Status: Fixed Managed to reproduce on 1920x1080 screen resolution.
  20. 2 points
    If i remember correctly, this isn't a bug. It was made like that due the lack of activity that xat Ayuda has.
  21. 2 points
    Fix: File: xmessage.as Function: Smilie Replace: with if (Code.match(/#wc/g).length > 0 && !todo.HasPowerA(todo.Users[uid].Powers, 410)) { Code = Code.replace(/#wc/g, "#WC"); smc.u = ("C" + xatlib.xInt(smc.u)); }
  22. 2 points
    Issue is caused by pools not being reset with <w packet (it doesnt get sent with chats that dont have pools) Before fix:After fix: Fix: (found problem with old fix added new one which is 100% now) File: network.as Function: myOnXML this goes at the end of the if statement "if (e.nodeName == "gp"")"
  23. 1 point
    It has been handled on our bugs board. You will be noticed when it is fixed. Thank you.
  24. 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
  25. 1 point
    This issue is already known, no need to re-report it.
  26. 1 point
    Thanks for reporting this, @DJFUNNY. We're already aware of this bug and it should be fixed in the next update.
  27. 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.
  28. 1 point
    Changed Status to Fixed
  29. 1 point
    @Kaay your chat is back now. Sorry for the inconveniences.
  30. 1 point
    It has been fixed on the newest version of the HTML5 chat.
  31. 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.
  32. 1 point
    Ah this bug on Firefox! I see. But we are already aware about this bug already! Thank you for reporting.
  33. 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.
  34. 1 point
  35. 1 point
    @Laming @Leandro Admin says he put a fix through for this. Can you please test soon and tell me what the results are? Chat still deleted? Thank you!
  36. 1 point
    I confirm, He mean, when you just add lots of invisible characters in the field "Description" and save the settings, the first time nothing happen, the second time you do this your chat will be deleted (redirected to xat.com/groups.php when you access it) https://xat.com/Lamingtons <- example of it.
  37. 1 point
    It doesn't only fail on mobile. Just because you've never experienced it, doesn't mean it doesn't happen. The way it works I believe is it uses mouse movements before the button is pressed to determine if it was checked by a human or by a robot (among other things like previous activity on Google sites while other things will cause it to default to the puzzle, for example using a VPN), and I'm not sure if this is adjusted to mobile tapping/scrolling so that's probably why.
  38. 1 point
  39. 1 point
    Changed Status to Status: Fixed
  40. 1 point
    I refreshed 10 times the page but someone touched the forums, so imo it has been fixed. (like other issues listed)
  41. 1 point
  42. 1 point
    This is fixed now. Please see this topic for more info: https://forum.xat.com/topic/5488-html5-chat-changelog/ If you find a new bug, please don't hesitate to let us know. Thank you.
  43. 1 point
    Admin has been notified. I'll notify you once i know more, it was probably a mistake. @ANGY It's fixed in next release. Thanks for reporting.
  44. 1 point
    At the moment, we can't do much since it's in beta and since we don't know if some users have this issue. This also means that it can be only on your side or not. But don't worry, the administrators are working on HTML5 and are working to fixing a lot of issues. I suggest you to try again later (when a new update is added) and then use the xat app during this time if you want to access xat chats. Thank you again and I hope that your problem is solved in the near future!
  45. 1 point
    I've also experienced this before, and it wasn't fun! Usually happens when you send an amount of messages in a short period of time.
  46. 1 point
    This issue has been fixed for the future release.
  47. 1 point
    What seems to be the cause of this login issue, I experienced this the other day after I updated my flash.
  48. 1 point
    I checked and yeah, it doesn't redirect to ayuda. That's more because it hasn't been updated or even added. Confirmed bug
  49. 1 point
    there you go baby cakes 10/10 perfect fix (pretty sure it works as far as i tested but that was a while ago) did it a month ago
  • 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.