Would this fix https://bugzilla.mozilla.org/show_bug.cgi?id=1526731#c15
? (That is, would we now send image/webp as part of the accept header
for the fetch() / nsIWebBrowserPersist requests?)
On 31/10/2019 23:31, Junior Hsu wrote:
I'd like to increase the visibility for this controversial intention.
Currently Firefox send
image/webp for image content, but it fails for navigation case. By adding
to default Accept:, developers can tell the webp support by Accept header
and opening URL by other application, other than inspect if version >= 65
However, it doesn't not align the spec, and it makes the Accept: longer in
a hack way.
FWIW, we add image/webp to default Accept header in 65, and it's removed in
aligning the spec.
Please see the detailed discussion in the following bug, and feel free to
weigh in here
or on the bug.
Link to standard:
Platform coverage: This will be exposed to all platforms.
Estimated or target release: Firefox 72
Do other browser engines implement this? Chrome, who supports webp, did.
Is this feature enabled by default in sandboxed iframes? Yes.
dev-platform mailing list