Ryan Sleevi
belum dibaca,11 Jul 2017, 10.58.3411/07/17Login untuk membalas kepada penulis
Login untuk meneruskan
Anda tidak memiliki izin untuk menghapus pesan dalam grup ini
Login untuk melaporkan pesan
Untuk melihat pesan asli, alamat email grup ini tidak boleh berstatus anonim atau Anda harus memiliki izin untuk melihat alamat email anggota.
kepadaMike West, Eric Roman, blin...@chromium.org, Ryan Sleevi, Rick Byers, Malte Ubl, PhistucK, Andy Paicu, Chris Harrelson, Dimitri Glazkov, Philip Jägenstedt, Owen Campbell-Moore, Jochen Eisinger, Tim Taubert
Mozilla bug for restricting to [SecureContext] is
https://bugzilla.mozilla.org/show_bug.cgi?id=1333140
It was initially gated on bindings issues, and then they wanted to
measure compat issues. I believe, like you mentioned, an uptick
related to AMP was noticed. Tim Taubert was last looking into the
measurements to assess impact. Note that Mike's proposal is to
properly implement the ancestry check, while Mozilla does not yet
restrict it at all. Mozilla's measurements about secure vs non-secure
does, however, implement the ancestry check - so the actual impact is
most likely aligned somewhere around those Chrome numbers.
>>>>>>>>> send an email to
blink-dev+...@chromium.org.
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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+...@chromium.org.
>>>>>> an email to
blink-dev+...@chromium.org.