webmanifest1.2 KB

Web app manifest with file, protocol and launch handlers

A manifest registering the desktop-integration members: two file handlers with MIME and extension accept maps, a custom web+ protocol handler alongside mailto, a launch_handler client mode list, an Edge side-panel width and handle_links. For testing OS integration and manifest members a validator may not know.

Web assets JSON parsing Schema validation

Preview — first 50 lineswebmanifest

{
  "name": "Example Handlers",
  "short_name": "Handlers",
  "id": "/?src=handlers",
  "start_url": "/?src=handlers",
  "scope": "/",
  "display": "standalone",
  "display_override": [
    "window-controls-overlay",
    "standalone",
    "browser"
  ],
  "theme_color": "#059669",
  "icons": [
    {
      "src": "/icons/icon-192.png",
      "sizes": "192x192",
      "type": "image/png"
    },
    {
      "src": "/icons/icon-512.png",
      "sizes": "512x512",
      "type": "image/png"
    }
  ],
  "file_handlers": [
    {
      "action": "/open-csv",
      "accept": {
        "text/csv": [
          ".csv",
          ".tsv"
        ]
      },
      "launch_type": "single-client"
    },
    {
      "action": "/open-image",
      "accept": {
        "image/png": [
          ".png"
        ],
        "image/jpeg": [
          ".jpg",
          ".jpeg"
        ]
      }
    }
  ],
  "protocol_handlers": [

… 71 lines total — download for the full file.

Specifications

Seed: 70400
Site: example.com (fictional)
Format: W3C Web App Manifest
File Handlers: 2
Protocol Handlers: 2
Launch Handler: navigate-existing
Display Override: 3

Testing contract

Expected to pass

Scenario: Install the app and double-click a .csv file, then follow a web+example: link.
Expected result: The CSV opens through /open-csv in a single existing client, the protocol link expands %s into /handle?u=..., and unknown members like edge_side_panel are preserved rather than dropped.

What is a .webmanifest file?

A web app manifest (.webmanifest) is a JSON file that describes a Progressive Web App to the browser, declaring its name, icons, theme colors, start URL, and display mode. It enables installation to a device home screen and standalone launching. It is linked from HTML via a manifest link element.

How to use this file

Use an example webmanifest to test PWA installability, manifest JSON parsing, icon and display-mode handling, and browser or auditing tools like Lighthouse.

How to use this file for testing

“Web app manifest with file, protocol and launch handlers” is a deterministic Novus Examples fixture for Web assets, JSON parsing, Schema validation. Favicons, web app manifests, service workers, robots and sitemap files, Open Graph images, and .well-known resources — for testing web tooling, crawlers, PWA installers, and asset pipelines.

Documented properties for this file: seed 70400 · W3C Web App Manifest. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Web-platform fixtures are standards-compliant samples against fictional example.com data. Test crawlers, PWA installers and manifest validators, favicon/icon pipelines, service-worker registration, or .well-known parsers against the documented structure.