Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)

I did a lot of thinking about CORS and here's what I came up with. Note that I've moved all the new text to its own section, "Processing a manifest without a document" which you can see in the preview. It now basically has prose that says "you SHOULD do CORS the way HTML does it".

Note that this is blocked on whatwg/html#9204 to export the definition of "CORS settings attribute credentials mode".

Also all the links to the link rel "`manifest`" value (both here, and existing already in the document) link to the wrong place due to w3c/respec#4435. Were it not for that, I'd have used `[^link/rel/manifest^]` more to directly link to the algorithm in HTML, but I can't get a direct link to that to work at the moment.

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

Message ID: <w3c/manifest/pull/1069/c1519418456@github.com>