The only thing I know baku reported on the spec during implementation is that the reload order isn't defined: https://github.com/w3c/webappsec-clear-site-data/issues/48 -Dan Veditz On Fri, Jul 20, 2018 at 2:36 PM, Mike West <mike@mikewest.org> wrote: > That’s great to hear! I imagine y’all found bugs in the spec along the > way. Anything in particular that needs to change? > > -mike > > On Fri 20. Jul 2018 at 22:55, Daniel Veditz <dveditz@mozilla.com> wrote: > >> Mozilla plans to ship support for the Clear Site Data spec in Firefox 63 >> which goes to beta early September and ships in October. This is testable >> now in Nightly with a pref flip and should default enabled by next week. >> >> -Dan Veditz >> >> ---------- Forwarded message ---------- >> From: Andrea Marchesini <amarchesini@mozilla.com> >> Date: Fri, Jul 20, 2018 at 1:01 AM >> Subject: Intent to ship: Clear-Site-Data header >> To: dev-platform <dev-platform@lists.mozilla.org> >> >> >> I intend to turn Clear-Site-Data header on by default in 63. The last >> remaining dependency bug is going to land today; we pass all the WPTs. >> >> It has been developed behind the dom.clearSiteData.enabled preference. >> >> Chrome has this feature enabled since 06-2017. >> >> Bug to turn on by default: bug 1470111. >> >> Spec: https://w3c.github.io/webappsec-clear-site-data/ >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform >> >>
Received on Friday, 20 July 2018 22:01:18 UTC