Chromium Code Reviews| Index: LayoutTests/css3/calc/transitions-expected.txt |
| diff --git a/LayoutTests/css3/calc/transitions-expected.txt b/LayoutTests/css3/calc/transitions-expected.txt |
| index 710e0cbd7e1f804cd8c6158f3435fcfbcd5bda31..7c401dab2d2322e99c82c9fe84c185d687a7cd95 100644 |
| --- a/LayoutTests/css3/calc/transitions-expected.txt |
| +++ b/LayoutTests/css3/calc/transitions-expected.txt |
| @@ -1,27 +1,21 @@ |
| -This tests that transitions containing calc() expressions transition correctly. |
| -PASS - "width" property for "startCalcEndCalc" element at 0.0s was: 100 |
| -PASS - "width" property for "startPxEndCalc" element at 0.0s was: 100 |
| -PASS - "width" property for "startPercentEndCalc" element at 0.0s was: 100 |
| -PASS - "width" property for "startCalcEndPx" element at 0.0s was: 100 |
| -PASS - "width" property for "startCalcEndPercent" element at 0.0s was: 100 |
| PASS - "width" property for "startCalcEndCalc" element at 0.25s saw something close to: 175 |
|
Steve Block
2013/05/23 05:17:20
Is it expected to lose the results at 0s?
|
| -PASS - "width" property for "startCalcEndCalc" element at 0.5s saw something close to: 250 |
| -PASS - "width" property for "startCalcEndCalc" element at 0.75s saw something close to: 325 |
| -PASS - "width" property for "startCalcEndCalc" element at 1s saw something close to: 400 |
| PASS - "width" property for "startPxEndCalc" element at 0.25s saw something close to: 175 |
| -PASS - "width" property for "startPxEndCalc" element at 0.5s saw something close to: 250 |
| -PASS - "width" property for "startPxEndCalc" element at 0.75s saw something close to: 325 |
| -PASS - "width" property for "startPxEndCalc" element at 1s saw something close to: 400 |
| PASS - "width" property for "startPercentEndCalc" element at 0.25s saw something close to: 175 |
| -PASS - "width" property for "startPercentEndCalc" element at 0.5s saw something close to: 250 |
| -PASS - "width" property for "startPercentEndCalc" element at 0.75s saw something close to: 325 |
| -PASS - "width" property for "startPercentEndCalc" element at 1s saw something close to: 400 |
| PASS - "width" property for "startCalcEndPx" element at 0.25s saw something close to: 175 |
| -PASS - "width" property for "startCalcEndPx" element at 0.5s saw something close to: 250 |
| -PASS - "width" property for "startCalcEndPx" element at 0.75s saw something close to: 325 |
| -PASS - "width" property for "startCalcEndPx" element at 1s saw something close to: 400 |
| PASS - "width" property for "startCalcEndPercent" element at 0.25s saw something close to: 175 |
| +PASS - "width" property for "startCalcEndCalc" element at 0.5s saw something close to: 250 |
| +PASS - "width" property for "startPxEndCalc" element at 0.5s saw something close to: 250 |
| +PASS - "width" property for "startPercentEndCalc" element at 0.5s saw something close to: 250 |
| +PASS - "width" property for "startCalcEndPx" element at 0.5s saw something close to: 250 |
| PASS - "width" property for "startCalcEndPercent" element at 0.5s saw something close to: 250 |
| +PASS - "width" property for "startCalcEndCalc" element at 0.75s saw something close to: 325 |
| +PASS - "width" property for "startPxEndCalc" element at 0.75s saw something close to: 325 |
| +PASS - "width" property for "startPercentEndCalc" element at 0.75s saw something close to: 325 |
| +PASS - "width" property for "startCalcEndPx" element at 0.75s saw something close to: 325 |
| PASS - "width" property for "startCalcEndPercent" element at 0.75s saw something close to: 325 |
| +PASS - "width" property for "startCalcEndCalc" element at 1s saw something close to: 400 |
| +PASS - "width" property for "startPxEndCalc" element at 1s saw something close to: 400 |
| +PASS - "width" property for "startPercentEndCalc" element at 1s saw something close to: 400 |
| +PASS - "width" property for "startCalcEndPx" element at 1s saw something close to: 400 |
| PASS - "width" property for "startCalcEndPercent" element at 1s saw something close to: 400 |