[Webkit-unassigned] [Bug 35438] Chrome extensions cause "Some insecure content" on all secure pages

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 26 14:20:19 PST 2010


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


Sam Weinig <sam at webkit.org> changed:

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




--- Comment #4 from Sam Weinig <sam at webkit.org>  2010-02-26 14:20:19 PST ---
(In reply to comment #3)
> That was my original plan, but then I saw the following:
> 
> http://trac.webkit.org/browser/trunk/WebCore/page/SecurityOrigin.cpp#L57
> 
> IMHO, we shouldn't have platform-specific ifdefs in either place.

That could probably be turned into something we set at the WebKit layer. One
difference is that applewebdata is a WebKit level thing (still admittedly a
layering violation), the chrome-extensions are an Application layer thing.

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