Prepare for ISO-8859-1 to windows-1252 switch

Prepare for ISO-8859-1 to windows-1252 switch

The following Blink CL will make 'windows-1252' the canonical name
for 'ISO-8859-1', 'US-ASCII' and 'windows-1252'. All three will be
treated synonymously per the WHATWG Encoding spec.

   https://codereview.chromium.org/655083002/

We have some test results with 'ISO-8859-1'. Change them to use
windows-1252 and disable them before landing the above Blink CL.

For PrefsTabHelperBrowserTest.WebPrefs, I made the test more robust
by setting 'windows-1251' (not '1252') as the default charset in
the Test Preference file.

Once the Blink CL is landed and rolled, we'll re-enable the disabled
tests as a part of the following Cr CL:
  https://codereview.chromium.org/649413002/ ,
which rolls ICU 52 to the latest revision (the other side of
ISO-8859-1 to windows-1252 transition).

TBR=jochen,rdsmith,mnissler,jsbell
BUG=412053
TEST=browser_tests the following tests (before and after the Blink roll)
    BrowserEncodingTest.TestEncodingAutoDetect
    BrowserEncodingTest.TestOverrideEncoding
    EncodingAliases/BrowserEncodingTest.TestEncodingAliasMapping
    SavePageBrowserTest.FileNameFromPageTitle
    SavePageBrowserTest.SaveCompleteHTML
    PrefsTabHelperBrowserTest.WebPrefs

Committed: https://crrev.com/51a1d05292ca2813ef6f74e61c1d5e390e2a4f3f
Cr-Commit-Position: refs/heads/master@{#300069}

[jungshik at Google, 2014-10-16 22:16:25]

jshin@chromium.org changed reviewers:
+ jochen@chromium.org, jsbell@chromium.org, mnissler@chromium.org,
rdsmith@chromium.org

[jungshik at Google, 2014-10-16 22:16:25]

I'll TBR this CL because this is just disabling and changing the expected result
in preparation for an upcoming Blink CL. 

mnissler@chromium.org: Please review changes in browser/ui/prefs

rdsmith@chromium.org: Please review changes in browser/download

jochen@chromium.org: Please review changes in chrome/browser

[jsbell, 2014-10-16 22:53:24]

The commit comment is:

'ISO-8859-1', 'US-ASCII' and 'ISO-8859-1'

Did you mean to list ISO-8859-1 twice?

Also, stray ) after one of the URLs.

[jungshik at Google, 2014-10-17 05:35:45]

The CQ bit was checked by jshin@chromium.org

[commit-bot: I haz the power, 2014-10-17 05:36:42]

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

[commit-bot: I haz the power, 2014-10-17 05:36:43]

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

[commit-bot: I haz the power, 2014-10-17 05:36:44]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[jungshik at Google, 2014-10-17 05:41:20]

On 2014/10/16 22:53:24, jsbell wrote:
> The commit comment is:
> 
> 'ISO-8859-1', 'US-ASCII' and 'ISO-8859-1'
> 
> Did you mean to list ISO-8859-1 twice?
> 
> Also, stray ) after one of the URLs.

Thank you for catching them. I corrected both issues.

[jungshik at Google, 2014-10-17 05:42:39]

The CQ bit was checked by jshin@chromium.org

[commit-bot: I haz the power, 2014-10-17 05:43:53]

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

[commit-bot: I haz the power, 2014-10-17 06:10:50]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-17 06:11:40]

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