Update HTMLImageElement's named constructor to use optional arguments

RESOLVED FIXED in mozilla22

Status

()

Core
DOM
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Ehsan, Assigned: Ehsan)

Tracking

Trunk
mozilla22
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 715221 [details] [diff] [review]
Patch (v1)

See https://www.w3.org/Bugs/Public/show_bug.cgi?id=20554
Attachment #715221 - Flags: review?(bzbarsky)
Where is the foundation of this change? Even the latest spec doesn't use optional arguments.
http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-1.html#the-img-element
Please file a spec bug, at least.
Sorry, I missed the URL.
Hm, W3C HTML5 has even more discrepancy from WHATWG HTML?
http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#the-img-element
However the IDL refer the WHATWG's version, not W3C's one.
(Assignee)

Comment 4

5 years ago
(In reply to comment #3)
> Hm, W3C HTML5 has even more discrepancy from WHATWG HTML?
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#the-img-element
> However the IDL refer the WHATWG's version, not W3C's one.

Doesn't Hixie pull these types of changes in to the WHATWG spec too?
Comment on attachment 715221 [details] [diff] [review]
Patch (v1)

r=me
Attachment #715221 - Flags: review?(bzbarsky) → review+
https://hg.mozilla.org/mozilla-central/rev/68359d79d869
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
You need to log in before you can comment on or make changes to this bug.