- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 07 Nov 2024 04:32:35 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/784/2462121621@github.com>
Co-pilot has a good example:
To illustrate the problem mentioned in issue [#784](https://github.com/w3c/manifest/issues/784), here is an example web manifest and the URL at which the app is being installed from:
### Web Manifest (manifest.json)
```json
{
"name": "Example App",
"short_name": "Example",
"start_url": "/start.html",
"scope": "/why",
"display": "standalone",
"background_color": "#ffffff",
"theme_color": "#000000",
"icons": [
{
"src": "icon.png",
"sizes": "192x192",
"type": "image/png"
}
]
}
```
### Example Page Linking to the Manifest (https://stormy-pincushion.glitch.me)
```html
<!DOCTYPE html>
<html>
<head>
<title>Example App</title>
<link rel="manifest" href="manifest.json">
</head>
<body>
<h1>Welcome to the Example App</h1>
</body>
</html>
```
In this example, the page `https://stormy-pincushion.glitch.me` links to the manifest but the scope defined in the manifest is `/why`, which does not include the page itself. This situation illustrates the issue where Chrome currently allows installation but results in a page being displayed out of scope when the app is launched.
--
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/784#issuecomment-2462121621
You are receiving this because you are subscribed to this thread.
Message ID: <w3c/manifest/issues/784/2462121621@github.com>
Received on Thursday, 7 November 2024 12:32:39 UTC