Re: Intent to ship: Make elements always unvisited.

2019-08-09 Thread Anne van Kesteren
On Thu, Aug 8, 2019 at 8:39 PM Emilio Cobos Álvarez wrote: > Standard: https://drafts.csswg.org/selectors-4/#location (though note > https://github.com/w3c/csswg-drafts/issues/3817). So the real standard for this is https://html.spec.whatwg.org/#pseudo-classes as CSS tries to be host-agnostic

Re: Intent to ship: Make elements always unvisited.

2019-08-09 Thread Emilio Cobos Álvarez
On 8/9/19 1:29 PM, Anne van Kesteren wrote: On Thu, Aug 8, 2019 at 8:39 PM Emilio Cobos Álvarez wrote: Standard: https://drafts.csswg.org/selectors-4/#location (though note https://github.com/w3c/csswg-drafts/issues/3817). So the real standard for this is

Intent to ship: restrict access to request notification permissions from cross-origin iframes

2019-08-09 Thread Ehsan Akhgari
Hi everyone, We currently allow cross-origin iframes to request notification permissions. This is problematic because we'd like to move to a model where permissions are only requested for the top-level document’s origin in order to show non-address-bar origins as little to the user as possible.

Fission Newsletter #2

2019-08-09 Thread Nika Layzell
Hey all! It's been a while (7 months!) since the first Fission newsletter, but we've made some exciting progress we'd love to tell you about! Enabling Fission on Nightly It's now possible to turn on Fission in nightly builds of Firefox by setting fission.autostart pref to true. Fission can also

Re: Fission Newsletter #2

2019-08-09 Thread Nika Layzell
Looks like gmail chewed up the formatting :-S Published gdocs link: https://docs.google.com/document/d/e/2PACX-1vTuGpZNthNxk0OYRyBjiHpaKnyKdmb9AompceuncvFmjeXB0bfk-L_LSlQmRaqiqx8vKif-LzdnE2F8/pub On Fri, Aug 9, 2019 at 1:33 PM Nika Layzell wrote: > Hey all! > > It's been a while (7 months!)

Re: Fission Newsletter #2

2019-08-09 Thread Alexis Beingessner
Is dogfoodability at all platform-specific for fission? i.e. is windows the only platform that is really actively developed/maintained? (as would make sense at this stage) More concretely, I was under the impression that fission had webrender as a dependency, is that mandatory? Is it actually

Re: Fission Newsletter #2

2019-08-09 Thread Nika Layzell
On Fri, Aug 9, 2019 at 1:55 PM Alexis Beingessner wrote: > Is dogfoodability at all platform-specific for fission? i.e. is windows > the only platform that is really actively developed/maintained? (as would > make sense at this stage) > The platform shouldn't have much impact, as we're

Re: Fission Newsletter #2

2019-08-09 Thread Bobby Holley
On Fri, Aug 9, 2019 at 11:11 AM Nika Layzell wrote: > On Fri, Aug 9, 2019 at 1:55 PM Alexis Beingessner > > wrote: > > > Is dogfoodability at all platform-specific for fission? i.e. is windows > > the only platform that is really actively developed/maintained? (as would > > make sense at this

Re: Intent to ship: restrict access to request notification permissions from cross-origin iframes

2019-08-09 Thread Martin Thomson
This is a great move for improving transparency and accountability of sites. Good work to all those who helped get us this far. On Sat, 10 Aug. 2019, 01:02 Ehsan Akhgari, wrote: > Hi everyone, > > We currently allow cross-origin iframes to request notification > permissions. This is

Re: Fission Newsletter #2

2019-08-09 Thread Kris Maglione
On Fri, Aug 09, 2019 at 01:33:31PM -0400, Nika Layzell wrote: Tests which do not currently successfully pass are marked as fail-if = Fission or skip-if = Fission. To be slightly pedantic, they're marked as `fail-if = fission` or `skip-if = fission`. mozinfo expression matching should be case