>
> Can we ask WebKit folks for a signal?

There's this bug <https://bugs.webkit.org/show_bug.cgi?id=231174> filed
against WebKit. I'm not aware of any other channels to get feedback.

On Thu, Oct 7, 2021 at 8:24 AM Yoav Weiss <yoavwe...@chromium.org> wrote:

>
>
> On Wed, Oct 6, 2021 at 10:22 PM Mike Taylor <miketa...@chromium.org>
> wrote:
>
>> On 10/5/21 6:50 AM, Rayan Kanso wrote:
>>
>> Contact emails rayank...@chromium.org, jakearchib...@chromium.org
>>
>> Specification https://fetch.spec.whatwg.org/
>> Diff: https://github.com/whatwg/fetch/pull/1312
>>
>> Summary
>>
>> Allows requests with simple range headers to go through without
>> preflight. CORS requests will be able to use the Range header in limited
>> ways (having only one valid range) without triggering a preflight.
>>
>> Blink component Blink>SecurityFeature>CORS
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ESecurityFeature%3ECORS>
>>
>> TAG review Not applicable - this is a simple amendment that does not
>> require an architectural review.
>>
>> Risks
>>
>> Interoperability and Compatibility
>> Gecko: Positive
>> <https://github.com/whatwg/fetch/issues/1310#issuecomment-927842498>
>>
>>
> Also, this doesn't count as a positive Mozilla position. I agree it's a
> good signal, and am not sure we need to file for an official position
> though.
>
>>
>>
>> WebKit: No signal
>>
>> Can we ask WebKit folks for a signal?
>>
>>
>> Web developers: No signal
>>
>>
>> Debuggability N/A
>>
>> Is this feature fully tested by web-platform-tests
>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>
>> ? https://github.com/web-platform-tests/wpt/pull/31058
>>
>> Flag name N/A
>>
>> Requires code in //chrome? False
>>
>> Launch bug https://bugs.chromium.org/p/chromium/issues/detail?id=1255711
>>
>> Estimated milestones
>>
>> M96/M97
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5652396366626816
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAe2mZ1N0Oqz%3DVgEm%2BFQdJBVJCQbG%3Dv-6aO_JqRzm-9uBeQ%3Dfg%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAe2mZ1N0Oqz%3DVgEm%2BFQdJBVJCQbG%3Dv-6aO_JqRzm-9uBeQ%3Dfg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/83e97b2b-cad3-07fc-747e-24a786b89ccd%40chromium.org
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/83e97b2b-cad3-07fc-747e-24a786b89ccd%40chromium.org?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAe2mZ18AoZ7H3NxqX4Un-9nLm_p39AnvTW4d%2Bo4Aq47CF8mqg%40mail.gmail.com.

Reply via email to