1954770 - Enable dom.workers.timeoutmanager and put it into the release cycle

Status: RESOLVED FIXED

(Core :: DOM: Workers, task)

Description

[Artur Iunusov]

We need to enable dom.workers.timeoutmanager around next softfreeze

So far, it's enabled for Nightly only

Comment 1

[Artur Iunusov]

Attachment: Bug 1954770 - Enable dom.workers.timeoutmanager and put it into the release cycle, r=smaug

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/c6aa28938ca8
Enable dom.workers.timeoutmanager and put it into the release cycle, r=smaug

Comment 3

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/c6aa28938ca8

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Should we add this to the Fx139 relnotes? Please add a relnote-firefox? nomination if yes.

Comment 5

[Artur Iunusov]

Release Note Request (optional, but appreciated)
[Why is this notable]: we changed timeout manager implementation on Workers (to enable timers throttling)
[Affects Firefox for Android]: yes
[Suggested wording]:
[Links (documentation, blog post, etc)]: to be added

Comment 6

[Ryan VanderMeulen [:RyanVM]]

Added to the Fx139 relnotes, but it would be really nice if we could flesh this one out a bit.

Comment 7

[Jens Stutte [:jstutte]]

(In reply to Ryan VanderMeulen [:RyanVM] from comment #6)

Added to the Fx139 relnotes, but it would be really nice if we could flesh this one out a bit.

[Why is this notable]: Being able to rely on the same timeout implementation everywhere reduces the risk of hard to diagnose differences between workers and normal content.
[Affects Firefox for Android]: yes
[Suggested wording]: Workers & Service workers now use the same timeout implementation as everything else, reducing the risk of hard to diagnose differences.
[Links (documentation, blog post, etc)]: None (there is hopefully no user perceivable functional change).