We should eliminate the NS_COMFALSE madness once and for all. Here's a list of offending uses in your module -- please pass the bug along if there's someone else who should deal with it. rdf/content/src/nsXULAttributes.cpp: View change log or Blame annotations line 558
Moving out non-critical tasks.
maybe scc'll do it.
Not many of these left, now, as most cases were replaced with | NS_ENUMERATOR_FALSE|, which at least makes the behavior in those situations somewhat understandable.
mass re-assigning to my new bugzilla account
Up todate list /rdf/content/src/nsXULElement.cpp line 3971 -- rv = nsClassList::HasClass(mPrototype->mClassList, aClass) ? NS_OK : NS_COMFALSE; /rdf/content/src/nsXULAttributes.cpp line 855 -- return nsClassList::HasClass(mClassList, aClass) ? NS_OK : NS_COMFALSE;
All remaining instances of NS_COMFALSE in the rdf code followed XUL into content/; inspection of rdf/ yields no further instances. Unless nsXULElement.cpp etc are still considered part of the RDF component, this bug can be closed.
Some |NS_COMFALSE| still exists in the tree, but not much. See the URL above for a search. Re-assigning to XPCOM owner.
not that important. -> future
*** This bug has been marked as a duplicate of 8929 ***
Verified dupe Sorry for the spam