This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The introduction includes 'images' as potentially covered content, but the specification does nothing to explicitly support this, such as adding an @integrity attribute to the img element (and HTMLImageElement).
As discussed in the past, adding such support using a single attribute on img is probably not enough. Such support would probably require adding it to srcset as well, possibly in the form of "integrity descriptors" of some sort.
Didn't we come up with syntax for that, Yoav? Freddy, was this part of The Great Shrinkening that you're doing for a trimmed-down v1?
We've discussed some options, but I don't think we ever came up with a concrete proposal. I'll open up a related issue on the respimg repo
What's the general process here? I removed the syntax because we wanted to do styles and scripts only in version 1. The plan is to bring this in, when we actually *do* image integrity. I ripped this out in https://github.com/w3c/webappsec/pull/74.
(In reply to fbraun from comment #4) > What's the general process here? I removed the syntax because we wanted to > do styles and scripts only in version 1. The plan is to bring this in, when > we actually *do* image integrity. > > I ripped this out in https://github.com/w3c/webappsec/pull/74. in that case, you need to say those are the plans, preferably saying this near where you say you are handling images and fonts