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 27356 - Define [LegacyNewObject]
Summary: Define [LegacyNewObject]
Status: NEW
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on: 27355
Blocks: 24652
  Show dependency tree / graph
 
Reported: 2014-11-17 19:59 UTC by Anne
Modified: 2014-11-17 20:19 UTC (History)
3 users (show)

See Also:

Attachments

Description Anne 2014-11-17 19:59:53 UTC 
For [NewObject] we can emulate JavaScript, but we likely need to keep something akin to [LegacyNewObject] around for Node-creating methods, such as createElement(). (New element creation mechanisms would not have to use this.)

See http://lists.w3.org/Archives/Public/public-script-coord/2014OctDec/0197.html and surrounding thread.
Comment 1 Boris Zbarsky 2014-11-17 20:19:05 UTC 
> New element creation mechanisms would not have to use this.

I disagree.  I think it would be really surprising for people to create an element with a given ownerDocument and have it start out with a different Realm than that ownerDocument started with.