Re: [w3c/manifest] Manifest id should strip fragment at parse time (Issue #1121)

Note that there is precedent for this: #793 was basically exactly the same issue with `scope`.

Prior to 2019, "scope" included the query and fragment, but the scope matching algorithm was expected to ignore those. This effectively meant that "scope" did not include the query and fragment, but the "processed manifest" version of scope did include those. We successfully changed it to strip query and fragment at parse time, and remove the check from the scope matching algorithm.

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

Message ID: <w3c/manifest/issues/1121/2095189293@github.com>