- From: Ben Francis <notifications@github.com>
- Date: Fri, 06 Nov 2026 04:34:02 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 6 November 2026 12:34:06 UTC
@benfrancis commented on this pull request.
> @@ -1878,6 +1878,18 @@ <h3>
</p>
</aside>
</section>
+ <section>
+ <h3>
+ Processing a document without a manifest link
+ </h3>
+ <p>
+ A [=document=] can also have no manifest link. The user agent MAY
+ still [=processing a manifest|process a manifest=] for that
+ [=document=], passing its [=Document/URL=] as both |document
+ URL:URL| and |manifest URL:URL|, an empty [=byte sequence=] as
My understanding of section [4.6.8.11](https://html.spec.whatwg.org/multipage/links.html#link-type-manifest) of the HTML specification is that if a page does not contain a `<link rel=manifest>` element then nothing happens at all. User agents only use "the first link element in tree order whose rel attribute contains the token manifest".
With no such `link`, there is no `el`, no fetch, no `response`, and therefore no document URL, manifest URL, bodyBytes or client for manifest processing.
--
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1255#discussion_r4492439995
You are receiving this because you are subscribed to this thread.
Message ID: <w3c/manifest/pull/1255/review/5800120422@github.com>
Received on Friday, 6 November 2026 12:34:06 UTC