[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 10:56:30 PST 2010


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





--- Comment #2 from Darin Adler <darin at apple.com>  2010-02-26 10:56:30 PST ---
(From update of attachment 49600)
> +#if PLATFORM(CHROMIUM)
> +        secureSchemes.add("chrome-extension");
> +#endif

Is this the right place to add this? Wouldn't this registration belong in
Chromium code rather than in Chromium WebKit? I'd expect the same level that
adds the extension mechanism would want to register the scheme so that other
clients without the mechanism wouldn't have it registered.

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