Intent to ship: ETP strict mode shims for content-blocked resources (aka SmartBlock)

2021-02-23 Thread Thomas Wisniewski
As of Firefox 87, I intend to enable ETP shims by default on desktop and Android. ETP shims are work-arounds for website breakage which is caused by blocking specific scripts in ETP strict mode and private browsing mode (see the intent to prototype for more context). Shims for the following

Re: Intent to unship: Application Cache API

2021-02-23 Thread Valentin Gosu
I don't think so. On Tue, 23 Feb 2021 at 14:50, Jeff Muizelaar wrote: > > Is the list of sites that have enrolled in Chrome's reverse origin trial > public? > > -Jeff > > On Tue, Feb 23, 2021 at 7:11 AM Valentin Gosu wrote: > > > > The storage backing for Application Cache has been completely

Re: Intent to unship: Application Cache API

2021-02-23 Thread Jeff Muizelaar
Is the list of sites that have enrolled in Chrome's reverse origin trial public? -Jeff On Tue, Feb 23, 2021 at 7:11 AM Valentin Gosu wrote: > > The storage backing for Application Cache has been completely disabled > starting with Firefox 84 [1]. That means the current > window.applicationCache

Intent to unship: Application Cache API

2021-02-23 Thread Valentin Gosu
The storage backing for Application Cache has been completely disabled starting with Firefox 84 [1]. That means the current window.applicationCache object is not really useful and only exists for backward compatibility. The plan is to remove it. We intend to do this in two stages: First we

Re: Intent to prototype and ship: :user-valid and :user-invalid pseudo-classes.

2021-02-23 Thread Emilio Cobos Álvarez
On 2/23/21 09:24, Anne van Kesteren wrote: On Mon, Feb 22, 2021 at 2:59 PM Emilio Cobos Álvarez wrote: Let me know if you have any objections about this change, but I think having a prefixed pseudo-class for this is not a great state of affairs. This seems reasonable, but I think we should

Re: Intent to prototype and ship: :user-valid and :user-invalid pseudo-classes.

2021-02-23 Thread Emilio Cobos Álvarez
On 2/23/21 11:52, Xidorn Quan wrote: Please head up in CSS working group about this, and probably ask for a resolution on no objection for us to ship it, as this spec is still in draft. Hmm, is it? https://www.w3.org/TR/selectors-4/#user-pseudos has had :user-invalid for quite a while, and

Re: Intent to prototype and ship: :user-valid and :user-invalid pseudo-classes.

2021-02-23 Thread Xidorn Quan
On Tue, Feb 23, 2021, at 12:59 AM, Emilio Cobos Álvarez wrote: > Standard: https://drafts.csswg.org/selectors/#user-pseudos > > Other browsers: No signal from other vendors, though we've shipped this > functionality for quite a while and the CSS working group considers it > useful, see

Re: Intent to prototype and ship: :user-valid and :user-invalid pseudo-classes.

2021-02-23 Thread Anne van Kesteren
On Mon, Feb 22, 2021 at 2:59 PM Emilio Cobos Álvarez wrote: > Let me know if you have any objections about this change, but I think > having a prefixed pseudo-class for this is not a great state of affairs. This seems reasonable, but I think we should define the processing model for them in the