Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixed content article should switch from the notion of active/passive content to blocked/upgradable content #33696

Closed
mozfreddyb opened this issue May 21, 2024 · 3 comments · Fixed by #33786
Labels
Content:Security Security docs goal: up-to-date (Experimental label) Issues about outdated content. help wanted If you know something about this topic, we would love your help!

Comments

@mozfreddyb
Copy link

MDN URL

https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content

What specific section or headline is this issue about?

This is about the whole article

What information was incorrect, unhelpful, or incomplete?

The Mixed Content spec has migrated away from the terminology "active" and "passive" content.

What did you expect to see?

There is only blocked and upgradable content now.
With https://www.w3.org/TR/mixed-content/, the difference is that everything is considered "blocked" except img, audio and video elements - which are considered upgradable.

Do you have any supporting links, references, or citations?

https://www.w3.org/TR/mixed-content/

Do you have anything more you want to share?

Firefox is making this switch in 127 which ships on June 11th. I am working on an accompanying blog post, that I am willing to share with MDN content authors. Ping me via email (fbraun-at-mozilla.com) or Mozilla slack.

MDN metadata

Page report details
@mozfreddyb mozfreddyb added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label May 21, 2024
@github-actions github-actions bot added the Content:Security Security docs label May 21, 2024
@hamishwillee
Copy link
Collaborator

hamishwillee commented May 23, 2024

Thanks @mozfreddyb - this should be looked at as part of #33592. I've assigned to myself and emailed you.

Initial research indicates that perhaps Chrome shipped this in version 86 https://chromestatus.com/feature/4926989725073408 but has allowed it to be relaxed on private networks in v124 https://chromestatus.com/feature/4926989725073408

Do you know if Safari has any support for upgrading mixed content? The mdn doc just says "it has no support" which I presume means it doesn't load it.

@mozfreddyb
Copy link
Author

Chrome shipped this in 2020, I believe. WebKit has a positive standards position and an implementation behind a flag, but did not ship yet. I am expecting them to follow soon.

@Josh-Cena Josh-Cena added help wanted If you know something about this topic, we would love your help! goal: up-to-date (Experimental label) Issues about outdated content. and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Jun 5, 2024
@mozfreddyb
Copy link
Author

Chrome shipped this in 2020, I believe. WebKit has a positive standards position and an implementation behind a flag, but did not ship yet. I am expecting them to follow soon.

FWIW, this will be shipped in Safari 18. https://webkit.org/blog/15443/news-from-wwdc24-webkit-in-safari-18-beta/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:Security Security docs goal: up-to-date (Experimental label) Issues about outdated content. help wanted If you know something about this topic, we would love your help!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants