Because the new function checks types, we need to change the fullCorner type
in nsComputedDOMStyle::GetEllipseRadii() and
StyleAnimationValue::ExtractComputedValue() from uint8_t to |Corner| to fix
build error.
MozReview-Commit-ID: 5NuFE3yA2QD
--HG--
extra : rebase_source : 8f94209b24bd909839358cd502f462edb9ce3116
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
Actually this is the same as color accumulation. Now we can pass test cases
that interpolation with overflowed values.
MozReview-Commit-ID: L4RqBhG5n3l
--HG--
extra : rebase_source : e80f1c135b33703dcda7c99df897aa7097030f05
This patch also fixes expected computed offset values in frame at 0.5 offset for
add composite.
MozReview-Commit-ID: 8PNp237NoV4
--HG--
extra : rebase_source : 7bdf83741198fb81c6721cad1764e6464033c240
This patch was written with the help of the following script. Also, manually
add mozilla qualifier to the enum values in nsStyleCoord.h, gfxRect.h, and
Types.h to make it build.
function rename() {
find .\
-type f\
! -path "./obj*"\
! -path "./.git"\
! -path "./.hg"\
\( -name "*.cpp" -or\
-name "*.h" \)\
-exec sed -i -e "s/$1/$2/g" "{}" \;
}
rename "NS_SIDE_TOP" "eSideTop"
rename "NS_SIDE_RIGHT" "eSideRight"
rename "NS_SIDE_BOTTOM" "eSideBottom"
rename "NS_SIDE_LEFT" "eSideLeft"
MozReview-Commit-ID: 9T0ORsqM6nP
--HG--
extra : rebase_source : 884ad96104c6e9cf6c8b3145d2d3a071ecccfe6a
This patch is written with the help of the following script.
function rename() {
find .\
-type f\
! -path "./obj*"\
! -path "./.git"\
! -path "./.hg"\
\( -name "*.cpp" -or\
-name "*.h" \)\
-exec sed -i -e "s/$1/$2/g" "{}" \;
}
rename "css::Side" "Side"
MozReview-Commit-ID: DPV6vivpPUp
--HG--
extra : rebase_source : 9c4f66dc9d2b26c89a4517fba4ff9c5db413411b
We should follow the rules used by other types - return false if computing
the distance is failed. So make ComputeShapeDistance and return the status
and let the last argument be the output distance.
MozReview-Commit-ID: CFoQhgyqILB
--HG--
extra : rebase_source : 353c42e54e554b0477e88ad8c1ee0d611e16618b
Both eUnit_Shadow and the drop-shadow of eUnit_Filter needs to compute the
distance of two shadows, so we can factor out the implementation.
MozReview-Commit-ID: IGdxQWMXdE1
--HG--
extra : rebase_source : 9889c556c0cc007102a152859575cfe56830ca61
We want to reuse AddShapeFunction for calculating the distance, so add
one more argument to enable/disable the default restrictions, so we can
reuse AddShapeFunction to get the differences, which may be negative values,
between two shape functions.
MozReview-Commit-ID: FgzOnPzyyAQ
--HG--
extra : rebase_source : e2ee1267100ef02a43131366eef9d46fc2f63ebe
Two things in this patch:
1. Move AddCSSValuePixelPercentCalc to the position above AddTransformTranslate.
2. Simplify AddTransformTranslate, i.e. re-use the same switch case of
AddCSSValuePixelPercentCalc.
MozReview-Commit-ID: BMEpkOHDoaT
--HG--
extra : rebase_source : 591da977266c5be01fdb5f27aa11e26f94fc6060
Decompose the 2d/3d matrix and calculate the Euclidean distance of
translate, scale, skew, quaternion, and perspective vectors.
MozReview-Commit-ID: 5nX9EeqvZi9
--HG--
extra : rebase_source : a15f2e4350e5c097eee8856a76244a81d589427a
Move Decompose2DMatrix and Decompose3DMatrix into nsStyleTransformMatrix
and remove some trailing spaces.
Both AddWeighted and ComputeDistance need Decompose2DMatrix and
Decompose3DMatrix on transform property, and both decomposition functions are
related to nsStyleTransformMatrix, so we move them into nsStyleTransformMatrix
to make StyleAnimationValue more concise.
MozReview-Commit-ID: 5aVK7971rDD
--HG--
extra : rebase_source : 75823b96a165ef65e3edfb00978b706d9db09393
Reuse AddTransformLists to get the identity transform functions to
replace none, and then treat them with another transform list as two matched
ones.
MozReview-Commit-ID: HwdBPCiUivg
--HG--
extra : rebase_source : 552ff668e2ac19dbfcfe2a37894b278f699f0c0b
Use quaternion vectors to calculate the distance of two rotate3d
functions.
MozReview-Commit-ID: LizbvRqzcuh
--HG--
extra : rebase_source : 6b852d1f66ba7d79708156119db63683900120fb
Implement these transform functions for matched transform lists:
1. translate3d
2. scale3d
3. skewXY (and skewX, skewY, skew)
4. rotateX, rotateY, rotateZ, rotate, and rotate3d with the same
direction axis.
MozReview-Commit-ID: 94so7VGHqc8
--HG--
extra : rebase_source : d68488e3b6e87d72702c348fa0495a4d0c17ab85
We also need these functions in ComputeDistance:
1. AddTransformTranslate
2. AddCSSValueAngle
3. TransformFunctionsMatch
So move them up.
MozReview-Commit-ID: 8mSFEOgUsLT
--HG--
extra : rebase_source : a58107f50e6636d4aeec93e086490cda09027ded
Ting-Yu Lin
Wes Kocher
Hiroyuki Ikezoe
Boris Zbarsky
Xidorn Quan
Sebastian Hengst
Cameron McCormack
cku
Daniel Holbert
Jonathan Kew
Carsten "Tomcat" Book
Boris Chiou
Manish Goregaokar