Johnny Stenback wrote:
Yeah, though I think I'd name the setter SetMayHaveFrame to not make it seem like it implies that you're required to keep this state up-to-date as frames go away.
Makes sense.
So for textnodes, I guess we can make the getter return parent->MayHaveFrame()
Yep.
and the setter a no-op
Yep.
and maybe even assert if someone ever calls it?
I'd rather not, since I was going to call the setter in nsFrame::Init() and be done with it... ;)
In fact, I'm tempted to implement the getter and setter on nsIContent itself (setter no-op, getter returns true) and then just override in the classes we care about....
Ok, makes sense. I can deal with that.
-Boris
-- jst _______________________________________________ mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
