XPConnect Chrome Object Wrappers: Difference between revisions

XPConnect Chrome Object Wrappers (view source)

112 bytes removed , 17 September 2009

simplified explanation

874

edits

Revision as of 00:07, 17 September 2009 (view source) Varmaa (talk \| contribs) (added Cu.exposeToContent() call on functions that need wrapping) ← Older edit		Revision as of 00:15, 17 September 2009 (view source) Varmaa (talk \| contribs) (simplified explanation) Newer edit →
Line 17:		Line 17:
	</pre>		</pre>

	In the above example, <tt>foo()</tt> is wrapped by a COW when accessed by sandboxed code executed via <tt>Components.utils.evalInSandbox()</tt>. The object <tt>{bar: 5}</tt> is wrapped in an <tt>XPCSafeJSObjectWrapper</tt> before being passed into <tt>foo()</tt>~~, and whatever is returned from <tt>foo()</tt> and placed in <tt>result</tt> is usually wrapped in a COW as well~~.		In the above example, <tt>foo()</tt> is wrapped by a COW when accessed by sandboxed code executed via <tt>Components.utils.evalInSandbox()</tt>. The object <tt>{bar: 5}</tt> is wrapped in an <tt>XPCSafeJSObjectWrapper</tt> before being passed into <tt>foo()</tt>.