[Question]In browser console, why request resource which is marked 'preload' in the html won't work?

[NE-SmallTown]

e.g. I use

<link rel="preload" href="http://foo.com/bar.jpg" as="image">

and

console.log(
  '%c   ',
  `
    font-size: 60px; 
    background-image:url('http://foo.com/bar.jpg'); 
    background-repeat: no-repeat; 
    background-size: contain;
   `
);

But will get warning 'The resourcehttp://foo.com/bar.jpg was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it wasn't preloaded for nothing.'

I think the request fired by console is also should be applicable to the 'preload' mechanism.If i am wrong, please let me know, thanks :)

[domenic]

I don't think this is the best forum for this question; I'd suggest e.g. StackOverflow.com, or the bug trackers of whatever browser you are experiencing this warning in.

Going to close, since this is not an issue with the HTML Standard, but happy to continue discussing in the closed thread---although again, I doubt we can be of much help compared to those other sources.

[NE-SmallTown]

@domenic Sorry.The reason I file this issue is that the spec just says

the user agent must preemptively fetch and cache the specified resource

but don't describe how to use it, so I don't know the situation I describe above whether is applicable for the 'preload' spec, and I am not sure this belongs to spec or browser(although I did not found the spec says the user agent should fire or not relevant warning), so I want to figure out first and then file the issue in the right place.

And maybe StackOverflow needs a long time to see a reply or even no reply about this, hah, so maybe closed thread is a good place to discuss?

[domenic]

The processing model for preload is described in the preload specification: https://w3c.github.io/preload/

But the processing model for consoles is browser-specific, and isn't defined by any spec since it's not observable by web pages.

[NE-SmallTown]

got it, thank you :)

[NE-SmallTown]

I file a related issue in chrome, if anyone want to know more about this, you can view this