ubuntu-webapps-bugs team mailing list archive
-
ubuntu-webapps-bugs team
-
Mailing list archive
-
Message #01441
[Bug 1368117] Re: WebView.blockedContent indicates the wrong state in some circumstances
** Changed in: oxide/1.2
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1368117
Title:
WebView.blockedContent indicates the wrong state in some circumstances
Status in Oxide Webview:
Fix Released
Status in Oxide 1.2 series:
Fix Released
Bug description:
Whilst writing the test for this, I noticed that if you do the
following:
- set WebPreferences.canDisplayInsecureContent to false
- load a page over SSL that contains an insecure script and an insecure image (at this point, the ContentTypeMixedDisplay and ContentTypeMixedScript bits of WebView.blockedContent are set, correctly)
- call WebView.setCanTemporarilyDisplayInsecureContent(true) (which causes the page to reload).
At this point, WebView.blockedContent should still have the
ContentTypeMixedScript bit set, but it is now clear
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1368117/+subscriptions
References