Re: Intent to ship: Add image/webp to default Accept header

2019-11-04 Thread Anne van Kesteren
On Fri, Nov 1, 2019 at 8:35 PM Boris Zbarsky wrote: > On 10/31/19 7:31 PM, Junior Hsu wrote: > > However, it doesn't not align the spec > > Is that covered by https://github.com/whatwg/fetch/issues/274 or is > there a new spec issue needed? That covers it. The specification says "should" currentl

Re: Intent to ship: Add image/webp to default Accept header

2019-11-01 Thread Boris Zbarsky
On 10/31/19 7:31 PM, Junior Hsu wrote: However, it doesn't not align the spec Is that covered by https://github.com/whatwg/fetch/issues/274 or is there a new spec issue needed? -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org htt

Re: Intent to ship: Add image/webp to default Accept header

2019-11-01 Thread Junior Hsu
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 wrot

Re: Intent to ship: Add image/webp to default Accept header

2019-11-01 Thread Gijs Kruitbosch
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?) ~ Gijs On 31/10/2019 23:31, Junior Hsu wrote: Summary: I'd like to increase the visibility for this c

Intent to ship: Add image/webp to default Accept header

2019-10-31 Thread Junior Hsu
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 othe