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. widget/src/xpwidgets/nsBaseWidget.cpp: View change log or Blame annotations line 566
I don't know anything about this. I've never written any code in this file.
I looked up the author, looks like Mike Judge.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → WONTFIX
Based on mike's comments, marking as verified won't fix.
If no one minds, I'll fix this after beta. There is a client-wide move toward nsISimpleEnumerator, it's been all over the xpcom newsgroup and in the mozilla architecture meeting. It isn't going to get constant fanfare, but it has already happened to a great degree (query bugzilla for resolved bugs to do with NS_COMFALSE). The mailnews guys have done much great work. Why stop short of completion? /be
Good. We should get rid of all this crap like NS_COMFALSE and nsIEnumerator. I'm glad someone's doing it.
I think braddr is driving this to a good conclusion throughout the tree. /be
Since this cleanup task is not an M15 stability blocker, I'm pushing it off to M16 (to help allow us to branch for M15).
Target Milestone: M15 → M16
NS_COMFALSE is no longer in /widget/src/xpwidgets/nsbasewidget.cpp Search shows NO listing for NS_COMFALSE in /widget branch This bug can be resolved fixed.
M16 has been out for a while now, these bugs target milestones need to be updated.
Moving out a few milestones.
Target Milestone: M16 → M18
Milestone 0.8 has been released. We should either resolve this bug or update its milestone.
Moving to XP Toolkit/Widgets component.
Component: Layout → XP Toolkit/Widgets: Trees
I think this one was fixed long ago, so could we close it now ? and perhaps #11592, #11595 and some more in #8929... /jc
i count 20 users that usually doesn't match my definition of eliminate (it might match decimate but ...)
*** This bug has been marked as a duplicate of 8929 ***
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago → 16 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.