Fix serialization of step timing functions

Fix serialization of step timing functions

The CSS Transitions specification recently added a section specifying how timing
functions should be serialized:
https://hg.csswg.org/drafts/rev/12d32649a91f
https://drafts.csswg.org/css-transitions/#serializing-a-timing-function

This patch changes how step timing functions are serialized in order to bring it
in line with the spec. The corresponding parsing function devtools/front_end is
also updated.

The removal of "step-middle" and "steps(x, middle)" as valid values is deferred
until frames() is implemented (see crbug.com/646265).

BUG=631875, 600248
Committed: https://crrev.com/d660b195483e9910ee6bfc3ad25df28301a35259
Cr-Commit-Position: refs/heads/master@{#418704}

[suzyh_UTC10 (ex-contributor), 2016-09-13 06:44:14]

suzyh@chromium.org changed reviewers:
+ shans@chromium.org

[suzyh_UTC10 (ex-contributor), 2016-09-13 06:44:24]

The CQ bit was checked by suzyh@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-13 06:44:31]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[suzyh_UTC10 (ex-contributor), 2016-09-13 07:01:19]

Description was changed from

==========
Fix serialization of step timing functions

The CSS Transitions specification recently added a section specifying how timing
functions should be serialized:
https://hg.csswg.org/drafts/rev/12d32649a91f
https://drafts.csswg.org/css-transitions/#serializing-a-timing-function

This patch changes how step timing functions are serialized in order to bring it
inline with the spec.

BUG=631875,600248
==========

to

==========
Fix serialization of step timing functions

The CSS Transitions specification recently added a section specifying how timing
functions should be serialized:
https://hg.csswg.org/drafts/rev/12d32649a91f
https://drafts.csswg.org/css-transitions/#serializing-a-timing-function

This patch changes how step timing functions are serialized in order to bring it
inline with the spec.

The removal of "step-middle" and "steps(x, middle)" as valid values is deferred
until frames() is implemented (see crbug.com/646265).

BUG=631875,600248
==========

[suzyh_UTC10 (ex-contributor), 2016-09-13 07:01:54]

On 2016/09/13 at 06:44:20, suzyh wrote:
> 

NB: Updated the CL description to document the choice to keep step-middle for
now.

[commit-bot: I haz the power, 2016-09-13 08:06:29]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-13 08:06:30]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[suzyh_UTC10 (ex-contributor), 2016-09-14 04:49:30]

Description was changed from

==========
Fix serialization of step timing functions

The CSS Transitions specification recently added a section specifying how timing
functions should be serialized:
https://hg.csswg.org/drafts/rev/12d32649a91f
https://drafts.csswg.org/css-transitions/#serializing-a-timing-function

This patch changes how step timing functions are serialized in order to bring it
inline with the spec.

The removal of "step-middle" and "steps(x, middle)" as valid values is deferred
until frames() is implemented (see crbug.com/646265).

BUG=631875,600248
==========

to

==========
Fix serialization of step timing functions

The CSS Transitions specification recently added a section specifying how timing
functions should be serialized:
https://hg.csswg.org/drafts/rev/12d32649a91f
https://drafts.csswg.org/css-transitions/#serializing-a-timing-function

This patch changes how step timing functions are serialized in order to bring it
in line with the spec. The corresponding parsing function devtools/front_end is
also updated.

The removal of "step-middle" and "steps(x, middle)" as valid values is deferred
until frames() is implemented (see crbug.com/646265).

BUG=631875,600248
==========

[suzyh_UTC10 (ex-contributor), 2016-09-14 04:49:30]

suzyh@chromium.org changed reviewers:
+ samli@chromium.org

[suzyh_UTC10 (ex-contributor), 2016-09-14 04:49:44]

+samli for devtools/front_end

[suzyh_UTC10 (ex-contributor), 2016-09-14 04:49:54]

The CQ bit was checked by suzyh@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-14 04:50:00]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[samli, 2016-09-14 05:37:33]

devtools/front_end lgtm

[commit-bot: I haz the power, 2016-09-14 06:48:07]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-14 06:48:08]

Dry run: This issue passed the CQ dry run.

[shans, 2016-09-14 22:38:09]

lgtm

[suzyh_UTC10 (ex-contributor), 2016-09-14 22:38:49]

The CQ bit was checked by suzyh@chromium.org

[commit-bot: I haz the power, 2016-09-14 22:39:25]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-14 22:45:14]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-09-14 22:48:49]

Description was changed from

==========
Fix serialization of step timing functions

The CSS Transitions specification recently added a section specifying how timing
functions should be serialized:
https://hg.csswg.org/drafts/rev/12d32649a91f
https://drafts.csswg.org/css-transitions/#serializing-a-timing-function

This patch changes how step timing functions are serialized in order to bring it
in line with the spec. The corresponding parsing function devtools/front_end is
also updated.

The removal of "step-middle" and "steps(x, middle)" as valid values is deferred
until frames() is implemented (see crbug.com/646265).

BUG=631875,600248
==========

to

==========
Fix serialization of step timing functions

The CSS Transitions specification recently added a section specifying how timing
functions should be serialized:
https://hg.csswg.org/drafts/rev/12d32649a91f
https://drafts.csswg.org/css-transitions/#serializing-a-timing-function

This patch changes how step timing functions are serialized in order to bring it
in line with the spec. The corresponding parsing function devtools/front_end is
also updated.

The removal of "step-middle" and "steps(x, middle)" as valid values is deferred
until frames() is implemented (see crbug.com/646265).

BUG=631875,600248

Committed: https://crrev.com/d660b195483e9910ee6bfc3ad25df28301a35259
Cr-Commit-Position: refs/heads/master@{#418704}
==========

[commit-bot: I haz the power, 2016-09-14 22:48:50]

Patchset 2 (id:??) landed as
https://crrev.com/d660b195483e9910ee6bfc3ad25df28301a35259
Cr-Commit-Position: refs/heads/master@{#418704}