Remove TOUCH_EVENTS and TOUCH_EVENT_TRACKING compile-time flags.

Remove TOUCH_EVENTS and TOUCH_EVENT_TRACKING compile-time flags.

This mechanical patch should have no web-visible effect, as we enable both these
flags everywhere we build Chromium.

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

[Use mkwst_at_chromium.org plz., 2013-04-16 19:23:04]

Hello, Reviewers!

Would you mind taking a look at this fairly mechanical patch?

-mike

[eseidel, 2013-04-16 19:31:14]

LGTM.

https://codereview.chromium.org/14296003/diff/1/Source/WebCore/dom/Element.idl
File Source/WebCore/dom/Element.idl (right):

https://codereview.chromium.org/14296003/diff/1/Source/WebCore/dom/Element.id...
Source/WebCore/dom/Element.idl:202: [NotEnumerable,EnabledAtRuntime=touch,
PerWorldBindings] attribute EventListener ontouchstart;
Missing a space.

https://codereview.chromium.org/14296003/diff/1/Source/WebCore/dom/TouchEvent...
File Source/WebCore/dom/TouchEvent.idl (left):

https://codereview.chromium.org/14296003/diff/1/Source/WebCore/dom/TouchEvent...
Source/WebCore/dom/TouchEvent.idl:27: Conditional=TOUCH_EVENTS
I wish we had a bindings mechanism to ASSERT that classes like these could not
be instantiated when the runtime flag was off.  Right now every possible place
this is exposed needs to check the runtime flag and there is no ASSERT help to
make sure we've caught them all.

[Mike West, 2013-04-18 12:50:08]

Committed patchset #4 manually as r148646 (presubmit successful).

[Use mkwst_at_chromium.org plz., 2013-04-18 12:50:53]

On 2013/04/18 12:50:08, Mike West (chromium) wrote:
> Committed patchset #4 manually as r148646 (presubmit successful).

Rebased; bots are happy except for a test that looks unrelatedly flaky.