Uses the correct scale factor for fallback images on iOS.

Uses the correct scale factor for fallback images on iOS.

Fallback images should always have a source scale factor of 1.0, even on 300P
devices.

BUG=413300, 415616
TEST=None

Committed: https://crrev.com/fb35e64ae36246591dbda7a1f90772c2ffc03d8b
Cr-Commit-Position: refs/heads/master@{#295703}

[lliabraa, 2014-09-19 12:42:47]

lliabraa@chromium.org changed reviewers:
+ lliabraa@chromium.org

[lliabraa, 2014-09-19 12:42:48]

lgtm

[rohitrao (ping after 24h), 2014-09-19 12:43:34]

rohitrao@chromium.org changed reviewers:
+ tony@chromium.org
- lliabraa@chromium.org

[rohitrao (ping after 24h), 2014-09-19 12:43:35]

+tony for OWNERS approval
+lliabraa, stuartmorgan FYI

One small fix, since I misunderstood how fallback images worked.  I also
reorganized the logic to be a little clearer.

[tony, 2014-09-19 13:31:00]

LGTM

[rohitrao (ping after 24h), 2014-09-19 13:32:41]

The CQ bit was checked by rohitrao@chromium.org

[commit-bot: I haz the power, 2014-09-19 13:34:07]

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

[commit-bot: I haz the power, 2014-09-19 14:34:15]

Committed patchset #3 (id:40001) as 3d9d6b1814865d64cea159a639e1e517f90f9260

[commit-bot: I haz the power, 2014-09-19 14:34:49]

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