Extensions Registry

This page documents standardized and proprietary extensions to the web manifest format.

If adding a new member, please provide the name, and brief description, and a link to either the specification or documentation the describes what the member does. If it's a enumerated member (i.e., one that takes discreet values), please briefly describe those values.

For example:

### The `moz_fruits` member
A Mozilla proprietary extension that allows your app to smell 
like either an "apple", "orange", or "banana". 
Information about the `moz_fruits` member can be found 
on [`moz_fruits` MDN page](https://developer.mozilla.org/moz_fruits).

Standardized extensions

These are extensions that are at least Working Drafts.

• App Information - Provides additional metadata related to how a web application may be presented in the context of a digital storefront, installation dialog, or other surfaces where this web application may be marketed or distributed.

Proprietary Extensions

These are vendor-specific extensions.

Google

gcm_sender_id member

A proprietary extension related to Google Cloud Messaging. More information may be found at: https://developers.google.com/cloud-messaging/gcm

gcm_user_visible_only member (DEPRECATED)

A proprietary extension related to Google Cloud Messaging. More information may be found at: https://www.chromestatus.com/feature/5778950739460096

Meta

ovr_package_name member

A proprietary extension in the Oculus VR browser. Specifies the Android package name associated with the app. Described at PWAs on Oculus Quest 2.

ovr_multi_tab_enabled member

A proprietary extension in the Oculus VR browser. Allows the PWA to be used in a multi-tab window. Described at PWAs on Oculus Quest 2.

Nothing specific to Oculus or VR. Appears to be serving the same role as the standards-track tabbed display mode proposal.

ovr_scope_extensions member

A proprietary extension in the Oculus VR browser. Allows additional URLs to be added to the manifest scope. Described at PWAs on Oculus Quest 2.

Nothing specific to Oculus or VR. Appears to be serving the same role as the standards-track scope extensions proposal.