Image() constructor's arguments should not have default values

Image() constructor's arguments should not have default values

Implementing them with [Default=Undefined] is equivalent to implementing
them with zero as the default value, which is semi-correct; the created
element's 'width' and 'height' IDL attributes should be zero.

However, per spec, calling Image() without the arguments should create
an element without the 'width' and 'height' content attributes, whereas
calling Image() with the arguments should create an element with the
content attributes, including if the argument values were zero. Thus we
need to distinguish between no argument and argument being zero.

BUG=253777
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=187973

[Jens Widell, 2015-01-07 13:28:07]

jl@opera.com changed reviewers:
+ haraken@chromium.org

[Jens Widell, 2015-01-07 13:28:08]

PTAL

[haraken, 2015-01-07 14:09:41]

LGTM, assuming the new behavior aligns with Firefox.

[Jens Widell, 2015-01-07 14:17:06]

On 2015/01/07 14:09:41, haraken wrote:
> LGTM, assuming the new behavior aligns with Firefox.

Thanks for review!

All the new (and other relevant) checks in custom-constructor.js passes in
Firefox. (Some other stuff fails in Firefox for various reasons.)

[Jens Widell, 2015-01-07 14:17:16]

The CQ bit was checked by jl@opera.com

[commit-bot: I haz the power, 2015-01-07 14:18:18]

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

[commit-bot: I haz the power, 2015-01-07 15:29:41]

Committed patchset #1 (id:1) as
https://src.chromium.org/viewvc/blink?view=rev&revision=187973