We have a ticket for this issue in our system! We’ll get back to you when we have an update. 
5 Likes
are there any updates on this? bug is still present in player & studio :<
2 Likes
Just pinged the team for an update
2 Likes
I reported this almost a year ago prior and I am surprised there has not been a fix yet
3 Likes
I am also experiencing this issue as we cannot use :CaptureFocus() making it impossible to use a custom textbox.
1 Like
Update when? Been waiting 6 months and it’s still a bug.
1 Like
This taking so long is frustrating. The only workaround at the moment is to disable the input box and manually make your own script to do the capture on keybind press. You can use ChatInputBarConfiguration.TargetTextChannel:SendAsync() to achieve the same result. That makes it even more frustrating since this workaround should not be needed
2 Likes
@music_man1996 Has any work been actually done on this since the problem was reported? I feel like this is also a bigger issue now that Roblox is making chat regulation changes.
1 Like
If a fix cannot be found, would it be possible to let CaptureFocus be used instead?
1 Like
They even writed it is not able to set key when they were releasing new chat. It looks like they forgot about it.
1 Like
So confused as to why this hasn’t been a priority since they want to ensure that custom chat interfaces can work with TextChatService since LegacyChatService is being removed. I reported this a year ago and even that got a response from staff with 0 action done so far.
I do hope that this gets resolved
1 Like
Bump. This issue has not been fixed yet and the deadline for LegacyChat to be removed is crawling closer and closer
1 Like
The negligence to the TextChatService from engineers is honestly getting ridiculous at this level.
I can understand some recently reported issues, but I can’t understand what’s the problem dealing with the issues that last for year or more.
Will there be something done for once or not? I don’t want to bother using this buggy mess if there are no plans to fix any of its issues. I’m genuinely getting tired of waiting for any response. Might aswell completely disable chat and call it a day once its forced.
2 Likes
This issue still persists to this day, and it’s just really bizarre to me how it hasn’t been fixed, I can’t even use :CaptureFocus() on reserved TextBoxes so I just have to wait until they fix it.
I’m not about to make my own chat input box system just to fix a bug.
1 Like
Hello. I apologize for the delay. We are currently working to resolve this issue with TextChatService.
3 Likes
Hello. I wanted to give an update that this issue is still being worked on.
3 Likes
Hello everyone. Thank you guys for your patience. This issue was paused for a bit, but I’ll be picking it up again next week and will keep you all updated on progress.
5 Likes
Hello everyone! Thank you all for your patience. The hotkey should now behave as expected with custom text boxes. Please let me know if any of you experience any further issues.
3 Likes
This is still an issue if the Chat CoreGuiType is ever disabled and then re-enabled. Using slash doesn’t capture the focus. Same issue occurs if you ever set during runtime the TextChatService.ChatInputBarConfiguration.Enabled flag to false and then back to true. This is causing big problems with trying to prevent using chat temporarily during certain actions.
1 Like
This is a great workaround that I’ll be using, thanks!
1 Like