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. IPS has confirmed there's an issue that will be fixed in a future maintenance release.
    1 point
  22. @Leandro oh, so you are talking about html5 not flash, my bad yes there are some issues that still have to be fixed, we're aware thanks
    1 point
  23. It will be fixed in a future update of the HTML5 chat.
    1 point
  24. Changed Status to Fixed
    1 point
  25. 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
  26. This was fixed on the new web registration. Thank you.
    1 point
  27. We have found out that this is related to a chrome pop-up setting. If you click on a link while linkvalidator setting is enabled, Chrome will show up the "pop-up" blocked message indicating that the linkvalidator page is blocked from being opened automtically. The problem is that linkvalidator is already being opened regardless. So if the user chooses "Always allow pop-up", clicking any links will open the page twice henceforward. That being said, we do not think this is a bug related to the HTML5 chat. This rather seems to be a Chrome Browser issue, especia
    1 point
  28. I've tried something. Please let me know if the problem persists. @LaFleur @Leandro @SLOom @6
    1 point
  29. Alright. Attempting to mail this issue to admins.
    1 point
  30. Hello, We are fully aware with the issue on Edge and the homepage. I'll mail the administrators to take a look at that. Other issues are already reported on our bugs board. We do not have official dates for when it will be fixed. Thank you.
    1 point
  31. Hello, We have already this bug listed on the board. (Was previously reported by Leandro to me.) Thank you for reporting.
    1 point
  32. 1 point
  33. 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
  34. 1 point
  35. 1 point
  36. 1 point
  37. As I said, would have worked with https://i.cubeupload.com Anyway, should be good now.
    1 point
  38. Changed Status to Status: Fixed
    1 point
  39. 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
  40. 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
  41. This is not a connection issue. You are asked to relogin on xat.com/login to update your account values according to Mike's comment since an exploit was recently found and fixed.
    1 point
  42. What seems to be the cause of this login issue, I experienced this the other day after I updated my flash.
    1 point
  43. Thanks for the report. We're already aware of this issue.
    1 point
  44. I checked and yeah, it doesn't redirect to ayuda. That's more because it hasn't been updated or even added. Confirmed bug
    1 point
  45. 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
  46. Pretty sure it's been like this since forever. It goes for anything you send, if it's the same exact message. I think this was added to stop a user trying to spam multiple people with the same message, link, etc.
    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.