[Webkit-unassigned] [Bug 14935] ResourceLoader should call ResourceHandle::setClient(0) after checking it's still the ResourceHandle's client

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Aug 13 17:47:02 PDT 2007


http://bugs.webkit.org/show_bug.cgi?id=14935





------- Comment #5 from aroben at apple.com  2007-08-13 17:47 PDT -------
(In reply to comment #4)
> This can happen if a WebKit embedder calls ResourceLoader::handle(),
> a public method, and then call ResourceHandle::setClient on the
> returned ResourceHandle to set its client to something else.  I'd
> like to know if this usage of ResourceHandle::setClient is allowed.
> If not, perhaps ResourceHandle::setClient should be constrained
> to prevent a WebKit embedder from making this mistake.

   I don't think there's a way to make this happen through the WebKit API, so I
don't think it's possible for a "WebKit embedder" to get into this situation.
Perhaps you're talking about someone who is making changes to WebCore/WebKit
itself? If so, seeing the patches that are running into this situation would
make this whole discussion much clearer.


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



More information about the webkit-unassigned mailing list