Closed Bug 838817 Opened 13 years ago Closed 12 years ago

Mixed_Content not being blocked on some websites

Categories

(Firefox :: Security, defect)

18 Branch
x86_64
Linux
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: koratezgs, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Build ID: 20130201190337 Steps to reproduce: I updated Firefox from 18.01 to 18.02 and then went to website: https://duck.co/topic/foss-2012-donation-nominations. When using 18.01, the site shows https with lock-icon (mixed_content is blocked). When using 18.02, the site shows https withOUT lock-icon (mixed_content is NOT blocked). Actual results: mixed_content is displayed when using Firefox 18.02 despite the fact that I have both about:config settings security.mixed_content.block_active_content AND security.mixed_content.block_display_content set to TRUE. Expected results: mixed_content should be blocked when the about:config settings are set to true. Updating to 18.02 broke this functionality.
Severity: normal → major
The update contains only a fix for one Javascript crash.
Component: Untriaged → Security: PSM
Product: Firefox → Core
I went and tested it again on different computers. Using 18.01, mixed_content is blocked on every single webpage I test. Using 18.02, mixed_content is never blocked. Whatever change was made to 18.02 appears to have broke mixed_content blocking.
Mixed Content is not blocked on this website: https://duck.co/topic/foss-2012-donation-nominations
Summary: 18.02 update broke security.mixed_content... settings → Mixed_Content not being blocked on some websites
Greg, please re-test this and leave a comment if this is still a problem. I think that duck.co fixed their site to not have mixed content.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Flags: needinfo?(koratezgs)
Resolution: --- → WORKSFORME
Component: Security: PSM → Security
Product: Core → Firefox
You need to log in before you can comment on or make changes to this bug.