Closed Bug 811663 Opened 12 years ago Closed 12 years ago

Create a DocumentFragment header

Categories

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

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla19

People

(Reporter: bzbarsky, Assigned: bzbarsky)

Details

Attachments

(2 files)

No description provided.
Actually, nevermind. This isn't doable because we use it in nsGenericHTMLElement. As long as I'm here, I'll just morph the bug.
Summary: Move FireNodeRemovedForChildren to nsDocumentFragment → Create a DocumentFragment header
Whiteboard: [need review]
Whiteboard: [need review]
Comment on attachment 681410 [details] [diff] [review] part 1. Rename nsDocumentFragment to mozilla::dom::DocumentFragment. >+ DocumentFragment *it = new DocumentFragment(nodeInfo.forget()); DocumentFragmeent* it =.. > if (!it) { > return NS_ERROR_OUT_OF_MEMORY; > } And while you're here, you could remove OOM check. >-DOMCI_NODE_DATA(DocumentFragment, nsDocumentFragment) You had to move this to elsewhere because of namespaces, right?
Attachment #681410 - Flags: review?(bugs) → review+
Attachment #681411 - Flags: review?(bugs) → review+
> And while you're here, you could remove OOM check. Done. > You had to move this to elsewhere because of namespaces, right? Correct.
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: