e686e7b714
Bug 324918: Make nsHTMLSelectElement deal better with options in unknown children. r=bz sr=jst
2006-03-01 01:10:20 +00:00
be9a220c32
Try to fix brad bustage by backing out these declarations, which aren't on the equivalent nsVoidArray symbols
2005-11-08 20:55:30 +00:00
1172c33dfc
Bug 305949 Part 1 - Separate the frozen XPCOM exports with the XPCOM_API macro; add compatibility methods to the frozen string API; convert most of the tests/tools to use the xpcom glue when appropriate r=darin This checking does not actually stop exporting the nonfrozen methods yet, pending a bunch of test cleanup throughout the tree.
2005-11-08 18:17:49 +00:00
b3322114f4
nsCOMArray::RemoveObjectAt fails to remove nulls correctly. Bug 265772,
...
r=darin, sr=dbaron
2005-11-02 16:05:25 +00:00
b04d4ee164
Make ReplaceObjectAt a little safer. Bug 227780, r=timeless, sr=alecf
2005-11-02 16:05:18 +00:00
58618cb325
nsCOMArray should not use nsDerivedSafe. b=221525 r=bryner
2005-11-02 16:05:13 +00:00
100f075a91
Bug 198685 need nsCOMArray function like IndexOf that checks COM object identity p=bsmedberg@covad.net r=alecf (no sr needed)
2005-11-02 16:05:09 +00:00
b0a45e4a36
fix build bustage
2005-11-02 16:05:08 +00:00
4678c4c82b
fix an assertion from nsCOMArray where ReplaceElementAt() wouldn't property extend the array because we were just using ObjectAt()
...
residual stuff from bug 197827, which caused an assertion browsing frame
patch by keeda@hotpop.com , r/sr=alecf
2005-11-02 16:04:49 +00:00
33ca821d9e
Bug 162115: Make nsCOMArray return nsDeriviedSafes to avoid bad addrefs/releases
...
r=bz sr=alecf
2005-11-02 16:04:48 +00:00
44aca08ea8
Make the nsCOMArray destructor release all the objects. Bug 178813,
...
r=bbaetz, sr=rpotts
2005-11-02 16:04:47 +00:00
5e587fc996
nsCOMArray_base copy constructor should not assert. Bug 178534,
...
r=dougt, sr=alecf
2005-11-02 16:04:46 +00:00
32a5133307
Add AppendObjects/InsertObjectsAt to nsCOMArray. Bug 175137,
...
r=timeless, sr=alecf, a=dbaron
2005-11-02 16:04:44 +00:00
6a1573eb45
Fix for bug 174443. nsCOMArray::ApendObject() shouldn't addref
...
r=dougt, sr=alecf, a=asa
2005-11-02 16:04:42 +00:00
f449844bf0
OS/2 bustage - need PR_CALLBACK
2005-11-02 16:04:41 +00:00
e3d65d86d6
- fix ReplaceObjectAt to properly account for existing null entries
...
- make nsCOMArray_base accessible from nsCOMArray<T> so that a nsCOMArray<T> can passed to NS_NewArray
for bug 162115, not part of build
2005-11-02 16:04:37 +00:00
faf8498d08
not part of build, more for bug 162115:
...
- fix some spelling, add documentation
- add NS_NewArray(), including one that takes an existing nsCOMArray<T>
- implement copy constructor for nsCOMArray_base, so that NS_NewArray can work
not part of build
2005-11-02 16:04:36 +00:00
08f5ef2664
match up some reviewers comments:
...
- tri-license with MPL, not NPL
- be consistent with policy on null in the array (it is allowed)
- move Clear() into implementation file, and hide static callback there too
- make sure to AddRef() on the way out of nsArray::IndexOf()
- handle failure of ReplaceElementAt more gracefully
bug 162115, not part of build yet
2005-11-02 16:04:35 +00:00
29453f3e5e
continuing work in progress on nsCOMArray<T> - take darin's suggestion and move all nsISupports-related code into a non-template base class nsCOMArray_base. This allows the generated template to be paper thin (or really, non-existent!)
...
Then, we move some of the non-trivial methods of this class into a .cpp file
2005-11-02 16:04:34 +00:00
cvshook%sicking.cc
bsmedberg%covad.net
bzbarsky%mit.edu
dbaron%dbaron.org
neil%parkwaycc.co.uk
alecf%netscape.com
sicking%bigfoot.com
varga%netscape.com
mkaply%us.ibm.com