I’m not a web developer expert, but the people I know who are always tell me the same thing.
Detect features, not browsers.
So if you guys are doing Chrome exclusive things, and then later add other browsers (probably with their own specific code and APIs), how will this not turn into a unmaintainable mess?
Detecting features rather than browsers is generally good advice for web development. However, in the case of push notifications, that’s not possible.
Push notifications are a new feature and still being developed by the browser vendors, and they are each doing it in slightly different ways. In the case of Chrome, you need to register an application with Google to handle the notification relaying, so there are actually browser specific requirements. The supported feature set also varies from browser to browser. So we’re supporting this feature browser by browser, starting with Chrome as it has the largest usage amongst our users.
Is it even possible for a mobile browser to send notifications? I see Discourse doesn’t let you enable notifications when you’re on Mobile Safari or Chrome.
Idk what I am getting, but I use the android-version of chrome and I get notifications on my phone, if you are not testing it. And it redirects me to chrome when I click it. Edit:
Good chance I will be reactivating group notifications via Merely’s group enhancer and remove Roblox+ as I don’t use any feature in it enough to keep it.
I don’t use R+, but it seems to be less useful haha.
All ROBLOX needs now is Read-Only API that will let you check limited / full inventorys for players and be able to get their total RAP without having to use R+ API for it or use json tables from rbx.trade (my hope)
Can confirm this is why the bug occurs. Just figured it out for myself and it turns out I was ninja’d 2 hours ago
Although, I’ve never actually had this bug, but I was aware the inbox notification didn’t disappear after opening the message directly from the chrome notification dialog.