Closed
Bug 975929
Opened 10 years ago
Closed 7 years ago
[MCB] Buttons in the upper-right of Tumblogs don't show with MCB and HTTPS Everywhere
Categories
(Web Compatibility :: Site Reports, defect)
Web Compatibility
Site Reports
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: strugee, Unassigned)
References
()
Details
(Whiteboard: [country-us] [contactready] [mcb])
Steps to Reproduce: 1. Have the Mixed Content Blocker turned on 2. Have HTTPS Everywhere[1] installed and turned on 3. Load any Tumblog, e.g. tumblrbot.tumblr.com 4. Look for the "follow" and "dashboard" buttons at the top-right. Expected results: The buttons should display. Actual results: The buttons trigger a Mixed Content Blocker violation and never display. Obviously, this issue is triggered by HTTPS Everywhere. However, eventually Tumblr is probably going to turn on HTTPS by default for these things, and it will break in all browser configurations, not just those with HTTPS Everywhere. Better to fix it now than later. [1]: https://www.eff.org/https-everywhere
Reporter | ||
Comment 1•10 years ago
|
||
Looks like Tumblr is going to turn this on quite soon. From https://www.eff.org/deeplinks/2013/11/encrypt-web-report-whos-doing-what: > Tumblr is planning to upgrade its web connections to HTTPS this year and implement HSTS by 2014
Comment 2•10 years ago
|
||
Confirming for Aurora 30 with HTTPS Everywhere installed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•10 years ago
|
||
I get a blocking for one asset only Loading mixed (insecure) display content on a secure page "http://38.media.tumblr.com/avatar_35a1a3ec0cf3_64.png"[Learn More] Which is the avatar.
Assignee: english-us → nobody
Component: English US → Desktop
Whiteboard: [country-us] [contactready] [mcb]
Comment 4•7 years ago
|
||
No MCB errors anymore, and Tumblr is HTTPS by default. Let's close.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•5 years ago
|
Product: Tech Evangelism → Web Compatibility
You need to log in
before you can comment on or make changes to this bug.
Description
•