The underlying problem is that sometimes that bug causes havoc in which we rewrite the top level page to HTTPS, and then the mixed content blocker kicks in and blocks scripts before we can rewrite their URLs to HTTPS (!).
Although to be fair, that horrible bug has subsequently been implemented in Firefox, so probably we should downgrade both extensions back to beta :( At least Mozilla developers are doing real work on fixing it; I haven't been able to wrangle that out of the Chrome team yet :/. On Fri, Aug 22, 2014 at 07:10:46PM -0400, Jacob S Hoffman-Andrews wrote: > > It's debatable whether this is a beta or not. Jsha argues that > we're stable, but I worry that we can't really be stable until > https://code.google.com/p/chromium/issues/detail?id=122548 is > resolved. > > For context: the bug is "Chrome displays insecure content warnings > for content handled by the WebRequest API." I would argue that this > should be considered a minor graphical bug. The functionality is > sound, but for some pages there will be a yellow triangle warning in > the URL bar. The warning will never be a crossed-out red HTTPS > because of mixed content blocking. > > I think the beta label no longer conveys any informational content, > and just makes the versioning confusing - what's beta vs development > vs stable? > -- Peter Eckersley [email protected] Technology Projects Director Tel +1 415 436 9333 x131 Electronic Frontier Foundation Fax +1 415 436 9993 _______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
