<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Implement Web Application Manifest"
href="https://bugs.webkit.org/show_bug.cgi?id=158205">158205</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Implement Web Application Manifest
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Nightly Build
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>Platform
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>addyo@chromium.org
</td>
</tr></table>
<p>
<div>
<pre>This specification defines a JSON-based manifest, which provides developers with a centralized place to put metadata associated with a web application. This includes, but is not limited to, the web application's name, links to icons, as well as the preferred URL to open when the user launches the web application. The manifest also allows developers to declare a default orientation for their web application, as well as how the application is to be displayed by the user agent (e.g., in fullscreen).
Using this meta data, user agents can provide developers with means to create user experiences that are more comparable to that of a native application.
Specification: <a href="https://w3c.github.io/manifest/">https://w3c.github.io/manifest/</a>
Support in other browsers:
Chrome: implemented on desktop and Android
Firefox: Partially implemented in Firefox for Android)
Edge: public support
WebKit (specifically, Mobile Safari on iOS) has previously been a leader in allowing web developers greater customisation over the add to homescreen experience. This included the ability to setup a custom splashscreen, something that has broken in recent versions of mobile safari (per <a href="https://gist.github.com/tfausak/2222823#gistcomment-1730484">https://gist.github.com/tfausak/2222823#gistcomment-1730484</a>). Rather than focusing on older, non-standards track implementations I think there's great value in shifting to a standards-track application manifest as a source for this type of data. It would allow web developers to ensure a high-quality web app experience is delivered on iOS as well as other platforms supporting this feature.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>