You mean the private security group list? I'm curious why you say that. Generally we should discuss as much on public lists as possible, especially new features or changes to existing ones. Security group exists really just to discuss issues that we can't publicly, because doing so would put users at direct risk. Thanks! Lucas.
On May 18, 2011, at 15:17, Jean-Marc Desperrier <jmd...@gmail.com> wrote: > Brian Smith wrote: >> See https://twitter.com/#!/scarybeasts/status/69138114794360832: >> "Chrome 13 dev channel now blocks certain types of mixed content by >> default (script, CSS, plug-ins). Let me know of any significant >> breakages." >> >> See >> https://ie.microsoft.com/testdrive/browser/mixedcontent/assets/woodgrove.htm >> IE9: http://tinypic.com/view.php?pic=11qlnhy&s=7 >> Chrome: http://tinypic.com/view.php?pic=oa4v3n&s=7 >> >> IE9 blocks all mixed content by default, and allows the user to >> reload the page with the mixed content by pushing a button on its >> doorhanger (at the bottom of the window in IE). >> >> Notice that Chrome shows the scary crossed-out HTTPS in the address >> bar. > > This is actually much more a suject for the .security group, Brian. > _______________________________________________ > dev-security mailing list > dev-secur...@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-security -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
