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
    Yeah, it requires refreshing to display updated data. It's supposed to work like that. If you don't want to refresh the whole tab, right-click the banner and select "Reload Frame".
  24. 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.
  25. 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.
  26. 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.
  27. 1 point
    Thank you for reporting. This has been forwarded.
  28. 1 point
    @xLaming what is this about? happens on new web too?
  29. 1 point
    Yeah, other users are experiencing this too. LaFleur has told it's due a websocket and they are trying to fix it.
  30. 1 point
    I've tried something. Please let me know if the problem persists. @LaFleur @Leandro @SLOom @6
  31. 1 point
    Changed Status to Fixed Fixed on an upcoming release.
  32. 1 point
    Hello, We have already this bug listed on the board. (Was previously reported by Leandro to me.) Thank you for reporting.
  33. 1 point
    I apologize for my mistake. I will be more careful next time
  34. 1 point
    Changed Status to Fixed
  35. 1 point
    Yes, It is working perfectly, still being replaced the weird char, but not deleting anymore.
  36. 1 point
    The cool smiley is fixed on new chat version.
  37. 1 point
    @Phin Thanks for reporting. I took a look at the mentioned issues and this is the outcome: 1. I think the first issue is related to slow loading of un-cached images, thus if you go to someone's private chat whose pcback wasn't loaded/cached yet, it won't show it immediately, and so when you go back to the chat it'll load the pcback-image as chat background, due to the delay. You can also spot the same issue in the HTML5 chat. Having said that, if this gets fixed on HTML5, and if the fix gets applied to Mobile, this issue should be resolved. 2. I can't reproduce it, you may wanna re-check it when a new version is available for you (the public). My version is 1.12.0.
  38. 1 point
    Nope, it may work fine, just the underline is used there as separator, Including you can try using like rgb--- or rgb+++ both will work fine (colors). Fix: Smiley should be renamed for (o-o) instead of (o_o) @Admin
  39. 1 point
    Should it show like that instead ? @Angelo
  40. 1 point
    Changed Status to Status: Fixed
  41. 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.
  42. 1 point
    This usually happens when you are automatically logged out of xat, or you click here and click logout. Example: https://transfer.sh/XbBVj/2018-04-12_19-40-08.mp4 (Couldn't figure out how to use imgur for gifs so this will do for now. )
  43. 1 point
    Happens with the reactions NO and MEH: (viewing from my account) Viewing from another account:
  44. 1 point
  45. 1 point
    Changed Status to Status: Fixed
  46. 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.
  47. 1 point
    This issue has been fixed for the future release.
  48. 1 point
    Changed Status to Status: Fixed This issue has been fixed with the latest chat version (debug chats for now).
  49. 1 point
    Fix: File: xkiss.as Function: WhoIs replace it with this private static function WhoIs(_arg_1:*=0){ if (todo.w_userno != todo.uKiss) { main.openDialog(2, todo.uKiss); } }
  • 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.