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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jun 3 12:39:11 PDT 2011


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





--- Comment #6 from Adam Barth <abarth at webkit.org>  2011-06-03 12:39:11 PST ---
> The chatty addMessage() messages pre-dated this change.  I think they should go, too.

Please don't remove those messages.  They're vey useful to developers.  We have many interactions with developers where we ask them to look for these messages and it usually results in them understanding the issue much better.

w.r.t. to the use case, we'd like to try blocking mixed content by default and then given users the option to override the default in various scenarios.  To know when to offer the override, the embedder needs to know when the mixed content was blocked.

-- 
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