3 ms·
So if I'm understanding this correctly: Apple still refuse to implement this PushManager interface in Safari, but because they don't have a public bug tracker,
by boomskats 5y ago
So if I'm understanding this correctly: Apple still refuse to implement this PushManager interface in Safari, but because they don't have a public bug tracker, the WebKit Bugzilla is where the iOS PWA devs go to vent?
- toxik 5y agoIt was recently fixed in WebKit, so I guess that’s a step in the right direction? Though I doubt it’s happening, lots of ads and spam via push notifications.
- schappim 5y ago>> lots of ads and spam via push notifications Yup, including via apps distributed in the iOS App Store. Hell, even some of Apple's own apps do it!
- tehbeard 5y agoApple could absolutely gate this and a dozen other "problematic" APIs behind a user willfully installing a PWA, and with all the other trimmings they use for "user privacy". Hell, at this point, make us pay the apple Dev tax to be able to register to send notifications for a domain, make it so there's a reporting process or such with real consequences since you made us jump through so many hoops to register and prove we're real. But no, Safari lingers and lags, and rightly or wrongly, looks to be gimped in favour of the app store and the walled garden revenue from it.
- om2 5y agoI’m not sure how you came to your conclusion but it doesn’t seem justified by the info in this bug. It reflects Web Push being done in WebKit by Apple engineers (who use and pay attention to bugs.webkit.org). Apple doesn’t usually comment on when/if WebKit features will ship in Safari but Apple engineers don’t generally do stuff like this just for kicks.
- boomskats 5y agoThank you for the context. Makes much more sense now.