Leaderboard

i reported a fix for this ages ago Fix (just incase they forgot):

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."

Fix was submitted earlier today and is applied whenever @Admins get to it. Done.

will fix at next release

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")"

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

Changed Status to Fixed

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.

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.

Thank you for reporting. This bug seems to appear also on HTML5. I will post when this bug is fixed.

Changed Status to Status: Fixed

Changed Status to Status: Fixed Managed to reproduce on 1920x1080 screen resolution.

If i remember correctly, this isn't a bug. It was made like that due the lack of activity that xat Ayuda has.

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)); }

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"")"

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, especially since no other browser is doing this behavior.

I've tried something. Please let me know if the problem persists. @LaFleur @Leandro @SLOom @6

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.

Hello, We have already this bug listed on the board. (Was previously reported by Leandro to me.) Thank you for reporting.

Changed Status to Fixed

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.

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.

@Phin Thanks for reporting. I took a look at the mentioned issues and this is the outcome: 1. I think the first issue is related to slow loading of un-cached images, thus if you go to someone's private chat whose pcback wasn't loaded/cached yet, it won't show it immediately, and so when you go back to the chat it'll load the pcback-image as chat background, due to the delay. You can also spot the same issue in the HTML5 chat. Having said that, if this gets fixed on HTML5, and if the fix gets applied to Mobile, this issue should be resolved. 2. I can't reproduce it, you may wanna re-check it when a new version is available for you (the public). My version is 1.12.0.

It does not support underline because it is the separator

Being addressed.

Being addressed.

Changed Status to Fixed

Please download the latest version (1.11.2) at the Google Play Store and let me know if this issue still occurs. @Stif @Seven

This issue has been fixed. Clear cache for new chat version.

Changed Status to Status: Fixed Fixed in a future IPS update.

Being addressed.

No issue for me ? I refresh and was still working for me.

The scrollbar style has been temporary removed for now because of Firefox. It will be added back later in the near future.

@Stif This issue is fixed with version 1.11.

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.

Arabic, Estonian, Filipino, French, German, Hungarian, Italian, Portuguese, Romanian, Spanish, Thai and Turkish, redirects to Help chat too.

I don't quite get this. Can you please elaborate so I can understand?

Ah! I wrote an answer about that but I wasn't sure, so I'll re-write for you. Your issue is because the gifts app is reading a page which is "cached" so, the update will not show directly. You have to clear your cache to see it updated, unfortunately. We'll try in the future to avoid this issue for HTML5.

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.

What the user reported was fixed.

I've also experienced this before, and it wasn't fun! Usually happens when you send an amount of messages in a short period of time.

Since it doesn't happen anymore, i'll move it as fixed. Feel free to open a new post if needed.

This issue has been fixed for the future release.

I've encountered this as well, only happens in mobile with any page of the xat.wiki. Thanks for the report Blacky. @Andre

What seems to be the cause of this login issue, I experienced this the other day after I updated my flash.

Thanks for the report. We're already aware of this issue.

Changed Status to Status: Fixed This issue has been fixed with the latest chat version (debug chats for now).

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