Closed Bug 862750 Opened 13 years ago Closed 9 years ago

https://www.theverge.com/ does not render properly because of mixed content blocking

Categories

(Web Compatibility :: Site Reports, defect)

Product:
Web Compatibility
Component:
Site Reports
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: evilpies, Unassigned)

References

(
URL
)

Details

(Whiteboard: [mcb-chrome][mcb-ie][mcb-thirdparty-notified][sitewait][webcompat:sightline])

https://www.theverge.com/ should render like http://www.theverge.com. There is a LOT of mixed content on this page, especially the big images they are using.
Tom - do you use the HTTPS Everywhere extension? How did you discover this issue?
Didn't even think about that, but yes I have that extension.
Matt, can you test this on IE and Chrome and set the whiteboard flags if it is also blocked on those browsers: [mcb-chrome][mcb-ie]
Blocked on IE10 / Chrome 27 as well.
Whiteboard: [mcb-chrome][mcb-ie]
Does anyone have a contact from the verge?
Whiteboard: [mcb-chrome][mcb-ie] → [mcb-chrome][mcb-ie][mcb-no-contact]
Emailed Lauren Fisher detailing the issue.
Whiteboard: [mcb-chrome][mcb-ie][mcb-no-contact] → [mcb-chrome][mcb-ie][mcb-thirdparty-notified]
Issue still exists. Lukas, did you hear back from them on the issue?
Assignee: english-us → nobody
URL: https://www.theverge.com/
Component: English US → Desktop
Flags: needinfo?(lsblakk)
Whiteboard: [mcb-chrome][mcb-ie][mcb-thirdparty-notified] → [mcb-chrome][mcb-ie][mcb-thirdparty-notified][sitewait]
No, there was no response.
Flags: needinfo?(lsblakk)
It's been a while, and I don't see any MCB warnings (and they redirect to https by default now). Let's close this as WORKSFORME.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Web Compatibility
Whiteboard: [mcb-chrome][mcb-ie][mcb-thirdparty-notified][sitewait] → [mcb-chrome][mcb-ie][mcb-thirdparty-notified][sitewait][webcompat:sightline]
You need to log in before you can comment on or make changes to this bug.