Revert of views: Initialize DesktopScreenX11::primary_display_index_.

Revert of views: Initialize DesktopScreenX11::primary_display_index_. (patchset #1 id:1 of https://codereview.chromium.org/1983863003/ )

Reason for revert:
Speculative revert to see if reverting this affects the tests on Windows 7 (Dbg)(1) http://crbug.com/612523

Original issue's description:
> views: Initialize DesktopScreenX11::primary_display_index_.
>
> The new field was introduced in crrev.com/391625, but this field was left
> uninitialized in this ctor.
>
> BUG=42313
>
> Committed: https://crrev.com/71017aa70fb2feaa60c8178e253b100969800b63
> Cr-Commit-Position: refs/heads/master@{#393985}

TBR=sky@chromium.org,sadrul@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=42313
Committed: https://crrev.com/e6688b1f2a74cd5055938f0fe05322ef011e7036
Cr-Commit-Position: refs/heads/master@{#394266}

[qyearsley, 2016-05-17 23:18:27]

Created Revert of views: Initialize DesktopScreenX11::primary_display_index_.

[commit-bot: I haz the power, 2016-05-17 23:19:29]

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

[commit-bot: I haz the power, 2016-05-17 23:20:10]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-17 23:22:21]

Description was changed from

==========
Revert of views: Initialize DesktopScreenX11::primary_display_index_. (patchset
#1 id:1 of https://codereview.chromium.org/1983863003/ )

Reason for revert:
Speculative revert to see if reverting this affects the tests on Windows 7
(Dbg)(1) http://crbug.com/612523

Original issue's description:
> views: Initialize DesktopScreenX11::primary_display_index_.
> 
> The new field was introduced in crrev.com/391625, but this field was left
> uninitialized in this ctor.
> 
> BUG=42313
> 
> Committed: https://crrev.com/71017aa70fb2feaa60c8178e253b100969800b63
> Cr-Commit-Position: refs/heads/master@{#393985}

TBR=sky@chromium.org,sadrul@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=42313
==========

to

==========
Revert of views: Initialize DesktopScreenX11::primary_display_index_. (patchset
#1 id:1 of https://codereview.chromium.org/1983863003/ )

Reason for revert:
Speculative revert to see if reverting this affects the tests on Windows 7
(Dbg)(1) http://crbug.com/612523

Original issue's description:
> views: Initialize DesktopScreenX11::primary_display_index_.
>
> The new field was introduced in crrev.com/391625, but this field was left
> uninitialized in this ctor.
>
> BUG=42313
>
> Committed: https://crrev.com/71017aa70fb2feaa60c8178e253b100969800b63
> Cr-Commit-Position: refs/heads/master@{#393985}

TBR=sky@chromium.org,sadrul@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=42313

Committed: https://crrev.com/e6688b1f2a74cd5055938f0fe05322ef011e7036
Cr-Commit-Position: refs/heads/master@{#394266}
==========

[commit-bot: I haz the power, 2016-05-17 23:22:22]

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

[sadrul, 2016-05-17 23:28:54]

On 2016/05/17 23:18:27, qyearsley wrote:
> Created Revert of views: Initialize DesktopScreenX11::primary_display_index_.

It's an x11 patch. This code doesn't even build on win32.

[qyearsley, 2016-05-17 23:42:13]

On 2016/05/17 at 23:28:54, sadrul wrote:
> On 2016/05/17 23:18:27, qyearsley wrote:
> > Created Revert of views: Initialize
DesktopScreenX11::primary_display_index_.
> 
> It's an x11 patch. This code doesn't even build on win32.

Makes sense; will reland

[qyearsley, 2016-05-17 23:43:06]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1985303002/ by qyearsley@chromium.org.

The reason for reverting is: That patch couldn't have affected tests on Windows
7 since doesn't build on Windows..