This patch removes the unnecessary getContentBlockingLog function from
nsIDocShell.idl.
Differential Revision: https://phabricator.services.mozilla.com/D57444
--HG--
extra : moz-landing-system : lando
This patch is doing two things.
1. Make GeckoView directly gets the ContentBlockingLog in the parent
process when it gets the bundle event 'ContentBlocking:RequestLog'. It
will get the top-level browsingContext and get the log from the
WindowGlobal of this browsingContext.
2. Remove the GeckoViewContentBlockingChild. The child module of
ContentBlocking is no longer needed since it serves nothing after we move
the functionality of getting log to the parent process.
Differential Revision: https://phabricator.services.mozilla.com/D57464
--HG--
extra : moz-landing-system : lando
Ensure we have called controller's shutdown before it gets destroyed and not to change its internal status after shutdown.
Differential Revision: https://phabricator.services.mozilla.com/D60563
--HG--
extra : moz-landing-system : lando
There are a number of issues with the current gradient dithering
implementation, that cause many test failures and also fuzziness
rendering when enabling DirectComposition virtual surfaces. In
particular, the dither result is dependent on the offset of the
update rect within a render target.
For now, this patch disables gradient dithering by default. This
gives us:
- A heap of new test PASS results (or reduced fuzziness).
- Fixes a number of non-deterministic fuzziness bugs with DC.
- Improves performance of gradient rendering by a reasonable amount.
We can fix gradient dithering as a follow up, and re-enable if/when
we find content that would benefit from it significantly (we may
be able to improve gradients in other ways than dithering too).
Differential Revision: https://phabricator.services.mozilla.com/D60460
--HG--
extra : moz-landing-system : lando
The semantics of the inaccuracy reftest mode are that the overall
test succeeds as long as one of the multiple test images mismatches
the reference image.
However, the previous implementation would print an unexpected result
if any of the comparisons were equal (even though the overall test
result would be reported correctly).
This patch changes wrench so that it only reports an unexpected
failure for the overall test, not each individual reference.
Differential Revision: https://phabricator.services.mozilla.com/D60564
--HG--
extra : moz-landing-system : lando
I tried to write a test for this, but it looks like
mCurrentAttributes.mGenerateTimestamps is only true when the type is "audio/aac"
or "audio/mpeg", and we don't support either of those in MediaSource. So this
code can't actually be reached, as far as I can tell.
Differential Revision: https://phabricator.services.mozilla.com/D60597
--HG--
extra : moz-landing-system : lando
Ensure we have called controller's shutdown before it gets destroyed and not to change its internal status after shutdown.
Differential Revision: https://phabricator.services.mozilla.com/D60563
--HG--
extra : moz-landing-system : lando
The original physical axis AxisOrientationType contains direction
information, which can be replaced by physical start side
straightforwardly.
Differential Revision: https://phabricator.services.mozilla.com/D59055
--HG--
extra : moz-landing-system : lando
Note that I return LogicalMargin by value for GetMargin(). It is
considered a suboptimal practice to return a constant reference to a
member variable. We won't gain performance by returning a reference
because the compiler can optimize the return value. If it were assigned
to a new variable, the copy/move constructor is called anyway.
As noted in FIXME(TYLin), the AxisOrientationType argument in
GetMarginBorderPaddingSizeInMainAxis() and many other methods can be
removed. However, to make the patch size manageable, I'll remove them in
a later part.
Differential Revision: https://phabricator.services.mozilla.com/D59051
--HG--
extra : moz-landing-system : lando
Also, use GetPhysicalMargin() instead of mMargin in
FlexItem::GetBaselineOffsetFromOuterCrossEdge() to ease the transition
when converting FlexItem::mMargin to LogicalMargin in the later parts.
Differential Revision: https://phabricator.services.mozilla.com/D59050
--HG--
extra : moz-landing-system : lando
These new added member variables and mWM are going to be used in the
following parts that convert border/padding/margin to use logical
layout, so they are added to the place prior to mBorderPadding and
mMargin.
For "strut" constructor, we can use the default values for mMainAxis,
mCrossAxis, and mIsInlineAxisMainAxis initialized in the class
declaration.
Differential Revision: https://phabricator.services.mozilla.com/D59048
--HG--
extra : moz-landing-system : lando
This includes renaming aAxis to aPhysicalAxis in PositionTracker's
constructor.
Differential Revision: https://phabricator.services.mozilla.com/D59046
--HG--
extra : moz-landing-system : lando
I'm going to add logical accessors and variables in the next patch, so
it's better the rename the old ones first.
Differential Revision: https://phabricator.services.mozilla.com/D59044
--HG--
extra : moz-landing-system : lando
Fix "warning: deleted member function should be public", which can be
reproduced by
`./mach static-analysis check layout/generic/nsFlexContainerFrame.cpp`
If a private delete method is called, the compiler shows two error
messages: the method is deleted, and a private methods is called. By
declaring the method as public, only the former message is shown, which
should be more readable.
Differential Revision: https://phabricator.services.mozilla.com/D59043
--HG--
extra : moz-landing-system : lando