WebView.blockedContent indicates the wrong state in some circumstances

Bug #1368117 reported by Chris Coulson on 2014-09-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Chris Coulson
Chris Coulson

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

Changed in oxide:
importance: Undecided → Medium
status: New → Triaged
milestone: none → branch-1.3
assignee: nobody → Chris Coulson (chrisccoulson)
description: updated
Changed in oxide:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers