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
    It should really show an error instead of changing to an unexpected value not chosen by the user.
  25. 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".
  26. 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.
  27. 1 point
  28. 1 point
  29. 1 point
    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.
  30. 1 point
    Can we get another update? These games are some of the best multiplayer games offered on flash and can be beneficial for hosting game events while HTML5 is still being developed. We need something that can entertain us in the meantime. @Admin
  31. 1 point
    I haven't tested it on HTML5 yet, but I've seen some people having the same trouble while on the mobile app, so yeah.
  32. 1 point
    The cool smiley is fixed on new chat version.
  33. 1 point
    It doesn't only fail on mobile. Just because you've never experienced it, doesn't mean it doesn't happen. The way it works I believe is it uses mouse movements before the button is pressed to determine if it was checked by a human or by a robot (among other things like previous activity on Google sites while other things will cause it to default to the puzzle, for example using a VPN), and I'm not sure if this is adjusted to mobile tapping/scrolling so that's probably why.
  34. 1 point
  35. 1 point
  36. 1 point
    As I said, would have worked with https://i.cubeupload.com Anyway, should be good now.
  37. 1 point
    Changed Status to Status: Fixed
  38. 1 point
    This issue has been fixed. Clear cache for new chat version.
  39. 1 point
    Apparently this itself is no longer an issue, however it does stick to the 4-user minimum. Being addressed.
  40. 1 point
    Changed Status to Status: Fixed
  41. 1 point
    What the user reported was fixed.
  42. 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.
  43. 1 point
    Yes, this is an issue. I'll forward this and let you know as soon as this is fixed. Ty.
  44. 1 point
    This issue has been fixed for the future release.
  45. 1 point
    I have discovered that the reputation system turned itself off. It has now been turned back on.
  46. 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
  47. 1 point
    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.
  48. 1 point
    The only way to make working export and import again would be to redo the photo_upload3.php file. (Maybe you can add it to your main post)
  49. 1 point
    Yeah, at least it's working when I'm not logged LOL I also saw a lot of users reporting the problem.
  • 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.