Re: Intent to implement: Cookie SameSite=lax by default and SameSite=none only if secure

2019-11-02 Thread 001m . gots
Asi O es mejor + A cookie associated with a resource at http://trc.taboola.com/ was set with `SameSite=None` but without `Secure`. A future release of Chrome will only deliver cookies marked `SameSite=None` if they are also marked `Secure`. You can review cookies in developer tools under Applica

Re: Intent to implement: Cookie SameSite=lax by default and SameSite=none only if secure

2019-11-02 Thread 001m . gots
El jueves, 23 de mayo de 2019, 4:34:14 (UTC-4), Andrea Marchesini escribió: > Link to the proposal: > https://tools.ietf.org/html/draft-west-cookie-incrementalism-00 > > Summary: > "1. Treat the lack of an explicit "SameSite" attribute as >"SameSite=Lax". That is, the "Set-Cookie" valu

Re: Intent to ship: Promise.allSettled

2019-11-02 Thread Paolo Amadini
On 11/1/2019 2:42 PM, Jan-Ivar Bruaroey wrote: My original point was that the semantics of Promise.allSettled, which are "keep waiting for the lot even if some async operations fail", did not deserve its own standard name in the JS language, because of A) how rarely this is actually what you w

Re: Upcoming changes to hg.mozilla.org access

2019-11-02 Thread Andreas Tolfsen
Also sprach Kim Moir: > On Nov 14, 2019, we intend to change the permissions associated > with Level 3 access to revoke direct push access to hg.mozilla.org > on mozilla-inbound, Several modules have a policy that changes to documentation, e.g. for https://firefox-source-docs.mozilla.org/, can be