- From: Karl Dubost <notifications@github.com>
- Date: Thu, 24 Jul 2025 19:16:47 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 25 July 2025 02:16:51 UTC
karlcow left a comment (w3c/manifest#1092) @raad-altaie About > Those compatibility concerns seem relatively minor, especially compared to the clear utility of being able to reliably detect if the app is running in a standalone window. This is unfortunately not minor. [See my previous comment](https://github.com/w3c/manifest/issues/1092#issuecomment-1616878673). This is always the issue when people using proxy detections (aka using a feature detection mechanism for trying to create device detection instead of the initial purpose of the feature). The issue with compatibility is that there are plenty of sites that will not get updated after the change, and will break on desktop computers. The victims will be **primarily the users**. It will put the burden of compatibility on browser implementers to fix it site per site (when/if the issue is reported). Firefox and Safari have mechanisms for this (Site Interventions for Firefox, Quirks for Safari), but this is still ugly and not perfect. Note that we all wish it was not the case. :( -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1092#issuecomment-3116149244 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1092/3116149244@github.com>
Received on Friday, 25 July 2025 02:16:51 UTC