2604465594
fix bug 388709 - "ASSERTION: Please remove this from the document properly: '!IsInDoc()'" with :after, floating :first-letter
...
Store the generated content as a nsCOMArray<nsIContent>* property on frames to make its clean-up on frame destruction less fragile.
r+sr=roc
2007-07-23 16:31:11 -07:00
d94c0df713
Remove nsIPresState (bug 279699). r+sr=roc.
2005-01-27 22:52:53 +00:00
b88692c5a1
Trying again to land support for content node properties (bug 253888). r=jst, sr=dbaron.
2004-08-24 18:50:29 +00:00
0c08074b27
Backing out 253888 again due to Tp regression plus another problem I noticed (frame properties not getting destroyed on frame destruction)
2004-08-22 07:10:50 +00:00
d86c91ac3a
Second try at landing support for content node properties (bug 253888). r=jst, sr=dbaron.
2004-08-22 04:58:44 +00:00
8c24cc7e63
Backing out bug 253888 until I can figure out how to fix the crash
2004-08-21 06:27:54 +00:00
11d98b36e5
Refactor the frame property code and use it for supporting properties on dom elements. Bug 253888, r=jst, sr=dbaron.
2004-08-21 05:09:50 +00:00
03e43cda2b
bug 218297 : disabled property of input elements is not stored in history
...
r=jkeiser sr=jst
2003-11-10 05:52:29 +00:00
476c30fdff
Make sure that Init() failures for image frames don't mean no alt text. Also
...
fixes a crasher when reframing fixed-pos frames.
This change adds an assertion in ConstructHTMLFrame that InitAndRestoreFrame
should succeed (unless it returns NS_ERROR_FRAME_REPLACED). This is an interim
change; eventually we want to bail out on errors, but there may be frame impls
that return errors in non-error conditions from Init() (eg nsFrameSetFrame did
that) and we're a little close to freeze.
Bug 202506, r=rbs, sr=roc+moz
2003-04-21 23:57:47 +00:00
8d87d5e285
Bug 8929: Kill NS_COMFALSE
...
r=peterv sr=bz
2002-11-25 11:21:22 +00:00
asqueella@gmail.com
bryner%brianryner.com
hpradhan%hotpop.com
bzbarsky%mit.edu
sicking%bigfoot.com