According to what Widevine told us, `kProtectionNone` will cause playback
to stop if HDCP_V1 is required. Therefore, we would report HDCP protection
if there is no potential capturing.
Differential Revision: https://phabricator.services.mozilla.com/D207483
This implements the behavior proposed in https://github.com/w3c/csswg-drafts/issues/10193.
Pending discussion of the issue there, and as input to that eventual debate, I'd like to
try enabling this behavior on Nightly to see how it goes in the wild.
This results in a bunch of failures on existing reftests, in an entirely predictable way,
because any text with letter-spacing gets offset slightly, and no longer matches with
references that assumed glyphs remain flush-left in their advance. If we do adopt the
symmetrical model across the web platform, corresponding test adjustments will be needed.
(We also get a few new passes, on tests involving letter-spacing + bidi, which is the case
where our legacy behavior is particularly poor, and the symmetrical model resolves the
issues.)
For the time being, with the pref change only on Nightly, I propose to just add pref
overrides in the manifests for the affected tests so that they stay green for both Nightly
and non-Nightly builds.
Differential Revision: https://phabricator.services.mozilla.com/D207421
Gecko always adds .2em space above and below stretchy operators but this
is not part of MathML Core and is causing several WPT failures. The
MATH table does not have any parameter for that so it's likely some
tweak that was added in the early days of MathML that may no longer be
necessary. This patch tentatively removes this feature by placing it
under a disabled-by-default flag.
Tests adjustments:
- table-width-1.xhtml: adjusted to work around antialiasing issue with the
top/bottom of stretchy operators (in the past the extra space added was
preventing this issue). This does not affect the testing goal, which is about
the width.
- stretchy-largeop-with-default-font-2.html: Some tests are failing depending
on the OS config so mark them as such. In the past, the extra vertical space
added was hiding the issue.
Differential Revision: https://phabricator.services.mozilla.com/D207014
Adds a mode where if bounce tracking protection is enabled it classifies
but does not purge trackers. This mode is helpful for testing the feature
without risking data loss. Telemetry is still collected normally.
Differential Revision: https://phabricator.services.mozilla.com/D206518
With the pref set to 0 by default, this does not change any existing behavior.
My intention is that a following patch will set it to 2 in Nightly. This will affect
a bunch of reftests, and so test/expectation adjustments will also be needed.
Differential Revision: https://phabricator.services.mozilla.com/D207150
Gecko always adds .2em space above and below stretchy operators but this
is not part of MathML Core and is causing several WPT failures. The
MATH table does not have any parameter for that so it's likely some
tweak that was added in the early days of MathML that may no longer be
necessary. This patch tentatively removes this feature by placing it
under a disabled-by-default flag.
Differential Revision: https://phabricator.services.mozilla.com/D207014
Gecko always adds .2em space above and below stretchy operators but this
is not part of MathML Core and is causing several WPT failures. The
MATH table does not have any parameter for that so it's likely some
tweak that was added in the early days of MathML that may no longer be
necessary. This patch tentatively removes this feature by placing it
under a disabled-by-default flag.
Differential Revision: https://phabricator.services.mozilla.com/D207014
Adds a mode where if bounce tracking protection is enabled it classifies
but does not purge trackers. This mode is helpful for testing the feature
without risking data loss. Telemetry is still collected normally.
Differential Revision: https://phabricator.services.mozilla.com/D206518
The MathML code adjust vertical position of basic binary operators with
the NS_MATHML_OPERATOR_CENTERED flag set (e.g. plus, equal or minus
signs) so that their centers align with the math axis. This behavior
is not defined in MathML Core and is not necessary in practice for math
fonts (which are already designed with the desired vertical alignments).
This patch tries and removes this by placing that legacy behavior
under a disabled-by-default runtime flag.
Intent-to-ship: https://groups.google.com/a/mozilla.org/g/dev-platform/c/nlA0t4J0gzo
Differential Revision: https://phabricator.services.mozilla.com/D207026
Unfortunately, we returned a `CompositionEvent` for
`Document.createEvent("textevent")` because we had a text event which we stopped
exposing to the web and was replaced with `eCompositionChange` event.
Therefore, this change could potentially have a compatibility risk.
Differential Revision: https://phabricator.services.mozilla.com/D200120
Unfortunately, we returned a `CompositionEvent` for
`Document.createEvent("textevent")` because we had a text event which we stopped
exposing to the web and was replaced with `eCompositionChange` event.
Therefore, this change could potentially have a compatibility risk.
Differential Revision: https://phabricator.services.mozilla.com/D200120
This moves the enabling to all.js, so that it is enabled for Thunderbird as well - now that Thunderbird is set up with their own version of the configuration.
Differential Revision: https://phabricator.services.mozilla.com/D206695
We introduce this rule and parse it in this patch. Also, fix some wpt
expectations for ERROR.
We will introduce CSSStartingStyleRule in the following patch, and test
it there.
Differential Revision: https://phabricator.services.mozilla.com/D206428
We introduce this rule and parse it in this patch. Also, fix some wpt
expectations for ERROR.
We will introduce CSSStartingStyleRule in the following patch, and test
it there.
Differential Revision: https://phabricator.services.mozilla.com/D206428
Previously the `boolean` type was also declared using a `bool` typedef in
xpidl, meaning that both were used in various places. This patch standardizes
on the built-in `boolean` type, removing the typedef.
Differential Revision: https://phabricator.services.mozilla.com/D206382
We know that we frequently hit this limit and so, based on observed performance improvements in sub-resource connection times, we are increasing it to 20.
Note that this is very conservative as on desktop we see no sign of overall socket pool exhaustion.
See https://bugzilla.mozilla.org/show_bug.cgi?id=1819556
Android changes will follow as we currently have a much smaller overall socket pool on that platform.
Differential Revision: https://phabricator.services.mozilla.com/D206406
