Closed
Bug 305326
Opened 20 years ago
Closed 20 years ago
nsXPathResult::IterateNext() does not advance to next result
Categories
(Core :: XSLT, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: Mook, Assigned: peterv)
References
Details
(Keywords: fixed1.8, regression)
Attachments
(2 files)
|
329 bytes,
text/html
|
Details | |
|
874 bytes,
patch
|
axel
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
(Will attach testcase in a moment)
Calling iterateNext() on an XPath result no longer advances to the next result;
therefore all xpath queries expecting a list become infinite loops.
Steps to reproduce:
1. Load testcase
Expected results:
Script terminates immediately; window title is "0"
Actual Results:
Script loops infinitely, until the warning comes up (at which point it can be
aborted); window title is non-zero (in my case, "8191")
Regression range: between trunk win32 nightlies of 2005-08-17-13 to
2005-08-18-07 - suspecting the checkin from 2005-08-18 02:14 as
nsXPathResult::IterateNext() appears to no longer increment mCurrentPos.
Updated•20 years ago
|
Attachment #193296 -
Flags: review?(axel) → review+
| Assignee | ||
Updated•20 years ago
|
Attachment #193296 -
Flags: superreview?(jst)
Updated•20 years ago
|
Keywords: regression
Comment 4•20 years ago
|
||
Comment on attachment 193296 [details] [diff] [review]
v1
sr=jst
Attachment #193296 -
Flags: superreview?(jst) → superreview+
| Assignee | ||
Updated•20 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•