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
    IPS confirmed there was an issue and escalated it to higher departments.
  9. 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.
  10. 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.
  11. 2 points
  12. 2 points
    @Blacky The issue has been fixed now. Thank you for reporting.
  13. 2 points
  14. 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 ?
  15. 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.
  16. 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.
  17. 2 points
  18. 2 points
    Thank you for reporting. This bug seems to appear also on HTML5. I will post when this bug is fixed.
  19. 2 points
    Changed Status to Status: Fixed
  20. 2 points
    Changed Status to Status: Fixed Managed to reproduce on 1920x1080 screen resolution.
  21. 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.
  22. 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)); }
  23. 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"")"
  24. 1 point
    IPS has confirmed there's an issue that will be fixed in a future maintenance release.
  25. 1 point
    IPS admits that there's probably an issue, but they can't fix what they can't reproduce, so they expect step-by-step instructions. Every time I've tried - a notification was conveniently sent.. We're probably missing some parameters that those specific topic creators managed to meet. Asking them to explain in detail how they created their topic might be the way of successfully reproducing this and solving the issue once and for all.
  26. 1 point
    We're aware of those already and will improve in future. Thanks for reporting.
  27. 1 point
    Thanks for reporting this, @DJFUNNY. We're already aware of this bug and it should be fixed in the next update.
  28. 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.
  29. 1 point
  30. 1 point
    @xLaming what is this about? happens on new web too?
  31. 1 point
    It has been fixed on the newest version of the HTML5 chat.
  32. 1 point
    Alright. Attempting to mail this issue to admins.
  33. 1 point
    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.
  34. 1 point
    Clearly this is a bug as it’s supposed to work in the opposite way. Just because this is how it currently works, doesn’t mean it is correct. This be fixed so that (hat#e) is golden egg and (hat#e#colour) is the coloured egg, rather than (hat#e#colour) is golden and you have to disable allpowers to colour it, as this is clearly not how it is supposed to work.
  35. 1 point
  36. 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
  37. 1 point
    Please download the latest version (1.11.2) at the Google Play Store and let me know if this issue still occurs. @Stif @Seven
  38. 1 point
    Changed Status to Status: Fixed Will be fixed in an upcoming maintenance update.
  39. 1 point
    Changed Status to Status: Fixed
  40. 1 point
    This issue has been fixed. Clear cache for new chat version.
  41. 1 point
    Changed Status to Status: Fixed Fixed on update 4.3. Confirmed.
  42. 1 point
  43. 1 point
    If this list is missing smilies, please post. Thanks.
  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
    Are you aware that PCBACK was boosted recently to show your pcback if the user doesn't have one ? Source : xat.wiki/pcback Thread closed since there is no bug.
  46. 1 point
    You would do so after getting into the pc and then clicking at the user again - then you get to the user dialog. But i don't disagree, it's quite inconvenient.
  47. 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); } }
  48. 1 point
    This doesn't only happen with smiley and it is indeed a bug Fix: FIle: main.as Function: ProcessMessage //towards the bottom of the function
  • 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.