This post was flagged by the community and is temporarily hidden.
3 Likes
I’m confused, is this a ROBLOX issue, or a BTRoblox issue?
2 Likes
A few things here:
- This engineer doesn’t work on this feature so they won’t be able to help. I know they’ve been really helpful with helping maintain functionality of critical extensions in the past, though, so I understand why you mentioned them
- This isn’t a Roblox bug, it’s just engineers being inconsiderate in their implementation of these changes. I already reported this and sadly, engineers responsible for this update don’t seem to care. They told me to ask the extension developers to fix it. See the response here on issue #2:
I guess it just depends on whether or not they can be bothered spending the time to maintain backwards compatibility with extensions, and sadly this doesn’t seem to be the case in this scenario. It’s disappointing but not much we can do other than ask the extension developers themselves to fix it. The BTRoblox engineer hasn’t been active at all recently and hence I doubt this will be fixed for a while, so right now we are being left without a solution from either party.
6 Likes
This is not a Roblox issue.
This is a 3rd party browser extension that is not endorsed by Roblox.
4 Likes
@catinpsyop @King_GamingRobloxYT Despite being a third-party extension and not officially made by the platform, there were times that it impacted the UI/UX, leading to a report and it was fixed. If you two do some research, I’m sure you all can find it!
As of right now, this case might end according to Roman’s response, which is sad, but, maybe in the distant future, things will be better.
@bvetterdays I marked your reply above as a “Solution” to be closed by engineers.
Thank you all for participating in this post. Have a nice day!
1 Like