Fix date picker performance issues, crash, and incorrect pre-1582 dates.

Fix date picker performance issues, crash, and incorrect pre-1582 dates.

This cleans up the DateDialogNormalizer, fixing three issues in the
process:

 1. The date picker is now way faster on L devices. This works around a
    performance issue with the Android DatePicker in L, where large
    min/max ranges consume tons of memory and time (many seconds). The
    workaround is simply to limit the date picker's range to at most
    5000 years before and after the initial selected date. In practice,
    this doesn't affect users since manually scrolling through 5000
    years is infeasible.

 2. This fixes a crash when the min date is after 2100 on pre-L devices.
    On KK and earlier, calling DatePicker.setMinDate() with a date
    that's greater than the current max date (which defaults to 2100)
    causes a crash. The fix is to set the DatePicker's min and max dates
    in such an order that the min is always less than the max.

 3. This fixes an issue where min/max dates before 1582 were off by 10
    days due to incorrect handling of the Gregorian/Julian switch.

This also revamps DateDialogNormalizerTest and converts it to a
Robolectric test.

BUG=441060, 580385, 580388
Committed: https://crrev.com/9e226039ff46dbc40f8529e2b70a577230d4d9dd
Cr-Commit-Position: refs/heads/master@{#371404}

[newt (away), 2016-01-22 22:57:41]

newt@chromium.org changed reviewers:
+ miguelg@chromium.org

[newt (away), 2016-01-22 22:57:41]

miguelg: PTAL

[newt (away), 2016-01-22 22:58:13]

newt@chromium.org changed reviewers:
+ mikecase@chromium.org

[newt (away), 2016-01-22 22:58:13]

Mike: PTAL gyp/gn changes for the new ui_junit_tests target

[mikecase (-- gone --), 2016-01-22 23:04:17]

gyp and gn, lgtm

[newt (away), 2016-01-22 23:07:26]

The CQ bit was checked by newt@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-01-22 23:08:45]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1622773002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1622773002/1

[commit-bot: I haz the power, 2016-01-23 00:46:09]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-23 00:46:09]

Dry run: This issue passed the CQ dry run.

[Miguel Garcia, 2016-01-23 16:52:47]

lgtm

Thanks for the thorough change!

[newt (away), 2016-01-25 17:59:07]

The CQ bit was checked by newt@chromium.org

[commit-bot: I haz the power, 2016-01-25 18:00:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1622773002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1622773002/1

[commit-bot: I haz the power, 2016-01-25 18:10:24]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-25 18:10:24]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[newt (away), 2016-01-25 18:19:39]

dpranke: PTAL at src/BUILD.gn, all.gyp, and gn_migration.gypi.

[newt (away), 2016-01-26 00:46:19]

newt@chromium.org changed reviewers:
+ dpranke@chromium.org

[newt (away), 2016-01-26 00:46:19]

dpranke: PTAL at src/BUILD.gn, all.gyp, and gn_migration.gypi. Thanks!

[Dirk Pranke, 2016-01-26 00:53:05]

lgtm

[newt (away), 2016-01-26 00:54:23]

The CQ bit was checked by newt@chromium.org

[newt (away), 2016-01-26 00:54:46]

The CQ bit was checked by newt@chromium.org

[commit-bot: I haz the power, 2016-01-26 00:55:15]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1622773002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1622773002/1

[commit-bot: I haz the power, 2016-01-26 01:30:21]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-26 01:31:33]

Description was changed from

==========
Fix date picker performance issues, crash, and incorrect pre-1582 dates.

This cleans up the DateDialogNormalizer, fixing three issues in the
process:

 1. The date picker is now way faster on L devices. This works around a
    performance issue with the Android DatePicker in L, where large
    min/max ranges consume tons of memory and time (many seconds). The
    workaround is simply to limit the date picker's range to at most
    5000 years before and after the initial selected date. In practice,
    this doesn't affect users since manually scrolling through 5000
    years is infeasible.

 2. This fixes a crash when the min date is after 2100 on pre-L devices.
    On KK and earlier, calling DatePicker.setMinDate() with a date
    that's greater than the current max date (which defaults to 2100)
    causes a crash. The fix is to set the DatePicker's min and max dates
    in such an order that the min is always less than the max.

 3. This fixes an issue where min/max dates before 1582 were off by 10
    days due to incorrect handling of the Gregorian/Julian switch.

This also revamps DateDialogNormalizerTest and converts it to a
Robolectric test.

BUG=441060,580385,580388
==========

to

==========
Fix date picker performance issues, crash, and incorrect pre-1582 dates.

This cleans up the DateDialogNormalizer, fixing three issues in the
process:

 1. The date picker is now way faster on L devices. This works around a
    performance issue with the Android DatePicker in L, where large
    min/max ranges consume tons of memory and time (many seconds). The
    workaround is simply to limit the date picker's range to at most
    5000 years before and after the initial selected date. In practice,
    this doesn't affect users since manually scrolling through 5000
    years is infeasible.

 2. This fixes a crash when the min date is after 2100 on pre-L devices.
    On KK and earlier, calling DatePicker.setMinDate() with a date
    that's greater than the current max date (which defaults to 2100)
    causes a crash. The fix is to set the DatePicker's min and max dates
    in such an order that the min is always less than the max.

 3. This fixes an issue where min/max dates before 1582 were off by 10
    days due to incorrect handling of the Gregorian/Julian switch.

This also revamps DateDialogNormalizerTest and converts it to a
Robolectric test.

BUG=441060,580385,580388

Committed: https://crrev.com/9e226039ff46dbc40f8529e2b70a577230d4d9dd
Cr-Commit-Position: refs/heads/master@{#371404}
==========

[commit-bot: I haz the power, 2016-01-26 01:31:34]

Patchset 1 (id:??) landed as
https://crrev.com/9e226039ff46dbc40f8529e2b70a577230d4d9dd
Cr-Commit-Position: refs/heads/master@{#371404}