Upon enabling the HTML about:addons discovery pane, about:addons page
start to send a fetch request from the default user context, instead of
a content load request with the tab's user context.
This mismatch in userContextId triggers the following debug assertion:
https://searchfox.org/mozilla-central/rev/c606cdd6d014f/netwerk/base/nsNetUtil.cpp#3021-3024
This assertion can be ignored, because the request has no credentials,
so its context should not matter.
Differential Revision: https://phabricator.services.mozilla.com/D34688
--HG--
extra : moz-landing-system : lando
This should make the test more managable as we add properties
validators in InactivePropertyHelper.
eslint doesn't support dynamic import yet, so we have to ignore
the test file.
Differential Revision: https://phabricator.services.mozilla.com/D34677
--HG--
rename : devtools/server/tests/mochitest/test_inspector-inactive-property-helper.html => devtools/server/tests/mochitest/inactive-property-helper/gap.js
rename : devtools/server/tests/mochitest/test_inspector-inactive-property-helper.html => devtools/server/tests/mochitest/inactive-property-helper/max-min-width-height.js
rename : devtools/server/tests/mochitest/test_inspector-inactive-property-helper.html => devtools/server/tests/mochitest/inactive-property-helper/vertical-align.js
extra : moz-landing-system : lando
- Don't block all drawing until whole screen was painted, clear the screen and
allow partial drawing instead.
- Detect window resize and allow partial drawing directly to wayland buffer in this case.
- Remove backbuffer copy - wait to buffer release instead.
Depends on D33910
Differential Revision: https://phabricator.services.mozilla.com/D33911
--HG--
extra : moz-landing-system : lando
Enable the web platform tests for clearkey scheme checking. Since these tests
simply check if the functionality is implemented, and do not check if the
browsers actually support different encryption schemes, it's okay to do this
even though we don't have cbcs support in clearkey yet. I.e. it's enough that a
page can ask "do you support cbcs in clearkey?" to Firefox to pass the test, the
answer from Firefox doesn't have to be "yes."
Add the pref setting to the DRM scheme checking test, though leave the
expectations as they are on this test, as in automation the test will still not
pass due to Widevine downloads being blocked. My hope is that we can find a
solution to this Widevine download issue in automation, at which point we'd
expect that tests to start passing due to the pref added in this patch -- at
which point we could toggle the expectations.
Differential Revision: https://phabricator.services.mozilla.com/D34303
--HG--
extra : moz-landing-system : lando
Drive by reordering of includes per google style and remove several unused
headers.
Differential Revision: https://phabricator.services.mozilla.com/D34302
--HG--
extra : moz-landing-system : lando
Add encryption scheme member to MediaKeySystemMediaCapability dict, but hide it
behind a pref as the behaviour involved is only proposed at this stage.
Differential Revision: https://phabricator.services.mozilla.com/D34301
--HG--
extra : moz-landing-system : lando
Surprisingly, `Document::ExecCommand()` may be called when there is no
corresponding `nsPresContext`. Then, `nsContentUtils::GetHTMLEditor()`
crashes because it does not check whether the argument is `nullptr` or not.
This patch makes it check whether `aPresContext` is `nullptr` or not, and
makes `Document::ExecCommand()` not try to look for an editor when its
`GetPresContext()` returns `nullptr`. This means that we cannot send
proper `nsIPrincipal` object to the editor in this case. But I'm not sure
how it's important and whether editor can or cannot modify the DOM tree
actually.
Differential Revision: https://phabricator.services.mozilla.com/D34505
--HG--
extra : moz-landing-system : lando
Use memory tracking APIs to track malloc memory associated with module IndirectBindingMap. These are attached to ModuleObjects and ModuleNamespaceObjects.
Differential Revision: https://phabricator.services.mozilla.com/D34551
The correct mapping for nsIAccessibleEvent::EVENT_TEXT_SELECTION_CHANGED
in ATK is text_selection_changed; not selection_changed. The latter is
meant for containers which support selection of child objects, such as
a menu or expanded select element.
Differential Revision: https://phabricator.services.mozilla.com/D34521
--HG--
extra : moz-landing-system : lando
The UTF-16 to UTF-8 conversion is now handled by XPConnect, because we're using AUTF8String for the type.
Differential Revision: https://phabricator.services.mozilla.com/D34560
--HG--
extra : moz-landing-system : lando
This works around the following situation: the Ngv/fat AAR task is
deterministic, but it depends on N tasks for multiple architectures,
adn the exact l10n changeset pulled by each N task depends on the tip
of the l10n HG repository at the time the N task executes.
For now, just ignore the obvious localized resources: *.ftl, *.dtd,
*.properties.
Differential Revision: https://phabricator.services.mozilla.com/D33413
--HG--
extra : moz-landing-system : lando
Otherwise clamped positions in layer pixels might cause 1-pixel difference
in CSS pixels on Android.
Note that there is a fundamental issue on the interaction between
the layer-pixel alignment and scrolling APIs (bug 1556685), once we fix the bug
properly, we should use the scrolled position, which was given by the scrolling
APIs, for the current position.
Differential Revision: https://phabricator.services.mozilla.com/D32779
--HG--
extra : moz-landing-system : lando
