Delete flag --enable-css-transform-pinch.

Delete flag --enable-css-transform-pinch.

This flag activated a different coordinate space for pinch that was used
only on Android.  Android has now converted to desktop pinch and this
old mode is already starting to break, so we should delete this flag.
I'll follow up with further cleanup later.

I also set apply_page_scale_factor_in_compositor to true in all cases in
order to avoid needing any further support for the codepaths where it's
false (it should be a no-op when pinch is disabled in principle).

NOTRY=true
BUG=173534
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=180048

[aelias_OOO_until_Jul13, 2013-02-01 00:12:35]

Hi Antoine,

Just a quick cleanup of a cruft flag to avoid confusing people.

[piman, 2013-02-01 00:25:09]

https://codereview.chromium.org/12089100/diff/1/content/browser/web_contents/...
File content/browser/web_contents/web_contents_impl.cc (right):

https://codereview.chromium.org/12089100/diff/1/content/browser/web_contents/...
content/browser/web_contents/web_contents_impl.cc:651:
prefs.apply_page_scale_factor_in_compositor = true;
apply_page_scale_factor_in_compositor was only set when kEnablePinch was set.
Did you intend to change this?

I don't understand fully what the flags effect is, so double-checking

[aelias_OOO_until_Jul13, 2013-02-01 00:34:11]

Yes, I intended to change it.  It affects the treatment of pageScaleFactor in
WebKit and CC.  In the case where pinch zoom is disabled and pageScaleFactor ==
1.0, the flip should be a no-op in principle.  But if there develops some bug or
quirk somewhere that makes it not a no-op, the safer option is to go with true
in all cases to make things simpler to support.

[piman, 2013-02-01 02:08:00]

OK, LGTM if you know what you're doing

[commit-bot: I haz the power, 2013-02-01 02:34:02]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/aelias@chromium.org/12089100/1

[commit-bot: I haz the power, 2013-02-01 03:02:21]

Change committed as 180048