[Webkit-unassigned] [Bug 61946] FrameLoaderClient::didRunInsecureContent - no way to distinguish between blocked/run cases.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jun 6 16:08:27 PDT 2011


--- Comment #16 from Thomas Sepez <tsepez at chromium.org>  2011-06-06 16:08:27 PST ---
re: no URL in didDisplayInsecureContent().  Predates this CL, I'd like to leave it for now, as I believe changing that API will ripple through all the platforms as in the first patch I submitted.

re: tests.  Got a pointer to a layout test for one of the other allow options?  I didn't kick out anything with a few minutes of grepping.

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