@serkodev is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

Hey, thanks for the work!

I think this is a reasonable solution however we need to be mindful as this may break the look and feel of current users videos given the size difference, the current is 640x480 with this change it becomes 480x360.

Do you have any ideas on how to workaround this? I think the ideal case is probably two things:

1. props to easily choose the right thumbnail size / webp
2. a <img onerror fallback that serves the lower res safe size (if it's using the defaults). It would be nice to use picture or something for this but seems like it wouldn't work (<picture> and <source> elements: How should 404s with placeholder image data be handled? whatwg/html#8916)

Also I'd still go with the webp endpoint (smaller image size)

If we provide props to choose the thumbnail size or WebP format, I believe we don't have a perfect solution to detect if a YouTube video doesn't support these options.

1. Use fetch to request the image and check the response code (we all know this isn't a good approach).
2. Fetch the YouTube Data API to get a list of thumbnail URLs (this method requires an API key and is not very client-side rendering-friendly).

There's a somewhat hacky method that involves detecting the image size.
Since all 404 images will have a size of 120x90, we can use this characteristic to detect whether a thumbnail exists. If we detect that the image size is 120x90, we can then fallback to default.jpg.

The only drawback is that if the original image request (e.g., default.jpg, 1.jpg, 2.jpg, 3.jpg) already has a size of 120x90, we can't determine if it's actually a 404. It may be forcibly fallback to default.jpg, unless we calculate the image data (e.g., hash) to determine if it's a not-found image, but that would make things increasingly complicated.

However, if we only provide props for thumbnail size or WebP format and let users determine whether the image is supported, then we might not need to detect if it's a 404 at all.

That's all I can think of for now. 🤣

I think the dimension heuristic is good enough and is free compared to doing extra requests manually.

<img src="https://i.ytimg.com/vi_webp/jNQXAC9IVRw/sddefault.webp" onload="if (this.naturalWidth == 120 && this.naturalHeight == 90) { (this.src = `https://i.ytimg.com/vi/jNQXAC9IVRw/hqdefault.jpg`) }" />

We should warn the developer in development that they should use the props when this fallback occurs.

Thanks for the feedback.

How about the behavior of the placeholder slot prop?

• Should we keep passing sddefault.webp as placeholder ?
• Or should we need to add a placeholderFallback (to pass hqdefault.jpg) slot prop?

As discussed previously, we can pass all formats of thumbnail links for the user to choose from. If we directly turn placeholder into a map containing all URLs, it might impact existing users.

• Should we pass an additional placeholders prop including all URLs?