Do not trigger touch adjustment in AddressDetectionTest#testAddressLimits

Do not trigger touch adjustment in AddressDetectionTest#testAddressLimits

Blink behaviour is being changed to re-use the hit test node for content
detection so this test shouldn't trigger touch adjustment as future changes to
adjustment would cause this to fail.

This is part 1 of 2, will be followed by
https://codereview.chromium.org/604573002

BUG=381728, 416746
Committed: https://crrev.com/8bac2728a9e154010aaf8cf210d9731f82b01987
Cr-Commit-Position: refs/heads/master@{#297546}

[Zeeshan Qureshi, 2014-09-24 23:34:48]

zeeshanq@chromium.org changed reviewers:
+ aruslan@chromium.org, jdduke@chromium.org

[Zeeshan Qureshi, 2014-09-24 23:34:49]

Jared / Ruslan PTAL.

[Zeeshan Qureshi, 2014-09-24 23:39:27]

+cc rbyers

[jdduke (slow), 2014-09-25 00:21:25]

If this is blocking rolls, then lgtm (assuming it's fine with aruslan@) with
nit.

https://codereview.chromium.org/603813002/diff/1/content/public/android/javat...
File
content/public/android/javatests/src/org/chromium/content/browser/AddressDetectionTest.java
(right):

https://codereview.chromium.org/603813002/diff/1/content/public/android/javat...
content/public/android/javatests/src/org/chromium/content/browser/AddressDetectionTest.java:73:
// FIXME: Enable after crrev.com/604573002 lands
Nit: In Chromium this should be

// TODO(zeeshanq): ...

[Zeeshan Qureshi, 2014-09-25 00:25:52]

Thanks, updated.

The blink side hasn't landed yet, I'm just lining this up and will wait for
aruslan@

[jdduke (slow), 2014-09-25 00:26:02]

On 2014/09/24 23:39:27, Zeeshan Qureshi wrote:
> +cc rbyers

Wait, this is the first patch? I'd like to have the discussion first before we
land anything.

[Zeeshan Qureshi, 2014-09-30 18:50:41]

zeeshanq@chromium.org changed reviewers:
- aruslan@chromium.org

[Zeeshan Qureshi, 2014-09-30 18:51:43]

aruslan@ says he's not the right reviewer for this. Jared would you know who'd
be the best person?

[jdduke (slow), 2014-09-30 19:22:21]

https://codereview.chromium.org/603813002/diff/20001/content/public/android/j...
File
content/public/android/javatests/src/org/chromium/content/browser/AddressDetectionTest.java
(right):

https://codereview.chromium.org/603813002/diff/20001/content/public/android/j...
content/public/android/javatests/src/org/chromium/content/browser/AddressDetectionTest.java:73:
// TODO(zeeshanq): Enable after crrev.com/604573002 lands
I don't think we should be testing touch adjustment at all here. Can we just
re-arrange the page to make sure we're not activating touch adjustment?

[Zeeshan Qureshi, 2014-09-30 22:23:01]

Updated.

The problem was that putting the text anywhere near a div with content in it was
causing it to be adjusted to it. I didn't spend too much time debugging but will
file a bug.

[jdduke (slow), 2014-09-30 22:29:18]

On 2014/09/30 22:23:01, Zeeshan Qureshi wrote:
> Updated.
> 
> The problem was that putting the text anywhere near a div with content in it
was
> causing it to be adjusted to it. I didn't spend too much time debugging but
will
> file a bug.

lgtm, thanks!

[Zeeshan Qureshi, 2014-09-30 22:33:34]

The CQ bit was checked by zeeshanq@chromium.org

[commit-bot: I haz the power, 2014-09-30 22:35:12]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/603813002/40001

[commit-bot: I haz the power, 2014-09-30 23:37:02]

Committed patchset #3 (id:40001) as 6b8deabcefe30cec9834c006b89f8218c679757c

[commit-bot: I haz the power, 2014-09-30 23:38:13]

Patchset 3 (id:??) landed as
https://crrev.com/8bac2728a9e154010aaf8cf210d9731f82b01987
Cr-Commit-Position: refs/heads/master@{#297546}