Re: [w3c/manifest] Let user agents process a manifest for a document with no manifest link (PR #1255)

benfrancis left a comment (w3c/manifest#1255)

Hi @marcoscaceres, thanks for taking a stab at addressing #1168.

I see how this technically provides workaround for applying the manifest processing algorithm without a manifest, but what does that actually achieve? What is the use case?

If the use case is "installing" a website without a manifest, as I said in https://github.com/w3c/manifest/issues/1168#issuecomment-6233725262 all this achieves is that a user can create an app launcher with no name and no icon which opens in a browser tab. "Applying" the resulting default manifest (as shown below) to a browsing context surely just has no effect?

```json
{
  "dir": "auto",
  "start_url": "https://example.com/foo/bar.html#baz",
  "id": "https://example.com/foo/bar.html",
  "scope": "https://example.com/foo/"
  "display": "browser",
  "icons": [],
  "shortcuts": []
}
```

How is this "installing" a website in any practical way?

If creating an installed app from a website without a manifest is now a use case for the Manifest specification (which seems nonsensical to me, but OK), I think the only way to fulfil that requirement is to define HTML fallbacks for at least some of the manifest members. Otherwise surely it's just useless in practice?

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

Message ID: <w3c/manifest/pull/1255/c6314372596@github.com>