Confirmed users
146
edits
DOM/ContentIterator Issues: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 1: | Line 1: | ||
Content Iterator, we've discovered, has a design flaw in it responsible for [https://bugzilla.mozilla.org/show_bug.cgi?id=157373 several] [https://bugzilla.mozilla.org/show_bug.cgi?id=302775 bugs] in Mozilla. In essence, nsContentIterator and its friends assume (incorrectly) a nsIContent interface is available for every nsIDOMNode object they receive. | Content Iterator, we've discovered, has a design flaw in it responsible for [https://bugzilla.mozilla.org/show_bug.cgi?id=157373 several] [https://bugzilla.mozilla.org/show_bug.cgi?id=302775 bugs] in Mozilla. In essence, nsContentIterator and its friends assume (incorrectly) a nsIContent interface is available for every nsIDOMNode object they receive. | ||
The truth of the matter is, there are four DOM node types (possibly five, if you count XPathResult) | The truth of the matter is, there are four non-content DOM node types (possibly five, if you count XPathResult): | ||
* Attr | * Attr | ||