Open Bug 1024193 Opened 6 years ago Updated 10 months ago

Maybe |node| is uninitialized in some cases in nsContentSubtreeIterator::Init

Categories

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

defect

Tracking

()

People

(Reporter: mccr8, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: coverity, Whiteboard: [CID 749683])

Coverity has some extremely long series of conditions under which it says |node| is uninitialized.  I don't really want to try to understand the sequence, so I propose we just initialize node to null or something.  I can dig out the actual sequence if somebody really wants to know.
Keywords: coverity
Whiteboard: [CID 749683]
There is no 'node' in that method.
Oops, I got confused...
Summary: Maybe |node| is uninitialized in some cases in nsContentUtils::GetAncestorsAndOffsets → Maybe |node| is uninitialized in some cases in nsContentSubtreeIterator::Init
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.
Priority: -- → P5
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.