[PATCH] When is KHTMLView done with rendering?

[David Faure]

On Friday 18 June 2004 17:44, Jeroen Wijnhout wrote:
> Hi,
> 
> It's me again :-) So the last patch did not fix all the bugs mentioned in 
> 57360 (it is actually a bunch of duplicate bugs). The problem lies in 
> detecting whether to skip loading the page and jump to the anchor directly, 
> or to jump after loading.
> 
> I propose the following:
> o If url.hasRef() is true, we should jump to an anchor, either delayed or 
> directly.
> o If urlcmp( url.url(), m_url.url(), true, true ) && !args.reload &&
>     !args.redirectedRequest() && !args.doPost() && !isFrameSet 
>   is true, we can be sure the page is not modified, reloading is not 
> necessary.
> I'm not too sure about the !isFrameSet, what is it for?

If this KHTMLPart is a frameset, then it contains child KHTMLParts 
(one per frame), which each have a KHTMLView. I think the idea of 
the code here is that the frame will handle the "jump to anchor" itself,
the frameset doesn't have to do anything.

-- 
David Faure -- faure at kde.org, dfaure at klaralvdalens-datakonsult.se
Qt/KDE/KOffice developer
Klarälvdalens Datakonsult AB, Platform-independent software solutions