W3C home > Mailing lists > Public > public-webappsec@w3.org > July 2017

Re: advance Referrer Policy?

From: Franziskus Kiefer <fkiefer@mozilla.com>
Date: Mon, 24 Jul 2017 10:29:07 +0200
Message-ID: <CADthy-+HcdjihiY+RKXoXA6BhqKKVUq6LBhPZM5TRMTBOaq93g@mail.gmail.com>
To: Emily Stark <estark@google.com>
Cc: Jochen Eisinger <eisinger@google.com>, Daniel Veditz <dveditz@mozilla.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>, Mike West <mkwst@google.com>
Firefox doesn't implement the CSS bits yet [1]. I'm not sure if this is
going to change any time soon.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1330487

On Sat, Jul 22, 2017 at 11:53 AM, Emily Stark <estark@google.com> wrote:

> Not sure -- Dan, do you know?
>
> On Fri, Jul 21, 2017 at 8:55 AM, Jochen Eisinger <eisinger@google.com>
> wrote:
>
>> Did Firefox implement the CSS specific bits meanwhile?
>>
>> On Fri, Jul 21, 2017 at 8:48 AM Emily Stark <estark@google.com> wrote:
>>
>>> Hi all,
>>>
>>> Chrome's implementation of Referrer Policy includes the three newest
>>> policy values in M61 (https://www.chromestatus.com/
>>> feature/5634117806850048). I believe this brings us to two
>>> interoperable implementations, covered by web-platform-tests
>>> <https://github.com/w3c/web-platform-tests/tree/master/referrer-policy>.
>>> I'm told this means it might be time for a CfC to transition to PR.
>>>
>>> Thoughts?
>>>
>>> Thanks,
>>> Emily
>>>
>>
>
Received on Monday, 24 July 2017 08:29:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:23 UTC