Bug 822371 - Mixed Content Doorhanger UI. r=dao
Bug 822367 - Plumbing needed to show user Mixed Content Blocker Doorhanger when Mixed Active Content is Blocked and allow user an option to load the inseucre content anyway. r=smaug
Bug 822367 - Since document.open() creates a new channel, set nsDocShell:mMixedContentChannel to the newly created channel if the user has decided to allow mixed content on the page. r=smaug
Bug 822367 - Performance enhancement - only call OnSecurityChange when the state really changes. r=smaug
Bug 822367 - Add mixed display flags to the document. Add mixed display and mixed active states to nsIWebProgressListener and use them in nsMixedContentBlocker. r=smaug
Bug 822367 - Use new nsIWebProgressListenerFlags for mixed active and mixed passive content in PSM. Also update the security state to STATE_IS_BROKEN if nsMixedContentBlocker has detected mixed content (even if PSM has not detected the mixed content). r=bsmith
Bug 822367 - Mochitests - User overrides mixed content blocking. r=smaug
Bug 822367 - With nsMixedContentBlocker.cpp, mixed content XHR calls are considered mixed active content and yield to a security state of STATE_IS_BROKEN. This fixes this mixed content todo-test to test that passes. r=bsmith