This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21209 - [Custom]: 4 Instantiating Custom Elements: parameters on createElement() doesn't need to be optional
Summary: [Custom]: 4 Instantiating Custom Elements: parameters on createElement() does...
Status: RESOLVED LATER
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 18511
  Show dependency tree / graph
 
Reported: 2013-03-07 08:11 UTC by Morrita Hajime
Modified: 2013-10-07 16:30 UTC (History)
0 users

See Also:

Attachments

Description Morrita Hajime 2013-03-07 08:11:19 UTC 
This is kinda editorial idea but...

> partial interface Document {
>     Element createElement(DOMString localName, optional DOMString typeExtension);
>     Element createElementNS(DOMString? namespace, DOMString qualifiedName, optional DOMString typeExtension);
> };

Since WebIDL supports overloading [1], typeExtension parameter on these API
doesn't need to be overloaded and it doesn't need to call themselves "monkey patching".
It can be just a partial interface, which provides overloaded versions.


[1] http://dev.w3.org/2006/webapi/WebIDL/#idl-overloading