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
    Has been fixed now. @HelperNate
  24. 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.
  25. 1 point
    This was fixed on the new web registration. Thank you.
  26. 1 point
    This should now be fixed (pending one more upload to fix default en to default international).
  27. 1 point
    Yeah, other users are experiencing this too. LaFleur has told it's due a websocket and they are trying to fix it.
  28. 1 point
    I've tried something. Please let me know if the problem persists. @LaFleur @Leandro @SLOom @6
  29. 1 point
    Alright. Attempting to mail this issue to admins.
  30. 1 point
    The cool smiley is fixed on new chat version.
  31. 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.
  32. 1 point
    Changed Status to Fixed Problem has been fixed. Hopefully. If the issue occurs again, private message me and I’ll re-open this.
  33. 1 point
    It does not support underline because it is the separator
  34. 1 point
  35. 1 point
    Should it show like that instead ? @Angelo
  36. 1 point
    Changed Status to Status: Fixed
  37. 1 point
  38. 1 point
    Changed Status to Status: Fixed Fixed on update 4.3. Confirmed.
  39. 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.
  40. 1 point
    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.
  41. 1 point
  42. 1 point
    Changed Status to Status: Fixed
  43. 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.
  44. 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.
  45. 1 point
  46. 1 point
    This is a confirmed bug. It happens also with the number "0". Thank you for report. @Admin
  47. 1 point
    this is correct its so users can register quick and easy. They can set a nick to anything they want right away. They can chose a reg name later.
  48. 1 point
    For the second problem, this is something we can fix on the wiki. To be honest, we had much trouble with the Arabic translations. Send me a PM and we can try finding fixes for this.
  49. 1 point
    Yeah, at least it's working when I'm not logged LOL I also saw a lot of users reporting the problem.
  • 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.