225562 2021-05-08 13:20:32 -0700 Send the supported image mimetypes in the HTTP request header for main resource 2023-08-22 12:49:35 -0700 1 1 1 Unclassified WebKit Images Safari 14 Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=211735 BrowserCompat, InRadar P2 Normal --- 1 yann webkit-unassigned achristensen beidson hi+webkit sabouhallawa simon.fraser webkit-bug-importer oldest_to_newest 1758206 0 yann 2021-05-08 13:20:32 -0700 Hi, It would be great if Safari was sending the accepted image mimetypes in the Accept header for a document request. That could save us a lot of (almost) redundant <source> in the HTML code. Chrome does it, Firefox does it, and Safari does it... but only for images request. That forces the developer to either have a list of sources, or to rely on a server-based solution for images requests (with a meaningless extension). Safari supports WebP, now, but new formats are coming, and I hope that Safari will support them soon. With all these new formats, every image tag could quickly look like this: <picture> <source srcset="path/to/my/1x/image.jxl 1x, path/to/my/2x/image.jxl 2x"> <source srcset="path/to/my/1x/image.avif 1x, path/to/my/2x/image.avif 2x"> <source srcset="path/to/my/1x/image.webp 1x, path/to/my/2x/image.webp 2x"> <img src="path/to/my/1x/image.jpg" srcset="path/to/my/1x/image.jpg 1x, path/to/my/2x/image.jpg 2x"> </picture> Chrome and Firefox, on the other hand, since they're sending the list of the format they support, can receive: <img srcset="path/to/my/image.jxl 1x, path/to/my/image.jxl 2x"> Of course, we could also parse the Safari user-agent to know which formats are supported (and maintain that code when a new format is supported), but it's way more complicated. Plus, the Accept header Safari is currently sending is not that great, since it's possible to type the URL of an image directly into the address bar. In that case, even a server-side mechanism won't be able to chose the most appropriate file to send, since Safari won't tell which image formats it supports in the Accept header (Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8). Thank you for reading this long text :-) 1758972 1 webkit-bug-importer 2021-05-11 10:54:34 -0700 <rdar://problem/77854289> 1972699 2 hi+webkit 2023-08-22 12:49:35 -0700 I’ve noticed that in Safari 16 the `Accept` header now seems correct for image requests that are part of an HTML document, but incorrect when loading an image directly. For example, I get this request header on web pages I visit `Accept:image/avif,image/webp,…` (truncated for brevity) but the same `text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8` when opening the image in its own tab.