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 your report, we will look into it and let you know once it's fixed. Changed Priority to Priority: High
    1 point
  22. 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
  23. It happens because you did a lot of actions in a row. It can be improved in the future to not "empty" the table but instead a message would be displayed. Manage power will be reworked in a near future to work better with this new main owner system.
    1 point
  24. 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
  25. @Kaay your chat is back now. Sorry for the inconveniences.
    1 point
  26. Ok, catch it. Seems that CSP is blocking something to be loaded correctly. When logging storage isn't being fully stored. What I did: I've logged-in using Google Chrome, copied all HTML5 data storage and replaced on Firefox, it worked fine. I've checked both and seems that Firefox's data isn't being stored "k3". Firefox shows "0", on Chrome shows correctly.
    1 point
  27. It has been fixed on the newest version of the HTML5 chat.
    1 point
  28. Alright. Attempting to mail this issue to admins.
    1 point
  29. 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.
    1 point
  30. I confirm, He mean, when you just add lots of invisible characters in the field "Description" and save the settings, the first time nothing happen, the second time you do this your chat will be deleted (redirected to xat.com/groups.php when you access it) https://xat.com/Lamingtons <- example of it.
    1 point
  31. 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
    1 point
  32. You can download Android version 1.11.2 at the Play Store now. This will fix this issue. @Encrypt If you find a new bug, please don't hesitate to let us know. Thank you.
    1 point
  33. Changed Status to Status: Fixed Will be fixed in an upcoming maintenance update.
    1 point
  34. 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.
    1 point
  35. If this list is missing smilies, please post. Thanks.
    1 point
  36. No issue for me ? I refresh and was still working for me.
    1 point
  37. Happens with the reactions NO and MEH: (viewing from my account) Viewing from another account:
    1 point
  38. 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
  39. I have discovered that the reputation system turned itself off. It has now been turned back on.
    1 point
  40. 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.
    1 point
  41. Thanks for the report. We're already aware of this issue.
    1 point
  42. Issue is caused by NaughtyStep & Dunce being treated as both a kick and ban function which they are not Fix: File: DialogActions.as Function: Constructor (aka DialogActions) Replace: with if (bKick != undefined || this.bDunce != undefined || this.bNaughty != undefined){ s = xconst.ST(79); Dia.kick = new xBut(Dia, (xx + 10), yy, 150, xatlib.NY(30), s, this.ViewprofileonKick, ((bKick || this.bDunce || this.bNaughty) ? 0 : (xBut.b_Grayed + xBut.b_NoPress))); Dia.kick.SetRoll(xconst.ST(80)); D
    1 point
  43. 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.
    1 point
  44. Yeah, at least it's working when I'm not logged LOL I also saw a lot of users reporting the problem.
    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.