Closed Bug 230439 Opened 22 years ago Closed 22 years ago

Remove anonymous nodeinfomanager and other cleanup

Categories

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

defect

Tracking

()

RESOLVED FIXED
mozilla1.7alpha

People

(Reporter: peterv, Assigned: peterv)

Details

Attachments

(2 files)

I'm working on doing away with nsINodeInfoManager and here's a first step, removing the anonymous nodeinfomanager. This involves one change in editor code to ensure a document is passed when creating a FragmentContentSink (not having a document at that point is already an error according to the editor code, I've just made the code ensure it at that point). Patches coming.
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.7alpha
Attachment #138654 - Flags: superreview?(jst)
Attachment #138654 - Flags: review?(caillon)
Attachment #138655 - Flags: superreview?(jst)
Attachment #138655 - Flags: review?(caillon)
Comment on attachment 138654 [details] [diff] [review] Kill anonymous nodeinfomanager - In NS_NewDocumentFragment(): { NS_ENSURE_ARG_POINTER(aInstancePtrResult); + nsINodeInfoManager *nimgr = aOwnerDocument->GetNodeInfoManager(); I'd rather see us check that aOwnerDocument is non-null here than wasting code on checking that aInstancePtrResult is non-null. sr=jst
Attachment #138654 - Flags: superreview?(jst) → superreview+
Comment on attachment 138655 [details] [diff] [review] Share CreateElement code Nice! sr=jst
Attachment #138655 - Flags: superreview?(jst) → superreview+
Attachment #138654 - Flags: review?(caillon) → review+
Attachment #138655 - Flags: review?(caillon) → review+
I'll do the remaining work in bug 236408.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
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: