Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • H HTTPS Everywhere EFF
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 251
    • Issues 251
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • HTTPS Everywhere EFF
  • Issues
  • #6977

Closed
Open
Created Sep 26, 2012 by Peter Eckersley@pde

[CHROME] add a power-user setting to re-enable mixedcontent rulesets

Rulesets disabled due to legacy/trac#6975 (moved) may still be useful to power users who prefer to look at things in HTTPS even if the CSS and/or JS is all messed up.

We should add a Chrome settings option to say "Force HTTPS even on sites that render weirdly if they are forced to be secure".

It should have a rollover/tooltip which explains that this is about embedded CSS/JS, and points to the shield in the URL bar.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking