search

w3c / webappsec-mixed-content

WebAppSec Mixed Content
https://w3c.github.io/webappsec-mixed-content/
Other
12 stars 22 forks source link

References to [mixed-content] don't point to the level 1 spec #58

Closed jyasskin closed 2 years ago

jyasskin commented 2 years ago

https://www.w3.org/TR/mixed-content/#category-upgradeable says

Upgradeable content was previously referred to as optionally-blockable in [mixed-content]

but that reference points to Mixed Content Level 2. It, and at least most of the other uses of [mixed-content] should point to level 1 instead.

annevk commented 2 years ago

FWIW, I think the solution here should be to simply remove the reference and adjust the sentence so it can stand on its own. For instance:

Upgradeable content was previously referred to as optionally-blockable.

jyasskin commented 2 years ago

There are 5 references to the level 1 spec that can probably all go away, but they'll each take a bit of editing.

sideshowbarker commented 2 years ago

There are 5 references to the level 1 spec that can probably all go away, but they'll each take a bit of editing.

I opened #57 for this. Please take a look there and let me know if I missed anything