Closed Bug 842376 Opened 13 years ago Closed 13 years ago

Update HTMLImageElement's named constructor to use optional arguments

Categories

(Core :: DOM: Core & HTML, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla22

People

(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)

References

Details

Attachments

(1 file)

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.
(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+
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: