This patch applies the following changes:
- make sure that the WebExtensions internals do not create any devtools_page related to a private tabs' toolbox
if the extension is not allowed to access the private browsing windows
- define a new mochitest to verify the expended behaviors on the private windows when the extension is
allowed and not allowed
Depends on D15948
Differential Revision: https://phabricator.services.mozilla.com/D15949
--HG--
extra : moz-landing-system : lando
This patch moves some "devtools related" test helpers into a shared support file,
and updates all the existing devtools API mochitests to use the new shared test helpers.
This change has also the following nice side-effects:
- remove any usage of the custom devtools module loader from the webextensions mochitests.
- use a custom "test blank toolbox panel" in all the devtools API tests that doesn't need a specific
panel to be selected (which should help to make the test able to run a bit faster because none of
the more expensive devtools panels is going to be loaded during the tests if not actually needed).
Differential Revision: https://phabricator.services.mozilla.com/D15948
--HG--
extra : moz-landing-system : lando
When doing bidi resolution for column-content blocks, we may still
traverse the parent chain up in RemoveBidiContinuation, reach
nsColumnSetFrame, and accidentally convert nsColumnSetFrame's
continuation into fluid ones.
Differential Revision: https://phabricator.services.mozilla.com/D17551
--HG--
extra : moz-landing-system : lando
Calling nsBlockFrame::ResolveBidi() on ColumnSpanWrapperFrame may cause
nsColumnSetFrame's non-fluid continuations being converted into fluid
ones in JoinInlineAncestors().
Since ColumnSpanWrapperFrame can only have nsColumnSetFrame and
column-span wrappers kids, no need to perform bidi resolution. This
doesn't affect column contents because they'll inherit "unicode-bidi"
from ColumnSetWrapperFrame in ua.css.
Differential Revision: https://phabricator.services.mozilla.com/D17550
--HG--
extra : moz-landing-system : lando
The Google weather search result widget has an SVG inside a transform,
inside a scrollframe. The patch in bug 1523776 broke the clipping in
that the SVG elements would not get clipped by the scrollframe. This
reftest exercises that scenario.
Differential Revision: https://phabricator.services.mozilla.com/D18273
WhatsApp Web has emojis in divs with border-radius, inside a transform,
inside a scrollframe. The patch in bug 1523776 broke the clipping in
that scrolling the scrollframe would make the emoji visible outside the
scrollframe. This reftest replicates that scenario.
Differential Revision: https://phabricator.services.mozilla.com/D18272
Refcounted objects should be put into refptrs when they are created.
This patch also moves the crash helper out of the object early in
Init, to maybe reduce the chance of a leak if it fails early.
This field is only used to pass in a value to the Init() method. It
can't be passed in directly because on Android there are two
implementations of CDMProxy, and MediaDrmCDMProxy doesn't take a crash
helper.
Differential Revision: https://phabricator.services.mozilla.com/D17707
--HG--
extra : moz-landing-system : lando
The failures were remaining in the data object, which later had any remaining keys printed in the diagnostics section. This bug was introduced because we stopped using Array objects to generate formatted strings. In the previous code, this would have ended up just printing out the first failure listed in the diagnostics section (a partial duplicate of the actual Failure Log).
Differential Revision: https://phabricator.services.mozilla.com/D18289
--HG--
extra : moz-landing-system : lando
Next, we need to look for a frame for first parameter of calling
PresShell::HandleEvent() of another PresShell instance. This patch creates
PresShell::EventHandler::GetFrameForHandlingEventWith() to do it.
Unfortunately, the result is used in 3 patterns. One is, the caller should
stop handling the event. Another one is, the caller should keep handling
the event by itself. The other is, the caller should call
PresShell::HandleEvent() of different PresShell instance. Therefore, this
patch makes the method take aFrame of the caller. Then, the caller can check
the last 2 patterns with check the result is same as aFrame. This is not so
smart approach, but I have no better idea without adding a bool argument or
making the return type bool and adding out argument of nsIFrame.
Differential Revision: https://phabricator.services.mozilla.com/D16957
--HG--
extra : moz-landing-system : lando
1. Selected tabs inherit the same colors as active tabs.
2. On top of that, it's added a translucent (0.2 alpha) overlay :
2.1. For selected tabs with dark text, the overlay color is black (#000000)
2.2. For selected tabs with bright text, the overlay color is white (#ffffff)
3. On hover, the overlay becomes just more translucent with its value going down to 0.1 alpha.
Differential Revision: https://phabricator.services.mozilla.com/D16097
--HG--
extra : moz-landing-system : lando
This is a follow-up to https://phabricator.services.mozilla.com/D16560
Previously, we had a conservative estimation of the local size based on the footprint
of the screen onto the potential raster root. This was too conservative in general,
and in some cases it wasn't conservative enough, since with filters we can have areas
needed in local space that don't necessarily project on the screen.
This change is doing an exact check for the surface size after we compute it, and
falls back to the parent raster root accordingly.
Differential Revision: https://phabricator.services.mozilla.com/D18258
--HG--
extra : moz-landing-system : lando
Like bug 1505072 did on other platforms. The rust tests don't go through
the whole build system, and even when the clang plugin is enabled, they
don't build it. So when passing compiler flags down through cargo, the
arguments enabling the plugin are passed, and compilation of C/C++ code
from cargo subsequently fails.
Differential Revision: https://phabricator.services.mozilla.com/D18178
--HG--
extra : moz-landing-system : lando
Also use armv7a as the default when no target is given at all.
Also change bootstrap to create a simpler mozconfig. The downside is
that the resulting mozconfig would not work when building older
revisions.
Add unit tests for this as well as the simplications added in bug
1523341.
Differential Revision: https://phabricator.services.mozilla.com/D17906
--HG--
extra : moz-landing-system : lando
A normal shadow root cannot be attached to a non-HTML element so UA Shadow Root should always be allowed.
Differential Revision: https://phabricator.services.mozilla.com/D18158
--HG--
extra : moz-landing-system : lando
Alexandre Poirot
Dão Gottwald
Luca Greco
Emma Humphries
Ting-Yu Lin
arthur.iakab
shindli
Cosmin Sabou
Kartikaya Gupta
Andrew McCreight
Jared Wein
Masayuki Nakano
Jeff Gilbert
Dzmitry Malyshau
Andrea Marchesini
Ricky Rosario
Mark Banner
Ehsan Akhgari
Jean-Yves Avenard
Chris Manchester
Abdoulaye O. Ly
Mike Hommey
Timothy Guan-tin Chien
Dustin J. Mitchell
Bas Schouten
Jason Laster
Brian Hackett
Jaril
Jeff Walden
David Walsh
Nicolas Chevobbe
Jason Laster