For those cpp files, it's sufficient to use Corner to refer to
mozilla::Corner.
MozReview-Commit-ID: JmDEJ3gGm8K
--HG--
extra : rebase_source : 79d7fc74fdb827894dd9ea17d6bb382eb75e81e8
To avoid confusion with the mozilla::css::corner, rename ::Corner to
mozilla::LogicalCorner, and move it to nsStyleCoord.h. Also, append
LogicalCorner prefix to all the enum values to match the coding style.
It also fixed the build error preemptively in a later patch that removing
::css namespace from mozilla::css::corner.
MozReview-Commit-ID: BbRYFuT3v4W
--HG--
extra : rebase_source : b8891eaa475c803de9a2137cb5e9a5a4bde37b9f
This changeset is intended to revert the logic from "Bug 1269045 part 3" [1],
*specifically* for legacy "-webkit-box"/"-webkit-inline-box" flex containers.
[1] https://hg.mozilla.org/mozilla-central/rev/707b2ab5879d
MozReview-Commit-ID: vc4TuAoLai
--HG--
extra : rebase_source : 3cc143055fc46851e882d48df2bd913ca1487793
This patch doesn't affect behavior at all -- it just refactors the
sanity-checking function "FrameWantsToBeInAnonymousItem()", so that the next
patch in this series can give it a new special case that checks a state bit on
the container frame.
This patch renames "parent" to "container" in this function's variable-names,
for clarity, because when this function returns true, the flex/grid container
is actually NOT expected to be the parent of aFrame. Rather, it's expected to
be the grandparent, and the anonymous flex/grid item would be the parent. So,
"aContainerFrame"/"containerType" is a bit more accurate (representing the
flex/grid container for aFrame).
Also worth mentioning: this patch makes FrameWantsToBeInAnonymousItem() perform
its own local GetType() call, instead of accepting an already-queried GetType()
result from the caller (as it previously did). Technically this could cause a
slight perf hit, but it doesn't really matter since this is in "#ifdef DEBUG"
sanity-checking code anyway. We could keep the nsIAtom* as an additional arg
to avoid this new call, but it seems better to fall on the side of simplicity &
just look up GetType() independently, rather than complicating the function
signature with an extra arg.
MozReview-Commit-ID: 4oJFkQMuH9c
--HG--
extra : rebase_source : 3b5d60d8c15e69470f450168698b855e353486d3
The addition of unicode-plaintext to the pre element will make RTL text to appear from right to left. The html[dir] pre rule will make sure that this addition won't break the 'switch page direction' functionality.
MozReview-Commit-ID: 2JXJjqt2iuX
--HG--
extra : rebase_source : 98c85228ce50fa145bfaa77051532f69e92ba98d
mask-opacity-1d.hmtl: vertify the change in Part 4. Before we land Part 4, the
rendering result in FF is not correct.
mask-opacity-1e.hmtl: vertify the change in Part 5.
MozReview-Commit-ID: GcbDCvr9ttF
--HG--
extra : rebase_source : 0be8c9cab639be2fda84a2a05319e25ba719ed09
Each concrete class of imgIContainer is able to handle opacity already. All we
need to do is pass opacity value to them.
MozReview-Commit-ID: EMkLnG3YXA1
--HG--
extra : rebase_source : b0a0aad1fec0c2765e96d23ed9b627345c793795
Some cubic-bezier functions, e.g. cubic-bezier(0,-0.5,0,0), produce values out
of range of [0, 1].
MozReview-Commit-ID: 9ZTsTRTcUaI
--HG--
extra : rebase_source : 7edf0c4d2702a502a9c0422be83ce7229751e815
mask-opacity-1d.hmtl: vertify the change in Part 4. Before we land Part 4, the
rendering result in FF is not correct.
mask-opacity-1e.hmtl: vertify the change in Part 5.
MozReview-Commit-ID: GcbDCvr9ttF
--HG--
extra : rebase_source : 842616602e1511cfebd7db5294c3937a6adb50e2
Each concrete class of imgIContainer is able to handle opacity already. All we
need to do is pass opacity value to them.
MozReview-Commit-ID: EMkLnG3YXA1
--HG--
extra : rebase_source : 080a843b34cc1ca27831310d474243b4066f59f2
I think there are three advantages of this change:
1. removes some dependencies from layout / painting code to pre-computed
value stuff in the style system;
2. makes it easier to audit usage of specific fields in style structs
(which is probably a side effect of the first one);
3. potentially improves performance since it doesn't go through the
unnecessary general logic in ExtractComputedValue.
Also, combined with the part before, we get a unified list for visited-
dependent properties so that we can ensure the assertion here and the
style difference calc code are consistent.
MozReview-Commit-ID: 5B9aN7CfRgI
--HG--
extra : rebase_source : ac80eaea2474b9ec4b47b1cc9a5bdd2e61f6ec4d
In cases where a mouse click that starts a scrollbar drag is also what
layerizes the scroll frame, the StartAsyncScrollbarDrag message needs to
arrive after the layer transaction. This patch ensures it does.
MozReview-Commit-ID: A02qRb6yWxg
--HG--
extra : rebase_source : 3517e8c8a578a0bd257a80bb8cb81303d171bb6c
