[GH-ISSUE #242] HTML 5.2 release news - CSP3, other policies, etc. #203

New issue

Open

opened 2026-02-25 21:34:25 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 21:34:25 +03:00

Owner

Originally created by @dumblob on GitHub (Dec 29, 2017).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/242

Originally assigned to: @jasonmunro on GitHub.

Some changes (e.g. those regarding Content Security Policy, referrer policy, secure context, ...) might be of interest for Cypht:

https://www.w3.org/TR/2017/REC-html52-20171214/changes.html

Originally created by @dumblob on GitHub (Dec 29, 2017). Original GitHub issue: https://github.com/cypht-org/cypht/issues/242 Originally assigned to: @jasonmunro on GitHub. Some changes (e.g. those regarding Content Security Policy, referrer policy, secure context, ...) might be of interest for Cypht: https://www.w3.org/TR/2017/REC-html52-20171214/changes.html

kerem added the

research

label

2026-02-25 21:34:25 +03:00

kerem commented

2026-02-25 21:34:26 +03:00

Author

Owner

@jasonmunro commented on GitHub (Jan 3, 2018):

I will check it out, thanks for the heads up! I wonder what the state of supporting HTML 5.2 is with current browsers?

@jasonmunro commented on GitHub (Jan 3, 2018): I will check it out, thanks for the heads up! I wonder what the state of supporting HTML 5.2 is with current browsers?

kerem commented

2026-02-25 21:34:26 +03:00

Author

Owner

@dumblob commented on GitHub (Jan 4, 2018):

I wonder what the state of supporting HTML 5.2 is with current browsers?

We can't currently rely on that, but we should take these small enhancements and changes into account. If I'm not mistaken, most (all?) of them could be selectively checked for availability though.

@dumblob commented on GitHub (Jan 4, 2018): >I wonder what the state of supporting HTML 5.2 is with current browsers? We can't currently rely on that, but we should take these small enhancements and changes into account. If I'm not mistaken, most (all?) of them could be selectively checked for availability though.

kerem commented

2026-02-25 21:34:26 +03:00

Author

Owner

@jasonmunro commented on GitHub (Jan 4, 2018):

I'm not sure about that, I would have to dig into the spec to better understand what the new features are (and it's definitely possible some cannot be checked for availability since in certain cases that could be a security issue). It's also possible that new features will degrade properly or be ignored in which case we could implement them and "set it and forget it". I'm definitely interested in any thing new that increases security. When I have a chance to dig into it more I will let you know!

@jasonmunro commented on GitHub (Jan 4, 2018): I'm not sure about that, I would have to dig into the spec to better understand what the new features are (and it's definitely possible some cannot be checked for availability since in certain cases that could be a security issue). It's also possible that new features will degrade properly or be ignored in which case we could implement them and "set it and forget it". I'm definitely interested in any thing new that increases security. When I have a chance to dig into it more I will let you know!

kerem commented

2026-02-25 21:34:26 +03:00

Author

Owner

@marclaporte commented on GitHub (May 7, 2024):

@dumblob

Please retest, as a lot has changed since you reported this issue. Notably, we now have 3 active branches and recently released Cypht 2.0.0

@marclaporte commented on GitHub (May 7, 2024): @dumblob Please retest, as a lot has changed since you reported this issue. Notably, we now have 3 active branches and recently released Cypht 2.0.0 - https://github.com/cypht-org/cypht/releases/tag/v2.0.0 - https://github.com/cypht-org/cypht/wiki/Lifecycle