Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)

dmurph left a comment (w3c/manifest#1218)

Manifest spec eu/us meeting notes:

  * Dan: having a bool that could be an enum often is something I regret when coding, as in the future for established APIs this hinders adding new values, and often the 'enum-label: enum value' is a more readable description than a bool.  
  * Dan  
    * Don't care THAT much. Dan has slight preference for enum and no bool, unless.. maybe 'installed'  
    * application-context with an enum feels the most future proof.  
  * Christian  
    * agreed on enums over bools can be nice  
    * also don't care that much  
    * why not installed?  
  * explanation from [explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ApplicationContextMediaFeature/explainer.md#alternatives-considered)  
    * The name installed suggests a statement about global installation state. A developer might reasonably expect (installed) to be true if the app is installed on the device, even when viewed in a browser tab. In reality, the feature only matches when running *inside* an installed app window. The name application-context makes this distinction explicit, and describes the current context, not a global property.  
    * Dan: seems reasonable?  
      * this also means that it is guaranteed to be interop, as apple didn't want to reveal installed in the browser tab, and chrome.. could? but we likely want to align, and teh getInstalledRelatedApps() api is still a way to detect if the app is installed.  
    * Christian \- sounds good

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1218#issuecomment-4683327160
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1218/c4683327160@github.com>