Add --disable-compositor-touch-hit-testing flag

Add --disable-compositor-touch-hit-testing flag

Plumb the flag to blink and the compositor.
Disable by default in Android webview for now.

Depends on blink CL: https://src.chromium.org/viewvc/blink?view=rev&revision=158956

BUG=303945
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=227511

[Rick Byers, 2013-10-04 02:10:39]

Alex,
Can you please review the chromium side of this patch?  I'll have to wait for
the blink side (https://codereview.chromium.org/25507008/) to land and roll
before landing this.

Do you think it's worth adding a test case?  It's pretty much entirely stupid
plumbing.  I've got a simple test case on the blink side.

Thanks,
   Rick

[aelias_OOO_until_Jul13, 2013-10-04 02:50:01]

lgtm.  I don't think it's worth adding a test case, particularly as in theory
this optimization doesn't change behavior so it's unclear how to cleanly test.

[Rick Byers, 2013-10-04 04:33:47]

On 2013/10/04 02:50:01, aelias wrote:
> lgtm.  I don't think it's worth adding a test case, particularly as in theory
> this optimization doesn't change behavior so it's unclear how to cleanly test.

Thanks.

+darin for OWNERS.
It's sad how much boring plumbing this takes :-(

[darin (slow to review), 2013-10-05 06:13:13]

On 2013/10/04 04:33:47, Rick Byers wrote:
> On 2013/10/04 02:50:01, aelias wrote:
> > lgtm.  I don't think it's worth adding a test case, particularly as in
theory
> > this optimization doesn't change behavior so it's unclear how to cleanly
test.
> 
> Thanks.
> 
> +darin for OWNERS.
> It's sad how much boring plumbing this takes :-(

Thoughts on how to make it better?

[darin (slow to review), 2013-10-05 06:14:15]

LGTM

[commit-bot: I haz the power, 2013-10-07 20:01:45]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/rbyers@chromium.org/25904004/8001

[Rick Byers, 2013-10-07 20:03:35]

On 2013/10/05 06:13:13, darin wrote:
> On 2013/10/04 04:33:47, Rick Byers wrote:
> > On 2013/10/04 02:50:01, aelias wrote:
> > > lgtm.  I don't think it's worth adding a test case, particularly as in
> theory
> > > this optimization doesn't change behavior so it's unclear how to cleanly
> test.
> > 
> > Thanks.
> > 
> > +darin for OWNERS.
> > It's sad how much boring plumbing this takes :-(
> 
> Thoughts on how to make it better?

I think our time is better served by first cleaning up existing settings /
switches (removing those that aren't really necessary, getting more consistency
between platforms, and applying a bit more discipline to adding new ones). 
There's a thread on blink-dev related to this now, and I'm filing bugs / putting
up some CLs to help.  Maybe once once temporary settings/switches are reliably
getting removed we can invest in making it easier to add (and later remove) them
:-)

[commit-bot: I haz the power, 2013-10-07 20:43:04]

Retried try job too often on linux_rel for step(s) cc_unittests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_rel&...

[commit-bot: I haz the power, 2013-10-08 04:42:14]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/rbyers@chromium.org/25904004/33001

[commit-bot: I haz the power, 2013-10-08 07:03:18]

Retried try job too often on win7_aura for step(s) interactive_ui_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win7_aura&...

[commit-bot: I haz the power, 2013-10-08 09:36:28]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/rbyers@chromium.org/25904004/33001

[commit-bot: I haz the power, 2013-10-08 14:27:15]

Change committed as 227511