Граф коммитов

18 Коммитов

Автор SHA1 Сообщение Дата
Ryan Hunt 00e98538aa Bug 1523969 part 6 - Move method definition inline comments to new line in 'dom/'. r=nika
Differential Revision: https://phabricator.services.mozilla.com/D21106

--HG--
extra : rebase_source : ea3f51c2c11247114deccbc86e90fb02b8a97257
2019-02-25 16:05:29 -06:00
Sylvestre Ledru 265e672179 Bug 1511181 - Reformat everything to the Google coding style r=ehsan a=clang-format
# ignore-this-changeset

--HG--
extra : amend_source : 4d301d3b0b8711c4692392aa76088ba7fd7d1022
2018-11-30 11:46:48 +01:00
Boris Chiou e3efce4cc6 Bug 1501117 - Part 2: Serialize timing function from web animation api with servo. r=emilio,birtles
It's worth to serialize the timing function from web animation api with
servo, too. However, we need an FFI to do that, so this patch also add a
new FFI.

Depends on D10443

Differential Revision: https://phabricator.services.mozilla.com/D10444

--HG--
extra : moz-landing-system : lando
2018-11-01 21:33:56 +00:00
Boris Chiou 3015824e8d Bug 1496619 - part 7: Implement steps(jump-*) functions r=birtles
1. Add a new preference, layout.css.step-position-jump.enabled, for
   step(_, jump-*) timing functions.
2. We still keep JumpEnd and End tags, even though there is no difference
   between them. Therefore, we could disable the preference if needed.
3. Update the calculation of StepTiming to match the algorithm in the spec.
4. For servo, we implement the correct step function algorithm except
   for the handling of before_flag. This could be fixed later.

Depends on D9313

Differential Revision: https://phabricator.services.mozilla.com/D9314

--HG--
extra : moz-landing-system : lando
2018-10-26 18:03:37 +00:00
Boris Chiou 04b273259e Bug 1496619 - part 6: Generate StyleTimingFunction and drop ns_timing_function.rs r=emilio,birtles
First, we generate StyleComputedTimingFunction by cbindgen from Rust, and use
it in nsTimingFunction, so we could copy it directly without handling
the different memory layout. However, we have to rewrite the
nsTimingFunction and mozilla::ComputedTimingFunction for this.

Second, the rust-bindgen seems cannot generate the correct generic members
from complex C++ templates, especially for the nested template struct,
(https://github.com/rust-lang-nursery/rust-bindgen/issues/1429)
So we have to hide StyleTimingFunction to avoid the compilation errors.

Depends on D9312

Differential Revision: https://phabricator.services.mozilla.com/D9313

--HG--
extra : moz-landing-system : lando
2018-10-26 18:03:35 +00:00
Boris Chiou adff31eff9 Bug 1496619 - Part 1: Drop frames() timing function r=birtles
frames() timing function was removed from the spec, so we drop it.
Besides, some devtool tests are removed because they use frame(). I will
add them back by using new step function later.

Differential Revision: https://phabricator.services.mozilla.com/D9309

--HG--
extra : moz-landing-system : lando
2018-10-26 18:03:24 +00:00
Boris Chiou af4598f9ae Bug 1248340 - Part 4: Implement Frames in the style system. r=dholbert
Use eCSSUnit_Function to store the frames timing function. Also, add one more
css keyword: frames.
The following changes are included in this:
1. Parser changes.
2. Serialization.
3. Computation in nsRuleNode.
4. Invalid and other values in property_database.js

MozReview-Commit-ID: 887QcXHQ2pU

--HG--
extra : rebase_source : ca0135380ea432cb69c4f36cf502d404e04999e5
2017-02-24 14:50:08 +08:00
Boris Chiou 98f895d166 Bug 1248340 - Part 2: Implement Frames in ComputedTimingFunction. r=birtles
MozReview-Commit-ID: 92MAv3OD8Tu

--HG--
extra : rebase_source : 0e14ade9e9f022b641605e2c0f368e3a6c950c18
2017-02-24 16:59:02 +08:00
Boris Chiou 89f3bc4396 Bug 1248340 - Part 1: Add the type of Frames in nsTimingFunction. r=birtles
MozReview-Commit-ID: GPn8D9gwjqa

--HG--
extra : rebase_source : 25e9f5f5d94545e26e467fe8666c03d8d222cda2
2017-02-24 14:34:08 +08:00
Brian Birtles 5ba8812302 Bug 1332206 - Don't clamp steps timing functions outside [0, 1] range; r=hiro
MozReview-Commit-ID: AiSdxQvU2mj

--HG--
extra : rebase_source : 77fb266b62a3a93ac134c1d65d1107c0bb8a110d
2017-02-08 09:25:31 +09:00
Daisuke Akatsuka 4f153efd27 Bug 1264865 - Part 3: Remove codes that are no longer in use. r=birtles
MozReview-Commit-ID: Dhrco8madlz

--HG--
extra : rebase_source : b26d9d25c2dd54f7ec0e12dd51127229cb085346
2016-07-27 10:13:17 +09:00
Hiroyuki Ikezoe cf5206ec40 Bug 1278485 - Part 2: ComputedTimingFunction::GetValue ensures 0 or 1 on both edges. r=birtles
MozReview-Commit-ID: ABkcUhhZdbZ

--HG--
extra : rebase_source : fa55b85515abe54d8ac4387e606039d88d4dbce0
2016-07-12 16:33:45 +09:00
Chris Peterson 8021dc9a73 Bug 1275475 - Fix -Wlogical-op warning in dom/animation/ComputedTimingFunction.cpp. r=daisuke
dom/animation/ComputedTimingFunction.cpp:33:114 [-Wlogical-op] logical 'or' of collectively exhaustive tests is always true

--HG--
extra : rebase_source : eaafc588d999c8653cbe8632f1e6ee232f34ae10
2016-05-22 21:02:12 -07:00
Daisuke Akatsuka 6c89bdf21b Bug 1248532 - Part 1: steps-start does not produce correct value at the beginning of the interval. r=birtles
MozReview-Commit-ID: F9b1HCfEqU6

--HG--
extra : transplant_source : %22xJ1%EBa%D6%7D%87%03%B84%2A5%CA9%93N%8A%16
2016-04-01 14:00:57 +09:00
Hiroyuki Ikezoe c5b7bd9a33 Bug 1216842 - Part 12: Extrapolate bezier function outside [0,1]. r=birtles
We use the tangent at the each boundary points as same as Chrome does.
2016-02-18 14:22:00 +01:00
Hiroyuki Ikezoe 10fdacf755 Bug 1216842 - Part 11: Clamp values of step functions outside [0, 1]. r=birtles 2016-02-18 14:21:00 +01:00
Hiroyuki Ikezoe 15210ae758 Bug 1216842 - Part 6: Make mTimingFunction in OrderedKeyframeValueEntry const Maybe<>*. r=cam 2016-01-29 14:47:00 +01:00
Boris Chiou 7203e534eb Bug 1208940 - Move ComputedTimingFunction to its own file. r=bbirtles 2015-11-01 22:41:00 +01:00