Revert 157745 "Add support for the object-position CSS property."

Revert 157745 "Add support for the object-position CSS property."

This is causing a number of debug layout tests to crash with
"ASSERTION FAILED: object-position is not whitelisted for animation"
in CSSAnimations::isAnimatableProperty.
e.g. see
http://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20%28dbg%29/builds/12296/steps/webkit_tests/logs/stdio

> Add support for the object-position CSS property.
> 
> This is hidden behind an "experimental" runtime flag named
> "ObjectFitPosition", together with object-fit.
> 
> This is an implementation of object-position as described in
> http://www.w3.org/TR/2012/CR-css3-images-20120417/#object-position
> 
> Object-position is used to offset replaced content within its content
> box. Painting is always clipped against the content box, regardless of
> the "overflow" property. This property is useful together with
> object-fit (to achieve a difference between content box size and
> replaced content size, so that specifying alignment is interesting),
> but can also be used on its own.
> 
> BUG=236333
> 
> Review URL: https://chromiumcodereview.appspot.com/22839023

TBR=mstensho@opera.com

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=157751

[ajuma, 2013-09-13 14:35:41]

Committed patchset #1 manually as r157751.

[mstensho (USE GERRIT), 2013-09-13 18:11:58]

I'm new, and I'm not sure why or how I should review this. Please tell me how to
proceed. :)

Also: I know I have to fix my code and re-apply it, but do I have to create a
new review, or can I re-use the old one?

[ajuma, 2013-09-13 18:31:13]

On 2013/09/13 18:11:58, Morten Stenshorne wrote:
> I'm new, and I'm not sure why or how I should review this. Please tell me how
to
> proceed. :)

Though codereview asks you to review this, reverts that have already landed with
a TBR aren't formally reviewed in practice.

> Also: I know I have to fix my code and re-apply it, but do I have to create a
> new review, or can I re-use the old one?

There isn't a consensus about whether to re-use the old codereview issue or to
create a new one. Here's a blink-dev discussion about this:
https://groups.google.com/a/chromium.org/d/topic/blink-dev/F0tc2EeJzao/discus...