I think the answer is yes, based on this [1]: > *Update (12/12/13)*: Firefox 23+ has enabled mixed content blocking by > default. As a result, many rules that were previously labeled "firefox" > should now be labeled "mixedcontent." >
But I don’t think that’s a very clear answer. Can someone confirm this? [1] https://www.eff.org/https-everywhere/rulesets -- Brian Drake All content created by me: Copyright<http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html>© 2014 Brian Drake. All rights reserved. On Wed, Jan 15, 2014 at 1316 (UTC), Drake, Brian <[email protected]>wrote: > In the ACM.org ruleset [1], there is a comment that says that we secure > all mixed content requests and, therefore, it should not be marked > mixedcontent. > > However, it still is marked mixedcontent. > > Is this the accepted workaround for the mixed content blocker not allowing > the requests to get to us [2]? > > [1] > https://gitweb.torproject.org/https-everywhere.git/blob/HEAD:/src/chrome/content/rules/ACM.org.xml > [2] > https://lists.eff.org/pipermail/https-everywhere/2014-January/001901.html > > -- > Brian Drake > > All content created by me: > Copyright<http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html>© 2014 > Brian Drake. All rights reserved. >
