[Webkit-unassigned] [Bug 102394] [Soup] Null-checking is required in cookiesEnabled

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Nov 15 10:04:52 PST 2012


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


Alexey Proskuryakov <ap at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #174455|review?, commit-queue?      |review-, commit-queue-
               Flag|                            |




--- Comment #6 from Alexey Proskuryakov <ap at webkit.org>  2012-11-15 10:06:40 PST ---
(From update of attachment 174455)
> The context could be null, when document or frame or loader is null

This can never happen in Navigator::cookieEnabled() - it checks that m_frame is not null, and others can never be null.

> and also FrameLoaderClient can't provide a proper networking context.

This looks like the root cause for your port. The client should provide a networking context, it makes no sense for a FrameLoader to not have one.

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



More information about the webkit-unassigned mailing list