Re: Subresource Integrity for Lazy-Loaded Resources

On Sat, Mar 6, 2021 at 8:55 PM Daniel Veditz <dveditz@mozilla.com> wrote:

> I'm having trouble wrapping my head around the concept of using both
> "preload" and "lazy loading" for the same resources -- don't those work at
> cross-purposes? Could you write up a simple description or sketch of a
> timeline of what happens when for these, in relation to other resources,
> preloaded and not?
>

I think the goal here is more to "load" than to "preload".

The approach of reusing preload here is definitely interesting...
I think we can go about this in a couple of ways.
One is to have those declarations only apply to integrity, in which case it
may make sense to define a separate rel for them. e.g. <link
rel=subresource integrity=0xbadbeef>.
Another option is to use those declarations to actually load the resource.
For that we could stick with preload and go with something like a milestone
attribute
<https://docs.google.com/document/d/15k6sLw3hscfsD1BD51FJ_qWLIOVziS33a3Ld-kB-G3w/edit#heading=h.x093xhzcx2f8>
to
help developers indicate *when* that resource is actually needed, and to
avoid it getting in the way of more critical resources.


> -Dan Veditz
>