Fix set_area sizes for RequestCopyOfOutput

Fix set_area sizes for RequestCopyOfOutput

Layers are in DIP space, we should use subrects in the same space
for RequestCopyOfOutput.

Also moved the force-device-scale command line option to its proper
place.  This ensures that the flag is set before the scale factors
are checked.  Previous tests were blindly passing due to the scale
factors not being supported.

The switch to DIP is here: https://codereview.chromium.org/311253004

BUG=

[powei, 2014-06-13 01:48:17]

PTAL.

Came across this while trying to fix related issue on Android.  We're going with
another fix for Android.  Please let me know if this is alright.

[danakj, 2014-06-13 15:14:04]

Thanks! This looks good, do you know why tests like
CompositingRenderWidgetHostViewTabCaptureHighDPI.CopyFromCompositingSurfaceVideoFrame
aren't failing before (or after) this change?

[powei, 2014-06-17 21:20:48]

On 2014/06/13 15:14:04, danakj wrote:
> Thanks! This looks good, do you know why tests like
>
CompositingRenderWidgetHostViewTabCaptureHighDPI.CopyFromCompositingSurfaceVideoFrame
> aren't failing before (or after) this change?

I think the command line for forcing the device-scale-factor was set too late,
which caused the tests to blindly pass.  Fix now included in this patch.

[danakj, 2014-06-17 21:45:26]

Thanks, so the test fails now without the changes to the frame host etc?

LGTM

[powei, 2014-06-17 21:55:11]

On 2014/06/17 21:45:26, danakj wrote:
> Thanks, so the test fails now without the changes to the frame host etc?
> 
> LGTM

Yes, it does.  


Thanks for reviewing.

[powei, 2014-06-17 21:55:18]

The CQ bit was checked by powei@chromium.org

[commit-bot: I haz the power, 2014-06-17 21:56:56]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/powei@chromium.org/333723004/20001

[powei, 2014-06-17 22:07:26]

+miu@ for content/browser/media/capture and content/browser/renderer_host/
OWNERS

[miu, 2014-06-17 22:59:18]

Very much lgtm!  :)

[commit-bot: I haz the power, 2014-06-18 08:28:34]

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

[commit-bot: I haz the power, 2014-06-18 08:28:34]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)

[danakj, 2014-06-18 15:19:24]

+sievers for OWNERS

[no sievers, 2014-06-18 21:18:42]

lgtm

[danakj, 2014-06-18 21:19:29]

The CQ bit was checked by danakj@chromium.org

[commit-bot: I haz the power, 2014-06-18 21:20:46]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/powei@chromium.org/333723004/20001

[powei, 2014-06-19 00:27:10]

On 2014/06/18 21:20:46, I haz the power (commit-bot) wrote:
> CQ is trying da patch. Follow status at
>  https://chromium-status.appspot.com/cq/powei@chromium.org/333723004/20001

These tests are failing on windows.  I'll look into this some more.

[commit-bot: I haz the power, 2014-06-19 10:40:34]

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

[commit-bot: I haz the power, 2014-06-19 10:40:35]

Try jobs failed on following builders:
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)

[miu, 2014-08-12 04:36:18]

powei: Did you still want to land this change?

[aelias_OOO_until_Jul13, 2014-08-12 18:28:52]

Powei left Google last week, unfortunately.  Someone else will need to look into
the windows try failures if we want to get this landed.

[miu, 2014-08-12 18:40:39]

On 2014/08/12 18:28:52, aelias wrote:
> Powei left Google last week, unfortunately.  Someone else will need to look
into
> the windows try failures if we want to get this landed.

Alright.  I'll take over this change.  Looks like we have all the LGTM's here,
and the commit box was checked, so the intention that this should land is clear.

[miu, 2014-08-12 19:14:21]

On 2014/08/12 18:40:39, miu wrote:
> Alright.  I'll take over this change.  Looks like we have all the LGTM's here,
> and the commit box was checked, so the intention that this should land is
clear.

Closed this issue, and started a continuation here:
https://codereview.chromium.org/462173002