Re: Intent to ship: Make elements always unvisited.

[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 (somewhat). It seems okay to me to get rid of this as
the  feature set always mismatched that of  and  a bit
and practically nobody would display a  anyway. Would you file
an issue against HTML to make it so?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to ship: Make elements always unvisited.

[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
https://html.spec.whatwg.org/#pseudo-classes as CSS tries to be
host-agnostic (somewhat). It seems okay to me to get rid of this as
the  feature set always mismatched that of  and  a bit
and practically nobody would display a  anyway. Would you file
an issue against HTML to make it so?


So the spec says that it should always match either :link or :visited, 
and that's still true with my patch (which just never makes it match 
:visited). I filed an issue about having interop / never make them 
navigate away from the page, probably:


 https://github.com/whatwg/html/issues/4831

And this to consider whether almost all MathML elements should really be 
links:


  https://github.com/mathml-refresh/mathml/issues/125

(Because they are now).

 -- Emilio


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

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

[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.
Therefore, in Firefox 70 I plan to land a change in bug 1560741[1] to deny
such permission requests without showing a prompt.

Chrome has announced this change over 2 years ago[2], but have yet to ship
it.  Our telemetry for beta 68 shows that cross-origin use of this feature
has very low usage[3] at around 0.02% of notification requests.

We’ll also log a warning in the web console when denying the permission
request because of this reason.

Please let me know if you have any questions or concerns.

Thanks,
Ehsan

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1560741
[2]
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/n37ij1E_1aY
[3] https://mzl.la/2Mafa6q
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Fission Newsletter #2

[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 be enabled for
running tests using mach test … --enable-fission.

When Fission is enabled, each cross-site iframe is loaded in a different
content process, meaning lots of different processes participate in drawing
a single tab. The hover tooltip for a Fission-enabled tab is annotated with
a "[F …]" containing a series of process IDs, as shown in the image below,
serving as a visual verification of an active Fission-enabled session.


We currently do not recommend trying to use Fission for day-to-day
browsing, as there are still known stability issues. However, if you do try
it out, please file bugs/issues blocking fission-dogfooding
.

Fission Mochitests on mozilla-central

Fission Mochitests were recently enabled as tier-2 jobs on mozilla-central.
This will allow us to run tests with Fission enabled on infrastructure, and
prevent landing new features or code which don't support Fission. Tests
which do not currently successfully pass are marked as fail-if =
Fission or skip-if
= Fission.

We'd love your help migrating tests to run with Fission enabled! Here are a
couple of handy tips for making your test Fission-compatible:

   1.

   Use SpecialPowers.spawn(target, [args…], async (args…) => { … }), to run
   code in potentially cross-origin iframes, as they may be in a different
   process. This API is similar to the ContentTask.spawn API used by
   browser-chrome mochitests.
   2.

   Wait for document loads to complete before trying to run code inside the
   target window, as a process switch may occur after the frame or browser is
   created. For frames in content, this usually means waiting for the load
   event.


These tests may also be run on the tryserver, however they are currently
excluded from the default set. They are called M-fis, and can be found
in ./mach
try fuzzy --full.

Fixing these Mochitests is a goal of our next major milestone, M4! There's
a ton of awesome stuff happening in M4, which you can read about on the
wiki (https://wiki.mozilla.org/Project_Fission#M4_goals).

Fission Talk and Demo

At the 2019 Whistler All-Hands, Nika gave a talk & demo about the Fission
architecture. This talk is publicly available on Air Mozilla.

You can watch the talk here:
https://onlinexperiences.com/Launch/Event.htm?ShowKey=44908=E334923

The slides are here:
https://docs.google.com/presentation/d/1equyaJTujM4xF-ucoMZiLE-lo0lbHKFMliUfPE4_1B8/edit?usp=sharing

And… So Much More!

A ton has happened in Fission over those 7 months, and it would be
impossible to cover all of the awesome work everyone has been contributing
to make Fission happen. We just want to say a massive thank you to everyone
who has helped with Fission - writing patches, doing reviews, planning, and
more! We hope to do brief update newsletters like this one with a better
cadence, so hopefully there'll be another one of these in your inbox soon.

Let's keep fission-on!

- The Fission Team.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Fission Newsletter #2

[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!) 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 be enabled for
> running tests using mach test … --enable-fission.
>
> When Fission is enabled, each cross-site iframe is loaded in a different
> content process, meaning lots of different processes participate in drawing
> a single tab. The hover tooltip for a Fission-enabled tab is annotated with
> a "[F …]" containing a series of process IDs, as shown in the image below,
> serving as a visual verification of an active Fission-enabled session.
>
>
> We currently do not recommend trying to use Fission for day-to-day
> browsing, as there are still known stability issues. However, if you do try
> it out, please file bugs/issues blocking fission-dogfooding
> .
>
> Fission Mochitests on mozilla-central
>
> Fission Mochitests were recently enabled as tier-2 jobs on mozilla-central.
> This will allow us to run tests with Fission enabled on infrastructure, and
> prevent landing new features or code which don't support Fission. Tests
> which do not currently successfully pass are marked as fail-if = Fission
> or skip-if = Fission.
>
> We'd love your help migrating tests to run with Fission enabled! Here are
> a couple of handy tips for making your test Fission-compatible:
>
>1.
>
>Use SpecialPowers.spawn(target, [args…], async (args…) => { … }), to
>run code in potentially cross-origin iframes, as they may be in a different
>process. This API is similar to the ContentTask.spawn API used by
>browser-chrome mochitests.
>2.
>
>Wait for document loads to complete before trying to run code inside
>the target window, as a process switch may occur after the frame or browser
>is created. For frames in content, this usually means waiting for the
>load event.
>
>
> These tests may also be run on the tryserver, however they are currently
> excluded from the default set. They are called M-fis, and can be found in 
> ./mach
> try fuzzy --full.
>
> Fixing these Mochitests is a goal of our next major milestone, M4! There's
> a ton of awesome stuff happening in M4, which you can read about on the
> wiki (https://wiki.mozilla.org/Project_Fission#M4_goals).
>
> Fission Talk and Demo
>
> At the 2019 Whistler All-Hands, Nika gave a talk & demo about the Fission
> architecture. This talk is publicly available on Air Mozilla.
>
> You can watch the talk here:
> https://onlinexperiences.com/Launch/Event.htm?ShowKey=44908=E334923
>
> The slides are here:
> https://docs.google.com/presentation/d/1equyaJTujM4xF-ucoMZiLE-lo0lbHKFMliUfPE4_1B8/edit?usp=sharing
>
> And… So Much More!
>
> A ton has happened in Fission over those 7 months, and it would be
> impossible to cover all of the awesome work everyone has been contributing
> to make Fission happen. We just want to say a massive thank you to
> everyone who has helped with Fission - writing patches, doing reviews,
> planning, and more! We hope to do brief update newsletters like this one
> with a better cadence, so hopefully there'll be another one of these in
> your inbox soon.
>
> Let's keep fission-on!
>
> - The Fission Team.
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Fission Newsletter #2

[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 enforced by the fission pref?
(webrender's support of different platforms has varying levels of quality,
although it is generally dogfoodable on all major platforms)

On Fri, Aug 9, 2019 at 1:43 PM Nika Layzell  wrote:

> 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!) 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 be enabled for
> > running tests using mach test … --enable-fission.
> >
> > When Fission is enabled, each cross-site iframe is loaded in a different
> > content process, meaning lots of different processes participate in
> drawing
> > a single tab. The hover tooltip for a Fission-enabled tab is annotated
> with
> > a "[F …]" containing a series of process IDs, as shown in the image
> below,
> > serving as a visual verification of an active Fission-enabled session.
> >
> >
> > We currently do not recommend trying to use Fission for day-to-day
> > browsing, as there are still known stability issues. However, if you do
> try
> > it out, please file bugs/issues blocking fission-dogfooding
> > .
> >
> > Fission Mochitests on mozilla-central
> >
> > Fission Mochitests were recently enabled as tier-2 jobs on
> mozilla-central.
> > This will allow us to run tests with Fission enabled on infrastructure,
> and
> > prevent landing new features or code which don't support Fission. Tests
> > which do not currently successfully pass are marked as fail-if = Fission
> > or skip-if = Fission.
> >
> > We'd love your help migrating tests to run with Fission enabled! Here are
> > a couple of handy tips for making your test Fission-compatible:
> >
> >1.
> >
> >Use SpecialPowers.spawn(target, [args…], async (args…) => { … }), to
> >run code in potentially cross-origin iframes, as they may be in a
> different
> >process. This API is similar to the ContentTask.spawn API used by
> >browser-chrome mochitests.
> >2.
> >
> >Wait for document loads to complete before trying to run code inside
> >the target window, as a process switch may occur after the frame or
> browser
> >is created. For frames in content, this usually means waiting for the
> >load event.
> >
> >
> > These tests may also be run on the tryserver, however they are currently
> > excluded from the default set. They are called M-fis, and can be found
> in ./mach
> > try fuzzy --full.
> >
> > Fixing these Mochitests is a goal of our next major milestone, M4!
> There's
> > a ton of awesome stuff happening in M4, which you can read about on the
> > wiki (https://wiki.mozilla.org/Project_Fission#M4_goals).
> >
> > Fission Talk and Demo
> >
> > At the 2019 Whistler All-Hands, Nika gave a talk & demo about the Fission
> > architecture. This talk is publicly available on Air Mozilla.
> >
> > You can watch the talk here:
> >
> https://onlinexperiences.com/Launch/Event.htm?ShowKey=44908=E334923
> >
> > The slides are here:
> >
> https://docs.google.com/presentation/d/1equyaJTujM4xF-ucoMZiLE-lo0lbHKFMliUfPE4_1B8/edit?usp=sharing
> >
> > And… So Much More!
> >
> > A ton has happened in Fission over those 7 months, and it would be
> > impossible to cover all of the awesome work everyone has been
> contributing
> > to make Fission happen. We just want to say a massive thank you to
> > everyone who has helped with Fission - writing patches, doing reviews,
> > planning, and more! We hope to do brief update newsletters like this one
> > with a better cadence, so hopefully there'll be another one of these in
> > your inbox soon.
> >
> > Let's keep fission-on!
> >
> > - The Fission Team.
> >
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Fission Newsletter #2

[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 generally working on
non-platform-specific functionality at this point. The most testing has
been done on Linux at this stage, though we're still very-much in early
days. I wouldn't recommend using fission for day-to-day browsing, as sites
with many cross-site iframes can be very slow to load and quite unstable.


> More concretely, I was under the impression that fission had webrender as
> a dependency, is that mandatory? Is it actually enforced by the fission
> pref? (webrender's support of different platforms has varying levels of
> quality, although it is generally dogfoodable on all major platforms)
>

We don't have a hard webrender dependency, and the browser should work
mostly-the-same on all platforms. Some edge cases with mouse event
targeting may work better with webrender enabled.


>
> On Fri, Aug 9, 2019 at 1:43 PM Nika Layzell  wrote:
>
>> 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!) 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 be enabled for
>> > running tests using mach test … --enable-fission.
>> >
>> > When Fission is enabled, each cross-site iframe is loaded in a different
>> > content process, meaning lots of different processes participate in
>> drawing
>> > a single tab. The hover tooltip for a Fission-enabled tab is annotated
>> with
>> > a "[F …]" containing a series of process IDs, as shown in the image
>> below,
>> > serving as a visual verification of an active Fission-enabled session.
>> >
>> >
>> > We currently do not recommend trying to use Fission for day-to-day
>> > browsing, as there are still known stability issues. However, if you do
>> try
>> > it out, please file bugs/issues blocking fission-dogfooding
>> > .
>> >
>> > Fission Mochitests on mozilla-central
>> >
>> > Fission Mochitests were recently enabled as tier-2 jobs on
>> mozilla-central.
>> > This will allow us to run tests with Fission enabled on infrastructure,
>> and
>> > prevent landing new features or code which don't support Fission. Tests
>> > which do not currently successfully pass are marked as fail-if = Fission
>> > or skip-if = Fission.
>> >
>> > We'd love your help migrating tests to run with Fission enabled! Here
>> are
>> > a couple of handy tips for making your test Fission-compatible:
>> >
>> >1.
>> >
>> >Use SpecialPowers.spawn(target, [args…], async (args…) => { … }), to
>> >run code in potentially cross-origin iframes, as they may be in a
>> different
>> >process. This API is similar to the ContentTask.spawn API used by
>> >browser-chrome mochitests.
>> >2.
>> >
>> >Wait for document loads to complete before trying to run code inside
>> >the target window, as a process switch may occur after the frame or
>> browser
>> >is created. For frames in content, this usually means waiting for the
>> >load event.
>> >
>> >
>> > These tests may also be run on the tryserver, however they are currently
>> > excluded from the default set. They are called M-fis, and can be found
>> in ./mach
>> > try fuzzy --full.
>> >
>> > Fixing these Mochitests is a goal of our next major milestone, M4!
>> There's
>> > a ton of awesome stuff happening in M4, which you can read about on the
>> > wiki (https://wiki.mozilla.org/Project_Fission#M4_goals).
>> >
>> > Fission Talk and Demo
>> >
>> > At the 2019 Whistler All-Hands, Nika gave a talk & demo about the
>> Fission
>> > architecture. This talk is publicly available on Air Mozilla.
>> >
>> > You can watch the talk here:
>> >
>> https://onlinexperiences.com/Launch/Event.htm?ShowKey=44908=E334923
>> >
>> > The slides are here:
>> >
>> https://docs.google.com/presentation/d/1equyaJTujM4xF-ucoMZiLE-lo0lbHKFMliUfPE4_1B8/edit?usp=sharing
>> >
>> > And… So Much More!
>> >
>> > A ton has happened in Fission over those 7 months, and it would be
>> > impossible to cover all of the awesome work everyone has been
>> contributing
>> > to make Fission happen. We just want to say a massive thank you to
>> > everyone who has helped with Fission - writing patches, doing reviews,
>> > planning, and more! We hope to do brief update newsletters like this one
>> > with a better cadence, so 

Re: Fission Newsletter #2

[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 stage)
> >
>
> The platform shouldn't have much impact, as we're generally working on
> non-platform-specific functionality at this point. The most testing has
> been done on Linux at this stage, though we're still very-much in early
> days. I wouldn't recommend using fission for day-to-day browsing, as sites
> with many cross-site iframes can be very slow to load and quite unstable.
>
>
> > More concretely, I was under the impression that fission had webrender as
> > a dependency, is that mandatory? Is it actually enforced by the fission
> > pref? (webrender's support of different platforms has varying levels of
> > quality, although it is generally dogfoodable on all major platforms)
> >
>
> We don't have a hard webrender dependency, and the browser should work
> mostly-the-same on all platforms. Some edge cases with mouse event
> targeting may work better with webrender enabled.
>

I believe the primary issue is that we need WebRender to hit our Fission
memory targets.


>
>
> >
> > On Fri, Aug 9, 2019 at 1:43 PM Nika Layzell 
> wrote:
> >
> >> 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!) 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 be enabled
> for
> >> > running tests using mach test … --enable-fission.
> >> >
> >> > When Fission is enabled, each cross-site iframe is loaded in a
> different
> >> > content process, meaning lots of different processes participate in
> >> drawing
> >> > a single tab. The hover tooltip for a Fission-enabled tab is annotated
> >> with
> >> > a "[F …]" containing a series of process IDs, as shown in the image
> >> below,
> >> > serving as a visual verification of an active Fission-enabled session.
> >> >
> >> >
> >> > We currently do not recommend trying to use Fission for day-to-day
> >> > browsing, as there are still known stability issues. However, if you
> do
> >> try
> >> > it out, please file bugs/issues blocking fission-dogfooding
> >> > .
> >> >
> >> > Fission Mochitests on mozilla-central
> >> >
> >> > Fission Mochitests were recently enabled as tier-2 jobs on
> >> mozilla-central.
> >> > This will allow us to run tests with Fission enabled on
> infrastructure,
> >> and
> >> > prevent landing new features or code which don't support Fission.
> Tests
> >> > which do not currently successfully pass are marked as fail-if =
> Fission
> >> > or skip-if = Fission.
> >> >
> >> > We'd love your help migrating tests to run with Fission enabled! Here
> >> are
> >> > a couple of handy tips for making your test Fission-compatible:
> >> >
> >> >1.
> >> >
> >> >Use SpecialPowers.spawn(target, [args…], async (args…) => { … }),
> to
> >> >run code in potentially cross-origin iframes, as they may be in a
> >> different
> >> >process. This API is similar to the ContentTask.spawn API used by
> >> >browser-chrome mochitests.
> >> >2.
> >> >
> >> >Wait for document loads to complete before trying to run code
> inside
> >> >the target window, as a process switch may occur after the frame or
> >> browser
> >> >is created. For frames in content, this usually means waiting for
> the
> >> >load event.
> >> >
> >> >
> >> > These tests may also be run on the tryserver, however they are
> currently
> >> > excluded from the default set. They are called M-fis, and can be found
> >> in ./mach
> >> > try fuzzy --full.
> >> >
> >> > Fixing these Mochitests is a goal of our next major milestone, M4!
> >> There's
> >> > a ton of awesome stuff happening in M4, which you can read about on
> the
> >> > wiki (https://wiki.mozilla.org/Project_Fission#M4_goals).
> >> >
> >> > Fission Talk and Demo
> >> >
> >> > At the 2019 Whistler All-Hands, Nika gave a talk & demo about the
> >> Fission
> >> > architecture. This talk is publicly available on Air Mozilla.
> >> >
> >> > You can watch the talk here:
> >> >
> >>
> https://onlinexperiences.com/Launch/Event.htm?ShowKey=44908=E334923
> >> >
> >> > The slides are here:
> >> >
> >>
> https://docs.google.com/presentation/d/1equyaJTujM4xF-ucoMZiLE-lo0lbHKFMliUfPE4_1B8/edit?usp=sharing
> >> >
> >> > And… So Much More!
> 

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

[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 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.
> Therefore, in Firefox 70 I plan to land a change in bug 1560741[1] to deny
> such permission requests without showing a prompt.
>
> Chrome has announced this change over 2 years ago[2], but have yet to ship
> it.  Our telemetry for beta 68 shows that cross-origin use of this feature
> has very low usage[3] at around 0.02% of notification requests.
>
> We’ll also log a warning in the web console when denying the permission
> request because of this reason.
>
> Please let me know if you have any questions or concerns.
>
> Thanks,
> Ehsan
>
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1560741
> [2]
>
> https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/n37ij1E_1aY
> [3] https://mzl.la/2Mafa6q
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Fission Newsletter #2

[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 
sensitive, so if you try to use `Fission` instead, it won't work.

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform