Hi Colleagues!
I'm removing TabGroup (and by virtue of it becoming just an
indirection I'm also removing SystemGroup), and this affects you if
you're doing event dispatching in a handful of ways.
TabGroup was the way in wich Quantum DOM would manage how runnables
were scheduled, but with Fission,
Hello Colleagues!
Now that we’ve passed All-Hands it’s time for another Fission
newsletter. To begin with the Fission team wants to thank all who came
to the introduction and the office hours! The slides from the
introduction are available online[1].
Our currently targeted milestones are M4.1, M5
Hello, Colleagues!
tl;dr
We're removing nsIDocShellTreeItem because of Fission. Please refrain
from using it, and please help us out!
As we're getting further along with Fission, the work on removing
nsIDocShellTreeItem completely comes into increased focus. With
Fission enabled you can no longer
TL;DR We have decided to not (re-)turn on throttling of timeouts from
tracking scripts, and also remove throttling of timeouts from tracking
scripts altogether.
This feature was, in the beginning, only intended for tabs in the
background, but experiments were also conducted to see the effect of
th
I see no reason for us to not support this.
On Tue, Oct 10, 2017 at 5:37 PM, L. David Baron wrote:
> A W3C Proposed Recommendation is available for the membership of
> W3C (including Mozilla) to vote on, before it proceeds to the final
> stage of being a W3C Recomendation:
>
> Cooperative Sched
et this wrong. I wonder if you have tested this with Web Audio
> scenarios in mind. We had a similar issue a while ago where web audio
> scheduled with setTimeouts (a common practice) would time out when eager
> optimisations were in place:
>
> https://bugzilla.mozilla.org/show_bug.cg
ults and maybe tune these constants? Do you plan to expose any of these
> parameters to web extensions?
>
> Gabor
>
> On Thu, Oct 5, 2017 at 5:27 PM, Andreas Farre wrote:
>>
>> Hi all!
>>
>> After Bug 1377766 lands, we will increase the amount timeouts
>&g
Hi all!
After Bug 1377766 lands, we will increase the amount timeouts
executing in background tabs are throttled, based on an execution
budget. This budget is continuously regenerating, and is decreased
when timeouts execute. If the budget becomes negative, timeouts will
not be allowed to run unti
Hi all!
As of 2017-06-21 I intend to, for nightly only, turn on throttling of
timeouts from tracking scripts for windows in the foreground. We're
already shipping this for background timeouts, and our hope is that
enabling throttling for foreground will help us determine the
effectiveness of the t
On Fri, May 19, 2017 at 4:18 AM, Mark Hammond wrote:
> On 5/18/17 12:03 PM, Boris Zbarsky wrote:
>>
>> On 5/17/17 9:22 PM, Mark Hammond wrote:
>>>
>>> I'm wondering if there are any ideas about how to solve this optimally?
>>
>>
>> I assume
>> https://w3c.github.io/requestidlecallback/#the-request
Timeouts classified using privacy.trackingprotection.annotate_channels as
coming from a tracking script.
On 11 May 2017 7:05 pm, "Boris Zbarsky" wrote:
> On 5/11/17 10:59 AM, Andreas Farre wrote:
>
>> As of 2017-05-15 I intend to turn on throttling of background tracking
this feature? This feels
> like something that is both quite important and quite risky and I'd love to
> understand more about how you plan to test/validate this kind of feature.
>
> --BDS
>
> On Thu, May 11, 2017 at 10:59 AM, Andreas Farre wrote:
>>
>> Hi!
>>
Hi!
As of 2017-05-15 I intend to turn on throttling of background tracking
timeouts by default. It has been developed behind the
dom.timeout.tracking_throttling_delay pref. Other relevant prefs are:
dom.min_tracking_timeout_value,
dom.min_tracking_background_timeout_value,
privacy.trackingprotect
As of 2016-11-7 I intend to turn requestIdleCallback on by default
(with the condition that
https://bugzilla.mozilla.org/show_bug.cgi?id=1314314 has landed). It
has been developed behind the dom.requestIdleCallback.enabled
preference. Other UAs shipping this or intending to ship it are Chrome
(ship
Summary:
Load a specified URL in a controlled client page. Part of the service
workers spec
Bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1218148
Link to standard:
https://www.w3.org/TR/service-workers/#client-navigate-method
Platform coverage:
All platforms
Estimated or target release:
Fir
Summary:
Add an API on Window for requesting a callback when the user agent is
idle.
With requestIdleCallback web developers will be able to schedule
background computation tasks on the event loop that has a better
chance of not interfering with other more time-critical operations.
Bug: https://b
Even better!
On Fri, Apr 8, 2016 at 2:49 PM, Steve Fink wrote:
> On 04/08/2016 09:13 AM, Andreas Farre wrote:
>
>> Looking for someone emacs savvy to help me with running mach --debug as a
>> command for M-x gdb. Currently there is an issue with mach logging a bit
>> to
is filed for a while now, just need to do something about it.
>> :/
>>
>> On Fri, Apr 8, 2016 at 9:13 AM, Andreas Farre wrote:
>>
>> > Looking for someone emacs savvy to help me with running mach --debug as
>> a
>> > command for M-x gdb. Currently th
Looking for someone emacs savvy to help me with running mach --debug as a
command for M-x gdb. Currently there is an issue with mach logging a bit to
much which screws up the GDB/MI communication with emacs. Has anyone
already some solution for this? Otherwise I got it working by adding a
quiet fla
19 matches
Mail list logo
