Jump to content

Leaderboard

Popular Content

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

  1. i reported a fix for this ages ago Fix (just incase they forgot):
    4 points
  2. 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."
    3 points
  3. Fix was submitted earlier today and is applied whenever @Admins get to it. Done.
    3 points
  4. will fix at next release
    3 points
  5. 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")"
    3 points
  6. 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
    3 points
  7. IPS confirmed there was an issue and escalated it to higher departments.
    2 points
  8. 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.
    2 points
  9. 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 points
  10. 2 points
  11. @Blacky The issue has been fixed now. Thank you for reporting.
    2 points
  12. 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 ?
    2 points
  13. 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.
    2 points
  14. 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.
    2 points
  15. Thank you for reporting. This bug seems to appear also on HTML5. I will post when this bug is fixed.
    2 points
  16. Changed Status to Status: Fixed
    2 points
  17. Changed Status to Status: Fixed Managed to reproduce on 1920x1080 screen resolution.
    2 points
  18. If i remember correctly, this isn't a bug. It was made like that due the lack of activity that xat Ayuda has.
    2 points
  19. 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)); }
    2 points
  20. 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"")"
    2 points
  21. Yeah, there was a problem. It looks like that https://prnt.sc/ut2f7y
    1 point
  22. Confirmed bug. Thank you for reporting.
    1 point
  23. It should really show an error instead of changing to an unexpected value not chosen by the user.
    1 point
  24. Addressing. In the meantime replace the script tags with something like <scr>.
    1 point
  25. This issue is already known, no need to re-report it.
    1 point
  26. Has been fixed now. @HelperNate
    1 point
  27. Thank you for reporting. This has been forwarded.
    1 point
  28. Changed Priority to Priority: Trivial This a known fact and will be implemented in the future. Thanks.
    1 point
  29. https://forum.xat.com/topic/7933-iphone-app-testflight-public-link/?do=findComment&amp;comment=100038
    1 point
  30. Seems to still happen to me. Browser: Chrome I have no error when clicking the text editor (to load it). I just had this error previously as on the screenshot from LaFleur.
    1 point
  31. Yeah, it has been fixed.
    1 point
  32. Changed Status to Fixed Problem has been fixed. Hopefully. If the issue occurs again, private message me and I’ll re-open this.
    1 point
  33. It does not support underline because it is the separator
    1 point
  34. 1 point
  35. I refreshed 10 times the page but someone touched the forums, so imo it has been fixed. (like other issues listed)
    1 point
  36. This issue has been fixed. Clear cache for new chat version.
    1 point
  37. @Stif This issue is fixed with version 1.11.
    1 point
  38. 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.
    1 point
  39. Ah! I wrote an answer about that but I wasn't sure, so I'll re-write for you. Your issue is because the gifts app is reading a page which is "cached" so, the update will not show directly. You have to clear your cache to see it updated, unfortunately. We'll try in the future to avoid this issue for HTML5.
    1 point
  40. 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.
    1 point
  41. This is a confirmed bug. It happens also with the number "0". Thank you for report. @Admin
    1 point
  42. The reason this has occured is because there recently was an exploit that has now been fixed. The relogin is needed to update everyone's values with the new values that are generated that fixed the exploit. So just go to xat.com/login and you should be fine, otherwise do what is said above and clear cache / cookies.
    1 point
  43. What seems to be the cause of this login issue, I experienced this the other day after I updated my flash.
    1 point
  • 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.