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 17144 - [Custom]: What to do with constructable DOM objects?
Summary: [Custom]: What to do with constructable DOM objects?
Status: RESOLVED FIXED
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: 14968
  Show dependency tree / graph
 
Reported: 2012-05-21 22:31 UTC by Dimitri Glazkov
Modified: 2012-06-04 21:32 UTC (History)
1 user (show)

See Also:

Attachments

Description Dimitri Glazkov 2012-05-21 22:31:58 UTC 
If we want Image or Audio as prototypes, do we want to ever run their constructors? Intuitively, the answer seems like a 'no, we should not allow Image/Audio/Video/Option as valid element prototypes'.
Comment 1 Dominic Cooney 2012-05-22 01:39:03 UTC 
What is the fundamental problem with these?

It seems like you could do the same thing the parser does – creates the objects without executing their constructors per se.
Comment 2 Dimitri Glazkov 2012-06-04 21:32:41 UTC 
The new algorithm simply says create the object. You were right.