Intent to implement & ship: Document.open/close/write/writeln

Hi everyone, *Summary*: I'm planning to move the open(), close(), write() and writeln() methods from HTMLDocument to Document to bring our implementation of this attribute on par with the HTML spec. *Bug*: https://bugzilla.mozilla.org/show_bug.cgi?id=1549560 *Link to standard*: https://html.spec.

Intent to implement & ship: Document.domain

Hi everyone, *Summary*: I'm planning to move the domain attribute from HTMLDocument to Document to bring our implementation of this attribute on par with the HTML spec. *Bug*: https://bugzilla.mozilla.org/show_bug.cgi?id=1467625 *Link to standard*: https://html.spec.whatwg.org/multipage/dom.html#

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

On Thu, May 23, 2019 at 10:53 AM Frederik Braun wrote: > Having read the proposal, I think it's a good mechanism for us to know > about websites that want third-party cookies and it seems less costly to > deploy for websites than Storage Access API. > > However, it seems this is Google's counter

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

Having read the proposal, I think it's a good mechanism for us to know about websites that want third-party cookies and it seems less costly to deploy for websites than Storage Access API. However, it seems this is Google's counter to Apple's Storage Access API, which we have also implemented in <

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

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" value "key=value" will produce a cookie equivalent to "key=value; SameSite=Lax".