Open Bug 361220 Opened 18 years ago Updated 2 years ago

Various assertions when failing to find a string with a leading space

Categories

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

defect

Tracking

()

People

(Reporter: neil, Unassigned)

Details

Steps to reproduce problem: 1. Open the find dialog 2. Type in a space then a random string 3. Click Find I get up to three assertions. The last one is always "No first node!" in nsContentIterator.cpp while the others (which I'm not so confident of reproducing) are "Text content wasn't nsIContent!" in nsFind.cpp
Stack backtrace: nsContentIterator::First() NS_ASSERTION(mFirst, "No first node!"); nsFindContentIterator::Reset() mOuterIterator->First(); nsFindContentIterator::First() Reset(); nsFind::InitIterator(nsIDOMRange * aSearchRange=0x082f20b8) mIterator->First(); nsFind::NextNode(nsIDOMRange * aSearchRange=0x07db5df8, nsIDOMRange * aStartPoint=0x07d5cf20, nsIDOMRange * aEndPoint=0x07cdc310, int aContinueOk=1) rv = InitIterator(newRange); nsFind::Find(const unsigned short * aPatText=0x08298ff0, nsIDOMRange * aSearchRange=0x07db5df8, nsIDOMRange * aStartPoint=0x07d5cf20, nsIDOMRange * aEndPoint=0x07cdc310, nsIDOMRange * * aRangeRet=0x0012d188) NextNode(aSearchRange, aStartPoint, aEndPoint, PR_TRUE); nsWebBrowserFind::SearchInFrame(nsIDOMWindow * aWindow=0x068dcf28, int aWrapping=0, int * aDidFind=0x0012d440) rv = mFind->Find(mSearchString.get(), searchRange, startPt, endPt, getter_AddRefs(foundRange)); nsWebBrowserFind::FindNext(int * outDidFind=0x0012d440) rv = SearchInFrame(searchFrame, PR_FALSE, outDidFind);
Assignee: traversal-range → nobody
QA Contact: ian → traversal-range
Component: DOM: Traversal-Range → DOM: Core & HTML
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
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.