Fallback to use output_index when searching for internal display

Fallback to use output_index when searching for internal display

BUG=180100
TEST=manual


Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=186322

[oshima, 2013-03-05 22:49:39]

haixia, can you test this on lucas? I don't have one
right now.

[hshi1, 2013-03-05 22:58:40]

Tested to fix the problem on Daisy.

For the internal display I get an ID of "0", I suppose that is expected as the
index is 0 and both manufacturer/product codes are 0 too.

LGTM (but please fix the nit for the bug #). Thanks!

https://codereview.chromium.org/12491005/diff/2001/ash/display/display_change...
File ash/display/display_change_observer_x11.cc (right):

https://codereview.chromium.org/12491005/diff/2001/ash/display/display_change...
ash/display/display_change_observer_x11.cc:123: // Fallback to output index.
crbug.com/18100
nit: bug number should be 180100

[oshima, 2013-03-05 23:36:13]

You get ID == 0 as the output index of the internal display
is 0. This won't change so this is probably just fine as is.

https://codereview.chromium.org/12491005/diff/2001/ash/display/display_change...
File ash/display/display_change_observer_x11.cc (right):

https://codereview.chromium.org/12491005/diff/2001/ash/display/display_change...
ash/display/display_change_observer_x11.cc:123: // Fallback to output index.
crbug.com/18100
On 2013/03/05 22:58:40, hshi1 wrote:
> nit: bug number should be 180100

Done.

[commit-bot: I haz the power, 2013-03-05 23:37:33]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/oshima@chromium.org/12491005/7001

[commit-bot: I haz the power, 2013-03-06 01:43:53]

Change committed as 186322