Skip to content
Novus Examples
webmanifest1.1 KB

Web app manifest with icon edge cases

A web app manifest whose icon array is built entirely from the awkward cases: a duplicate declaration, an entry with no sizes, sizes="any" on an SVG, a multi-size ICO, a .webp declared as image/png, a cross-origin icon and a 0x0 entry. For testing icon selection and validation logic.

Preview — first 50 lineswebmanifest
{
  "name": "Example Icon Edge Cases",
  "short_name": "IconEdge",
  "id": "/?src=icon-edges",
  "start_url": "/?src=icon-edges",
  "scope": "/",
  "display": "standalone",
  "background_color": "#0e1116",
  "theme_color": "#059669",
  "icons": [
    {
      "src": "/icons/icon-192.png",
      "sizes": "192x192",
      "type": "image/png"
    },
    {
      "src": "/icons/icon-192.png",
      "sizes": "192x192",
      "type": "image/png",
      "purpose": "any"
    },
    {
      "src": "/icons/icon-no-size.png",
      "type": "image/png"
    },
    {
      "src": "/icons/icon.svg",
      "sizes": "any",
      "type": "image/svg+xml"
    },
    {
      "src": "/icons/icon-multi.ico",
      "sizes": "16x16 32x32 48x48",
      "type": "image/x-icon"
    },
    {
      "src": "/icons/icon-512.webp",
      "sizes": "512x512",
      "type": "image/png"
    },
    {
      "src": "https://cdn.example.net/icons/icon-1024.png",
      "sizes": "1024x1024",
      "type": "image/png"
    },
    {
      "src": "/icons/icon-0x0.png",
      "sizes": "0x0",
      "type": "image/png"
    }
53 lines total — download for the full file.

Specifications

Seed
70400
Site
example.com (fictional)
Format
W3C Web App Manifest
Icons
8
Duplicate Declarations
1
Missing Sizes
1
Sizes Any
1
Type Mismatch
1
Cross Origin
1

Testing contract

Expected to recover
Scenario
Pick the icon an installer would use for a 192 px launcher slot.
Expected result
The duplicate 192x192 entries collapse to one candidate, the sizes-less and 0x0 entries are skipped, the .webp declared as image/png is flagged as a type mismatch, and the sizes="any" SVG stays eligible at every size.

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 icon edge cases” 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.

Generated by generation/web_p7.py. Free for any use, no attribution required — license.