In the Chrome port, if an HTTPS website times out, the user won't get a context menu to turn off the ruleset that HTTPSified things in the first place!
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
Fixed by commit 8d82be18dd803e22a05ce51ba7e8089762ee61a4 in gitosis@git.eff.org:public/dan/https-everywhere.git. It still needs to be merged into the main repo's master branch.
Trac: Resolution: N/Ato fixed Status: new to closed
Dammit, I though we'd fixed this, but variants of this bug still seem to be lurking for me. Running 2012.6.21, visiting http://blip.tv is an example case.
Trac: Resolution: fixed toN/A Status: closed to reopened
I've added more event listeners to fire chrome.pageAction.show() in more possible situations. For the blip.tv case, onErrorOccurred appears to be the correct listener. However, although chrome.pageAction.show() is executing with the relevant tabId as an argument, curiously it does not seem to be working as the UI widget is still missing.