To be more specific, the title should be "Add image/webp to default Accept navigation header" That is, include image/webp when content policy is DOCUMENT/SUB_DOCUMENT.
fetch()/"Save as" is with `Accept: */*" as is. Thanks for any feedback. Junior On Thu, Oct 31, 2019 at 4:31 PM Junior Hsu <ju...@mozilla.com> wrote: > Summary: > 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 > image/webp > to default Accept:, developers can tell the webp support by Accept header > for navigation > and opening URL by other application, other than inspect if version >= 65 > by User-Agent. > 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 66 for > aligning the spec. > > Please see the detailed discussion in the following bug, and feel free to > weigh in here > or on the bug. > > Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1544231 > > Link to standard: > https://fetch.spec.whatwg.org/#fetching 4.1.3 > > 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. > > Junior > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
