Reject promise with InvalidStateError instead of null in createImageBitmap(Blob)

Reject promise with InvalidStateError instead of null in createImageBitmap(Blob)

Right now, the createImageBitmap(Blob) reject promise with null when
the input image cannot be decoded, for example, the input image is a SVG
image. A recently change is made to the specs here:
https://github.com/whatwg/html/pull/884
which states that we should reject the promise with InvalidStateError
insetad of null.

This CL changes it such that it will reject the promise with a
InvalidStateError.

BUG=596251
Committed: https://crrev.com/672ae7a2037e92b305054849f31a7bb4fb873823
Cr-Commit-Position: refs/heads/master@{#384045}

[xidachen, 2016-03-30 15:32:27]

xidachen@chromium.org changed reviewers:
+ junov@chromium.org

[xidachen, 2016-03-30 15:32:28]

PTAL

[Justin Novosad, 2016-03-30 15:43:42]

On 2016/03/30 15:32:28, xidachen wrote:
> PTAL

This is in response to a recent change in the spec, you should reference it in
the CL description. Other than that, lgtm

[xidachen, 2016-03-30 15:46:31]

Description was changed from

==========
Reject promise with InvalidStateError instead of null in createImageBitmap(Blob)

Right now, the createImageBitmap(Blob) reject promise with null when
the input image cannot be decoded, for example, the input image is a SVG
image. This CL changes it such that it will reject the promise with a
InvalidStateError instead of null.

BUG=596251
==========

to

==========
Reject promise with InvalidStateError instead of null in createImageBitmap(Blob)

Right now, the createImageBitmap(Blob) reject promise with null when
the input image cannot be decoded, for example, the input image is a SVG
image. A recently change is made to the specs here:
https://github.com/whatwg/html/pull/884
which states that we should reject the promise with InvalidStateError
insetad of null.

This CL changes it such that it will reject the promise with a
InvalidStateError.

BUG=596251
==========

[xidachen, 2016-03-30 15:46:36]

The CQ bit was checked by xidachen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-03-30 15:47:01]

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

[xidachen, 2016-03-30 16:31:16]

The CQ bit was unchecked by xidachen@chromium.org

[xidachen, 2016-03-30 16:31:34]

The CQ bit was checked by xidachen@chromium.org

[commit-bot: I haz the power, 2016-03-30 16:31:58]

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

[commit-bot: I haz the power, 2016-03-30 19:12:22]

Description was changed from

==========
Reject promise with InvalidStateError instead of null in createImageBitmap(Blob)

Right now, the createImageBitmap(Blob) reject promise with null when
the input image cannot be decoded, for example, the input image is a SVG
image. A recently change is made to the specs here:
https://github.com/whatwg/html/pull/884
which states that we should reject the promise with InvalidStateError
insetad of null.

This CL changes it such that it will reject the promise with a
InvalidStateError.

BUG=596251
==========

to

==========
Reject promise with InvalidStateError instead of null in createImageBitmap(Blob)

Right now, the createImageBitmap(Blob) reject promise with null when
the input image cannot be decoded, for example, the input image is a SVG
image. A recently change is made to the specs here:
https://github.com/whatwg/html/pull/884
which states that we should reject the promise with InvalidStateError
insetad of null.

This CL changes it such that it will reject the promise with a
InvalidStateError.

BUG=596251
==========

[commit-bot: I haz the power, 2016-03-30 19:12:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-30 19:13:49]

Description was changed from

==========
Reject promise with InvalidStateError instead of null in createImageBitmap(Blob)

Right now, the createImageBitmap(Blob) reject promise with null when
the input image cannot be decoded, for example, the input image is a SVG
image. A recently change is made to the specs here:
https://github.com/whatwg/html/pull/884
which states that we should reject the promise with InvalidStateError
insetad of null.

This CL changes it such that it will reject the promise with a
InvalidStateError.

BUG=596251
==========

to

==========
Reject promise with InvalidStateError instead of null in createImageBitmap(Blob)

Right now, the createImageBitmap(Blob) reject promise with null when
the input image cannot be decoded, for example, the input image is a SVG
image. A recently change is made to the specs here:
https://github.com/whatwg/html/pull/884
which states that we should reject the promise with InvalidStateError
insetad of null.

This CL changes it such that it will reject the promise with a
InvalidStateError.

BUG=596251

Committed: https://crrev.com/672ae7a2037e92b305054849f31a7bb4fb873823
Cr-Commit-Position: refs/heads/master@{#384045}
==========

[commit-bot: I haz the power, 2016-03-30 19:13:50]

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