Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668)

@marcoscaceres @mgiuca I note that the commit message in 22a0b1e138c31a06ca9b7a0b8d244fbbc298989a describes that change as "pre-work" for this issue.

Since the [algorithm for processing a manifest](https://w3c.github.io/manifest/#processing) still takes document URL as an input, should this issue not still be open?

I'm also curious what the next step would be for separating these out, since the current specification is very much dependent on a document URL.

Perhaps a version 2.0?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/668#issuecomment-2465261178
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/668/2465261178@github.com>

Received on Friday, 8 November 2024 16:50:38 UTC