On Fri, 22 Jan 1999, Waldo Bastian wrote: >David Faure wrote: >> >> > I have kfm and kfmw. :) >> :) >> >> > My guess is that an extra vspace_inserted=true somewhere could help.. >> Lars' commit did that. >> and >> @@ -3327,7 +3327,8 @@ void KHTMLWidget::parseH( HTMLClueV *_cl >> } >> } >> // Start a new flow box >> - newFlow(_clue); >> + if(!flow) >> + newFlow(_clue); >> >> flow->setHAlign( align ); > >Doesn't this bring you into trouble when you already have flow? >I mean... you call flow->setHAlign( align) which will also affect >that part of the flow which is above the header. Short excerpt from the code: vspace_inserted = insertVSpace( _clue, vspace_inserted ); HTMLClue::HAlign align = divAlign; .... parsing of attributes cutted // Start a new flow box if(!flow) newFlow(_clue); flow->setHAlign( align ); I don't think it'll make any problems. vspace_inserted is usually false, if you already started filling the flow (e.g. with text). So insertVSpace will create a new flow anyway. The newFlow is only needed in case we have vspace_inserted=true && flow == 0. I anyway tried it with quite some pages, and couldn't find any problems with headers. > >I would think that the right solution would be not to create >a flow explicitly during the handling of "