Reland: Allow high-res bitmaps to be passed in from notifications API.

Reland: Allow high-res bitmaps to be passed in from notifications API.

Previously the custom binding in JS would prevent an image that's larger
than the size of the template from being sent to the browser process.
This relaxes the maximum to be the largest supported scale factor of the machine.

TBR=kalman@chromium.org,dimich@chromium.org
BUG=239676
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=274730

[dewittj, 2014-05-22 23:47:30]

csharp: Please take a look at isolate changes.

kalman (TBR), dimich (TBR): no new code, just fixing isolated test failures.

This is relanding https://codereview.chromium.org/256503004

[dewittj, 2014-05-23 22:49:53]

csharp: ping

[csharp, 2014-05-26 13:05:54]

https://codereview.chromium.org/291193009/diff/20001/chrome/unit_tests.isolate
File chrome/unit_tests.isolate (right):

https://codereview.chromium.org/291193009/diff/20001/chrome/unit_tests.isolat...
chrome/unit_tests.isolate:105:
'<(PRODUCT_DIR)/test_data/chrome/renderer/resources/extensions/',
Do the tests not need access to these files when running on Linux?

[dewittj, 2014-05-27 16:16:42]

https://codereview.chromium.org/291193009/diff/20001/chrome/unit_tests.isolate
File chrome/unit_tests.isolate (right):

https://codereview.chromium.org/291193009/diff/20001/chrome/unit_tests.isolat...
chrome/unit_tests.isolate:105:
'<(PRODUCT_DIR)/test_data/chrome/renderer/resources/extensions/',
On 2014/05/26 13:05:55, csharp wrote:
> Do the tests not need access to these files when running on Linux? 

Tests don't seem to require this on linux, and I'm cargo culting the way google
now and print preview got their gtestjs files in.

Should I just put it in a platform-independent place?

[csharp, 2014-05-27 16:56:34]

lgtm

https://codereview.chromium.org/291193009/diff/20001/chrome/unit_tests.isolate
File chrome/unit_tests.isolate (right):

https://codereview.chromium.org/291193009/diff/20001/chrome/unit_tests.isolat...
chrome/unit_tests.isolate:105:
'<(PRODUCT_DIR)/test_data/chrome/renderer/resources/extensions/',
On 2014/05/27 16:16:43, dewittj wrote:
> On 2014/05/26 13:05:55, csharp wrote:
> > Do the tests not need access to these files when running on Linux? 
> 
> Tests don't seem to require this on linux, and I'm cargo culting the way
google
> now and print preview got their gtestjs files in.
> 
> Should I just put it in a platform-independent place?

If the tests don't need these files for linux, then this is good as is.

[dewittj, 2014-06-02 17:33:02]

technically the gjsunit tests run on all platforms.  So I'll move it up.

[dewittj, 2014-06-02 17:57:57]

The CQ bit was checked by dewittj@chromium.org

[commit-bot: I haz the power, 2014-06-02 17:58:39]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dewittj@chromium.org/291193009/60001

[commit-bot: I haz the power, 2014-06-02 21:19:44]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel/bu...)
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)

[commit-bot: I haz the power, 2014-06-02 21:23:40]

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

[commit-bot: I haz the power, 2014-06-02 21:23:40]

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

[dewittj, 2014-06-02 21:24:13]

The CQ bit was checked by dewittj@chromium.org

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

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dewittj@chromium.org/291193009/60001

[commit-bot: I haz the power, 2014-06-03 01:51:47]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel/bu...)
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)

[commit-bot: I haz the power, 2014-06-03 02:52:58]

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

[commit-bot: I haz the power, 2014-06-03 02:52:59]

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

[dewittj, 2014-06-03 20:39:33]

The CQ bit was checked by dewittj@chromium.org

[commit-bot: I haz the power, 2014-06-03 20:40:24]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dewittj@chromium.org/291193009/80001

[commit-bot: I haz the power, 2014-06-04 01:31:03]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)

[commit-bot: I haz the power, 2014-06-04 08:40:49]

Change committed as 274730