If this pref is set, native layers will use a specialized video layer api for
fullscreen video content, which will reduce power consumption. It will do this
by isolating the fullscreen video layer from other layers. It may also remove
non-video content accompanying the fullscreen video. Content behind the video
*will* be replaced with a black fullscreen rectangle.
Future bugs will aim to reduce this side effect.
Differential Revision: https://phabricator.services.mozilla.com/D124999
We add scroll-timeline rule into the stylesheet rule type, and add a new
perference to protect it: layout.css.scroll-linked-animations.enabled.
We will use this perference for animation-timeline property as well.
Differential Revision: https://phabricator.services.mozilla.com/D125765
It looks like these were formatted wrong by mistake, and so the final `else` value in both instances was being used as the default value on all platforms.
Differential Revision: https://phabricator.services.mozilla.com/D125753
Add prefs:
* browser.sessionstore.dom_form_limit
Limit for how long a value from a form can be to be included in
session store collection.
* browser.sessionstore.dom_form_max_limit
Limit how much total data we collect from forms from one site, as in
the sum of length of values plus sum of length of xpath/id.
Differential Revision: https://phabricator.services.mozilla.com/D125195
With the non-native theme we don't need filter for this to affect
"native" inputs, we can just implement the logic in nsNativeBasicTheme
instead.
A bit unfortunate that we need that special-case, but it seems better
than using filter, which can break websites due to it creating an
stacking context.
I _think_ there are tests that I need to adjust for this change, but if
not I'll write some.
Keep the current behavior behind a pref just in case.
Differential Revision: https://phabricator.services.mozilla.com/D125232
On one website, the touch input fluffing made an audio scrubber so large that it
covered other playback controls, making them inaccessible. This patch addresses
this problem by changing the top fluffing radius so it more closely matches the
bottom radius.
In our investigation, we found the top radius was added asymmetrically to the
bottom radius without an explanation. We speculate the bottom bias was added
because when you touch the screen, you tend to aim with the top part of your
finger, near your fingernail, and sometimes the bottom part of your finger will
also touch the screen, fat fingering it: if true, we would fluff the event less
below the touch point (which is what the code was). I vaguely remember this fat
fingering problem in the early 2010's but I haven't thought about it in recent
years and I didn't notice this problem in my testing for this patch – perhaps
device touch handling has just gotten better. Therefore, we feel safe to remove
the bias.
Differential Revision: https://phabricator.services.mozilla.com/D124267
With the non-native theme we don't need filter for this to affect
"native" inputs, we can just implement the logic in nsNativeBasicTheme
instead.
A bit unfortunate that we need that special-case, but it seems better
than using filter, which can break websites due to it creating an
stacking context.
I _think_ there are tests that I need to adjust for this change, but if
not I'll write some.
Keep the current behavior behind a pref just in case.
Differential Revision: https://phabricator.services.mozilla.com/D125232
I'll add some tests before enabling. Also, WebKit folks (who have
implemented cos() / tan() / sin()) said they will upstream their tests
to WPT, so I'll extend those with the inverse functions before landing
as well.
Differential Revision: https://phabricator.services.mozilla.com/D124990
This also remove `FPSCounter`, `TimedMetric`, and these prefs:
- layers.acceleration.draw-fps.print-histogram
- layers.acceleration.draw-fps.write-to-file
Differential Revision: https://phabricator.services.mozilla.com/D125110
Add a pref to manage Sqlite.jsm logging, default to reporting Errors.
Change some of the logging to more coherently report warnings, errors and debug info.
Reuse the same logger for all the objects, just change the prefix.
Depends on D124184
Differential Revision: https://phabricator.services.mozilla.com/D124916
