[fxtf-drafts] [css-masking-1] Fetch doesn't define "potentially CORS-enabled fetch" (#358)

• From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
• Date: Fri, 19 Jul 2019 21:36:57 +0000
• To: public-fxtf-archive@w3.org
• Message-ID: <issues.opened-470568086-1563572216-sysbot+gh@w3.org>

foolip has just created a new issue for https://github.com/w3c/fxtf-drafts:

== [css-masking-1] Fetch doesn't define "potentially CORS-enabled fetch" ==
https://drafts.fxtf.org/css-masking/#priv-sec says:

> User agents must use the potentially CORS-enabled fetch method defined by the [FETCH] specification for all <mask-source>, <clip-source> and <image> values on the mask-image, mask-border-source and clip-path properties. When fetching, user agents must use “Anonymous” mode, set the referrer source to the stylesheet’s URL and set the origin to the URL of the containing document. If this results in network errors, the effect is as if the value none had been specified.

However, Fetch doesn't define "potentially CORS-enabled fetch" and mentions it only in https://fetch.spec.whatwg.org/#goals as having once been in HTML.

Perhaps @annevk can suggest what to say instead.


Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/358 using your GitHub account

Received on Friday, 19 July 2019 21:36:59 UTC