Re: [w3c/manifest] The new definition of "installable web application" is inconsistent with the normative text of the specification (Issue #1168)

dmurph left a comment (w3c/manifest#1168)

@benfrancis wrote:
> 1. Specifying that inside this specification by defining a default manifest (and manifest URL) that can be applied when the website doesn't provide one, to turn a website into an installed app
> 2. Specifying "add to home/add to dock/create shortcut" for a website as a _separate_ mechanism to installing a web app, which re-uses some of the primitives like display modes and navigation scope, but defines a separate processing algorithm which doesn't require a manifest and manifest URL as input, to create an app from a website. ie. "create an app from a website" vs. "install an installable web app", which do already appear to be separate features in some browsers.

I believe, but I could be wrong, that if there isn't a manifest and no manifest url, the manifest processing algorithm does currently return a manifest with document url as start url, that without the filename as the scope, and that without fragments as the id. I believe that every processing algorithm that takes the manifest_url exists early in the empty-json case of no manifest, so it's not actually used.

I can definitely see trying to call this default cause out more explicitly, as it's not obvious.

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

Message ID: <w3c/manifest/issues/1168/6223047056@github.com>