> However, as I said, adding a simple confirmation prompt would be plenty enough.
That would be enough for you. That is apparently not enough for Apple, and you can tell that isn’t enough for Apple by their actions because despite the fact that there were less expensive and time consuming ways they could have complied with the whole rest of the DMA, the only feature regression they’ve had is PWA support in the iPhone version of Safari.
> By your logic that PWAs are unsecure
That is not what I said. Here’s what I actually said not that long ago:
> Apple can make security guarantees about their own rendering engine that they can’t for any other rendering engine.
> It’s not about what PWAs are like in Safari, it’s about what they’re like in third-party browsers that have to by law be allowed to do whatever Safari can do with their own fully enabled rendering engines.
That would be enough for you. That is apparently not enough for Apple, and you can tell that isn’t enough for Apple by their actions because despite the fact that there were less expensive and time consuming ways they could have complied with the whole rest of the DMA, the only feature regression they’ve had is PWA support in the iPhone version of Safari.
> By your logic that PWAs are unsecure
That is not what I said. Here’s what I actually said not that long ago:
> Apple can make security guarantees about their own rendering engine that they can’t for any other rendering engine.
> It’s not about what PWAs are like in Safari, it’s about what they’re like in third-party browsers that have to by law be allowed to do whatever Safari can do with their own fully enabled rendering engines.