Closed Bug 734029 Opened 14 years ago Closed 14 years ago

Move nsJSContext::{Set,Create}OuterObject to nsGlobalWindow

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla14

People

(Reporter: Ms2ger, Assigned: Ms2ger)

References

Details

Attachments

(1 file)

CreateOuterObject only has one caller, nsGlobalWindow::SetNewDocument. SetOuterObject has two, CreateOuterObject and SetNewDocument. It seems better to just move that code to nsGlobalWindow.cpp. The only nsJSContext state these functions use is mContext, which we can get through GetNativeContext(). This will also allow us to make NS_NewOuterWindowProxy private to nsGlobalWindow.cpp.
Depends on: 733606
Assignee: nobody → Ms2ger
Comment on attachment 604512 [details] [diff] [review] Patch v1 >diff --git a/dom/base/nsIScriptContext.h b/dom/base/nsIScriptContext.h >--- a/dom/base/nsIScriptContext.h >+++ b/dom/base/nsIScriptContext.h >@@ -89,16 +89,18 @@ NS_DEFINE_STATIC_IID_ACCESSOR(nsIScriptC > class nsIScriptContext : public nsIScriptContextPrincipal > { > public: > NS_DECLARE_STATIC_IID_ACCESSOR(NS_ISCRIPTCONTEXT_IID) > > /* Get the ID of this language. */ > virtual PRUint32 GetScriptTypeID() = 0; > >+ virtual void SetGlobalObject(nsIScriptGlobalObject* aGlobalObject) = 0; >+ It would be nice if this didn't have to be virtual, but maybe that de-agnostification is a task for another day. Nice patch - sorry for the delay. I wanted to take some time to really grok this stuff. r=bholley
Attachment #604512 - Flags: review?(bobbyholley+bmo) → review+
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: