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. Thank you for reporting this issue. We are already aware of it. The smiley is currently broken due to ''_''. You'll be notified when fixed.
    1 point
  22. 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.
    1 point
  23. 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.
    1 point
  24. Both (hearts) and (switch) should be playable now.
    1 point
  25. Update: This is happening on Windows as well by now. It could be caused by a Google Chrome / Chromium update which was rolled out slowly
    1 point
  26. Please clear your cache and give me an update if it happens again @LaFleur. After clearing my cache, the editor loads considerably faster for me.
    1 point
  27. Yes, It is working perfectly, still being replaced the weird char, but not deleting anymore.
    1 point
  28. Should it show like that instead ? @Angelo
    1 point
  29. Changed Status to Status: Fixed
    1 point
  30. Changed Status to Status: Fixed Fixed on update 4.3. Confirmed.
    1 point
  31. This is a known bug and away is not fully added/working. This is the same for typing. Thank you for reporting but we can't consider this bug as high priority at the moment.
    1 point
  32. Arabic, Estonian, Filipino, French, German, Hungarian, Italian, Portuguese, Romanian, Spanish, Thai and Turkish, redirects to Help chat too.
    1 point
  33. 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!
    1 point
  34. Thanks for the report @Stif. We're already aware of this issue and this will be fixed at some point. It is considered low priority for now.
    1 point
  35. What the user reported was fixed.
    1 point
  36. Yes, this is an issue. I'll forward this and let you know as soon as this is fixed. Ty.
    1 point
  37. This is a confirmed bug. It happens also with the number "0". Thank you for report. @Admin
    1 point
  38. 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
  39. 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.
    1 point
  40. This issue has been fixed. Thank you ^^
    1 point
  41. 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); } }
    1 point
  42. I've looked into it but i can not confirm/reproduce this issue (tried with opera, chrome and edge). Is flash allowed for the ticket page for the users who have it?
    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.