[Webkit-unassigned] [Bug 27444] Wrong FrameLoader::activeDocumentLoader when loading an invalid URL.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=27444


Antonio Gomes (tonikitoo) <tonikitoo at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hausmann at webkit.org




--- Comment #8 from Antonio Gomes (tonikitoo) <tonikitoo at gmail.com>  2009-07-21 08:39:42 PDT ---
(In reply to comment #7)
> > > What happens if you try using activeDocumentLoader()->mainDocumentError()?
> > 
> > as you said, I could use that *if* activeDocumentLoader() returns the resource
> > loader corresponding to the failing loader. I will check ...
> 
> I don't have time to run the experiment right now, but I think
> mainResourceError might be set on the current document loader, even in this
> case, along with unreachableURL.  

hum, DocumentLoader::setMainResourceError() gets called in the right (failing)
loader, ok. It calls FrameLoader::setMainDocumentError(error), which on its
turn calls FrameLoaderClientXXX()::setMainDocumentError ...

that can be possibly a bridge. I could try emit a signal from it to be catch in
QWebFrame, where I need to know if the load was successful or not.

if it is not successful (case where I am stuck on) I can get the originalUrl
from calling FrameLoader::outgoingReferrer()

simon, what do you think ?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.