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 16455 - Using platform object example
Summary: Using platform object example
Status: NEW
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: All Windows 3.1
: P2 enhancement
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
Whiteboard: [v1]
Depends on:
Reported: 2012-03-20 19:06 UTC by Marcos Caceres
Modified: 2013-06-17 01:12 UTC (History)
2 users (show)

See Also:


Description Marcos Caceres 2012-03-20 19:06:36 UTC
Spec says: 

"Every platform object is associated with a global environment, just as the initial objects are. It is the responsibility of specifications using Web IDL to state which global environment (or, by proxy, which global object) each platform object is associated with."

This seems pretty important (maybe this should be a warning?). Can you please provide an example of some prose to use in another spec?
Comment 1 Cameron McCormack 2012-03-21 23:19:34 UTC
You're right, that's a sneaky requirement in there that probably nobody adheres to. :)  I wanted to avoid having spec writers define this, but I am not sure how to avoid it really.  We need to define for example that all objects returned from document.createElement are associated with the global environment that the document is associated with, while the objects returned from the contentDocument property on <iframe>s are associated with the global environment in the frame.

Not sure really what the best way for other specs to word this requirement is, yet...